[openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

Tony Breeds tony at bakeyournoodle.com
Thu Apr 7 04:29:46 UTC 2016

On Wed, Apr 06, 2016 at 10:08:44AM +0000, Amrith Kumar wrote:
> Stable team, the reason for this failure of py27 in kilo is 
> 	https://bugs.launchpad.net/trove/+bug/1437179
> The bug was fixed in liberty in commit I92eaa1c98f5a58ce124210f2b6a2136dfc573a29 and therefore, at this time, only impacts Kilo.
> The issue is that the flavors are coming back in a non-deterministic order.
> The fix was to take this into account while comparing the expected output to
> the actual output. Please advise whether you would like this testing change
> to be backported to Kilo, it is a clean cherry pick of the change listed
> above.

By the letter of the stable policy this isn't appropriate BUT ... 

It's a small self contained fix that corrects an interment test failure.

I'd accepts a backport, and I don't think it would endanger the
stable:follows-policy tag :)

Thanks again for staying on top of the trove periodic-stable queue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160407/9dfb4150/attachment.pgp>

More information about the OpenStack-dev mailing list