Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal
On 07/18/2017 10:01 AM, Tony Breeds wrote: It wasn't forgotten as suchi, there are jobs still using it/them. If keeping the branches around cuases bigger probelsm then EOLing them is fine. I'll try to generate a list of the affected projects/jobs and turn them off. Thanks; yeah this was pointed out to me later. I think any jobs can use the -eol tag, rather than the branch if required (yes, maybe easier said than done depending on how many layers of magic there are :). There doesn't seem to be much point in branches we can't commit to due to broken CI, and I doubt anyone is keen to maintain it. -i __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal
On Mon, Jul 17, 2017 at 07:22:34PM +1000, Ian Wienand wrote: > I have taken the liberty of EOL-ing stable/liberty and stable/mitaka > for devstack. I get the feeling it was just forgotten at the time. > Comments in [4] support this theory. I have also taken the liberty of > approving backports of the fix to newton and ocata branches [5],[6]. It wasn't forgotten as suchi, there are jobs still using it/them. If keeping the branches around cuases bigger probelsm then EOLing them is fine. I'll try to generate a list of the affected projects/jobs and turn them off. Yours Tony. signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal
On Mon, Jul 17, 2017 at 07:22:34PM +1000, Ian Wienand wrote: > Hi, > > The removal of the mysql.qcow2 image [1] had a flow-on effect noticed > first by Paul in [2] that the tools/image_list.sh "sanity" check was > not updated, leading to DIB builds failing in a most unhelpful way as > it tries to cache the images for CI builds. > > So while [2] fixes the problem; one complication here is that the > caching script [3] loops through the open devstack branches and tries > to collect the images to cache. > > Now it seems we hadn't closed the liberty or mitaka branches. This > causes a problem, because the old branches refer to the old image, but > we can't actually commit a fix to change them because the branch is > broken (such as [4]). > > I have taken the liberty of EOL-ing stable/liberty and stable/mitaka > for devstack. I get the feeling it was just forgotten at the time. > Comments in [4] support this theory. I have also taken the liberty of > approving backports of the fix to newton and ocata branches [5],[6]. > > A few 3rd-party CI people using dib have noticed this failure. As the > trio of [4],[5],[6] move through, your builds should start working > again. > > Thanks, > > -i > > [1] https://review.openstack.org/482600 > [2] https://review.openstack.org/484001 > [3] > http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/cache-devstack/extra-data.d/55-cache-devstack-repos > [4] https://review.openstack.org/482604 > [5] https://review.openstack.org/484299 > [6] https://review.openstack.org/484298 > Thanks, I had patches up last week but was hitting random devstack job failures. I'll watch this today and make sure our image builds are back online. Also, thanks for cleaning up the old branches. I was planning on doing that this week. -PB __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal
Hi, The removal of the mysql.qcow2 image [1] had a flow-on effect noticed first by Paul in [2] that the tools/image_list.sh "sanity" check was not updated, leading to DIB builds failing in a most unhelpful way as it tries to cache the images for CI builds. So while [2] fixes the problem; one complication here is that the caching script [3] loops through the open devstack branches and tries to collect the images to cache. Now it seems we hadn't closed the liberty or mitaka branches. This causes a problem, because the old branches refer to the old image, but we can't actually commit a fix to change them because the branch is broken (such as [4]). I have taken the liberty of EOL-ing stable/liberty and stable/mitaka for devstack. I get the feeling it was just forgotten at the time. Comments in [4] support this theory. I have also taken the liberty of approving backports of the fix to newton and ocata branches [5],[6]. A few 3rd-party CI people using dib have noticed this failure. As the trio of [4],[5],[6] move through, your builds should start working again. Thanks, -i [1] https://review.openstack.org/482600 [2] https://review.openstack.org/484001 [3] http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/cache-devstack/extra-data.d/55-cache-devstack-repos [4] https://review.openstack.org/482604 [5] https://review.openstack.org/484299 [6] https://review.openstack.org/484298 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
