<div dir="ltr">On Thu, Feb 9, 2017 at 7:51 AM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">On 02/09/2017 07:00 AM, Jim Rollenhagen wrote:<br>
> Hey folks,<br>
><br>
> Ironic plans to release Ocata this week, once we have a couple small patches<br>
> and a release note cleanup landed.<br>
><br>
> However, our grenade job is now testing master->master, best I can tell.<br>
> This<br>
> is pretty clearly due to this d-s-g commit:<br>
> <a href="https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8" rel="noreferrer" target="_blank">https://github.com/openstack-<wbr>infra/devstack-gate/commit/<wbr>9c752b02fbd57c7021a7c9295bf4d6<wbr>8a0d1973a8</a><br>
><br>
> Evidence:<br>
><br>
> * it appears to be checking out a change on master into the old side:<br>
><br>
> <a href="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" rel="noreferrer" target="_blank">http://logs.openstack.org/44/<wbr>354744/10/check/gate-grenade-<wbr>dsvm-ironic-ubuntu-xenial/<wbr>4b395ff/logs/grenade.sh.txt.<wbr>gz#_2017-02-09_07_15_32_979</a><br>
><br>
> * and somewhat coincidentally, our grenade job seems to be broken when<br>
> master<br>
>   (ocata) is on the old side, because we now select instance images in our<br>
>   devstack plugin:<br>
><br>
> <a href="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" rel="noreferrer" target="_blank">http://logs.openstack.org/44/<wbr>354744/10/check/gate-grenade-<wbr>dsvm-ironic-ubuntu-xenial/<wbr>4b395ff/logs/grenade.sh.txt.<wbr>gz#_2017-02-09_08_07_10_946</a><br>
><br>
> So, we're currently blocking the ironic release on this, as obviously we<br>
> don't<br>
> want to release if we don't know upgrades work. As I see it, we have two<br>
> options:<br>
><br>
> 1) Somehow fix devstack-gate and configure our jobs in project-config<br>
> such that<br>
> this job upgrades newton->master. I might need some help on navigating this<br>
> one.<br>
><br>
> 2) Make our grenade job non-voting for now, release 7.0.0 anyway, and<br>
> immediately make sure that the stable/ocata branch runs grenade as<br>
> expected and<br>
> passes. If it isn't passing, fix what we need to and cut 7.0.1 ASAP.<br>
><br>
> Thoughts?<br>
<br>
</div></div>By now ironic should have a stable/ocata branch, right? That's the thing<br>
that is missing -<br>
<a href="https://github.com/openstack-infra/devstack-gate/commit/9c752b02fbd57c7021a7c9295bf4d68a0d1973a8" rel="noreferrer" target="_blank">https://github.com/openstack-<wbr>infra/devstack-gate/commit/<wbr>9c752b02fbd57c7021a7c9295bf4d6<wbr>8a0d1973a8</a><br>
<br>
A stable/ocata branch doesn't require a release. It's an expectation<br>
that all the projects have one of those at this point.<br>
<br>
I'd be -1 putting project specific branch selection logic inside<br>
devstack-gate. Things are already complicated enough there.<br></blockquote><div><br></div><div>Ironic's release model is <span class="gmail-pl-s">cycle-with-intermediary, meaning we don't do release<br></span></div><div><span class="gmail-pl-s">candidates, and don't necessarily branch at the same time. The deadline is next<br></span></div><div><span class="gmail-pl-s">week; we were hoping to get ahead of the game this week.<br><br></span></div><div><span class="gmail-pl-s">And a branch does require a release as a branch point (though in most cases that's<br></span></div><div><span class="gmail-pl-s">an RC1 release), if the project is released at all, AIUI.<br></span></div><div><span class="gmail-pl-s"><br></span></div><div><span class="gmail-pl-s">// jim</span><br></div></div><br></div></div>