On Mon, Dec 28, 2015 at 01:52:45PM +0100, Julien Danjou wrote: > On Mon, Dec 28 2015, Rabi Mishra wrote: > > > Yes, this has started happening after keystone/trusts config changes by the > > devstack patch you mentioned. I've no idea how this can be fixed. As Steve > > Hardy is away, either someone with keystone knowledge should fix this or we > > merge the devstack patch revert[3] that I tested few days ago. > > Why don't you just revert the devstack change? > > This is way saner than disabling the test! Steve will be able to rework > his initial change when he come back.
Firstly, I'm very sorry for the breakage here, and I agree that in general a quick-revert is the best policy when something like this happens. I'm a little unclear how this occurred tho, since I had a clear CI run on this patch: https://review.openstack.org/#/c/256315/ Which had a Depends-On to the devstack change, anyone know why that didn't fail with the CeilometerAlarmTest.test_alarm before the devstack change merged? Regardless, we've got several fixes now which can be considered: 1. Rabi's devstack revert: https://review.openstack.org/#/c/261310/ 2. Fix the actual issue in heat: https://review.openstack.org/#/q/topic:bug/1529058 Given that the review latency on Devstack is quite high, it seems possible we'll land (2) before (1) lands, but if not then I'll re-propose it and hopefully figure out where I went wrong with Depends-On to confirm all is fixed before it lands. Also, there's this fix: https://review.openstack.org/#/c/261398/ I've not yet confirmed if this also fixes the issue referencing the default domain which broke the alarm tests. Steve __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
