Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Rabi Mishra
> 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 > > >

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Steven Hardy
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

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Rabi Mishra
> > Hi, > > >> 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? > > > > It seems the test was skipped[1], as it was disabled for another > > bug[2]. > > > > [1] > >

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Julien Danjou
On Mon, Jan 04 2016, Steven Hardy wrote: Hi, > 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. No problem Steven, shit happens. It'd be even better if Heat'd move to a devstack plugin to limit this

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Steven Hardy
On Mon, Jan 04, 2016 at 11:31:40AM +0100, Julien Danjou wrote: > On Mon, Jan 04 2016, Steven Hardy wrote: > > Hi, > > > 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. > > No problem Steven, shit

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Mehdi Abaakouk
Hi, 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? It seems the test was skipped[1], as it was disabled for another bug[2]. [1]

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2016-01-04 Thread Steven Hardy
On Mon, Jan 04, 2016 at 11:31:40AM +0100, Julien Danjou wrote: > On Mon, Jan 04 2016, Steven Hardy wrote: > > Hi, > > > 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. > > No problem Steven, shit

[openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2015-12-28 Thread Julien Danjou
Hi there, The gate for telemetry projects is broken: https://bugs.launchpad.net/heat/+bug/1529583 The failure appears in Heat from what I understand: BadRequest: Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2015-12-28 Thread Sergey Kraynev
Hi, Julien. I suppose, that your guess is right. Mentioned patch was merged recently and it broke our Ceilometer related functional test. There is a patch, which skip it. [1] and related bug [2] We already have a revert for this staff [3] and patch for check based on this revert [4]. [1]

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2015-12-28 Thread Rabi Mishra
> Hi there, > > The gate for telemetry projects is broken: > > https://bugs.launchpad.net/heat/+bug/1529583 > > The failure appears in Heat from what I understand: > > BadRequest: Expecting to find domain in project - the server could not > comply with the request since it is either

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

2015-12-28 Thread Julien Danjou
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