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 point
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 o
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
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 comp
