[openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

Sean Dague sean at dague.net
Thu Feb 9 13:37:29 UTC 2017


On 02/09/2017 08:22 AM, Jim Rollenhagen wrote:
> On Thu, Feb 9, 2017 at 7:51 AM, Sean Dague <sean at dague.net
> <mailto:sean at dague.net>> wrote:
> 
>     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.
>     > This
>     > is pretty clearly due to this d-s-g commit:
>     >
>     https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8
>     <https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8>
>     >
>     > Evidence:
>     >
>     > * it appears to be checking out a change on master into the old side:
>     >
>     >
>     http://logs.openstack.org/44/354744/10/check/gate-grenade-dsvm-ironic-ubuntu-xenial/4b395ff/logs/grenade.sh.txt.gz#_2017-02-09_07_15_32_979
>     <http://logs.openstack.org/44/354744/10/check/gate-grenade-dsvm-ironic-ubuntu-xenial/4b395ff/logs/grenade.sh.txt.gz#_2017-02-09_07_15_32_979>
>     >
>     > * and somewhat coincidentally, our grenade job seems to be broken when
>     > master
>     >   (ocata) is on the old side, because we now select instance
>     images in our
>     >   devstack plugin:
>     >
>     >
>     http://logs.openstack.org/44/354744/10/check/gate-grenade-dsvm-ironic-ubuntu-xenial/4b395ff/logs/grenade.sh.txt.gz#_2017-02-09_08_07_10_946
>     <http://logs.openstack.org/44/354744/10/check/gate-grenade-dsvm-ironic-ubuntu-xenial/4b395ff/logs/grenade.sh.txt.gz#_2017-02-09_08_07_10_946>
>     >
>     > So, we're currently blocking the ironic release on this, as
>     obviously we
>     > don't
>     > want to release if we don't know upgrades work. As I see it, we
>     have two
>     > options:
>     >
>     > 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
>     > one.
>     >
>     > 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.
>     >
>     > Thoughts?
> 
>     By now ironic should have a stable/ocata branch, right? That's the thing
>     that is missing -
>     https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8
>     <https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8>
> 
>     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.
> 
> 
> Ironic's release model is cycle-with-intermediary, meaning we don't do
> release
> candidates, and don't necessarily branch at the same time. The deadline
> is next
> week; we were hoping to get ahead of the game this week.
> 
> And a branch does require a release as a branch point (though in most
> cases that's
> an RC1 release), if the project is released at all, AIUI.

Ok, sorry, my failure to understand that's all linked.

	-Sean

-- 
Sean Dague
http://dague.net



More information about the OpenStack-dev mailing list