[openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton
sean at dague.net
Thu Feb 9 12:51:41 UTC 2017
On 02/09/2017 07:00 AM, Jim Rollenhagen wrote:
> Hey folks,
> Ironic plans to release Ocata this week, once we have a couple small patches
> and a release note cleanup landed.
> However, our grenade job is now testing master->master, best I can tell.
> is pretty clearly due to this d-s-g commit:
> * it appears to be checking out a change on master into the old side:
> * and somewhat coincidentally, our grenade job seems to be broken when
> (ocata) is on the old side, because we now select instance images in our
> devstack plugin:
> So, we're currently blocking the ironic release on this, as obviously we
> want to release if we don't know upgrades work. As I see it, we have two
> 1) Somehow fix devstack-gate and configure our jobs in project-config
> such that
> this job upgrades newton->master. I might need some help on navigating this
> 2) Make our grenade job non-voting for now, release 7.0.0 anyway, and
> immediately make sure that the stable/ocata branch runs grenade as
> expected and
> passes. If it isn't passing, fix what we need to and cut 7.0.1 ASAP.
By now ironic should have a stable/ocata branch, right? That's the thing
that is missing -
A stable/ocata branch doesn't require a release. It's an expectation
that all the projects have one of those at this point.
I'd be -1 putting project specific branch selection logic inside
devstack-gate. Things are already complicated enough there.
More information about the OpenStack-dev