Thanks Eric. Shipping it.
On Sat, Jul 22, 2017 at 2:28 PM, Eric Fried wrote:
> dims-
>
> SHA was good; just hadn't merged yet. It has now. All greens.
> Assuming lbragstad/morgan/mordred are on board, let's do it.
>
> Thanks,
> efried
>
> On 07/22/2017 10
dims-
SHA was good; just hadn't merged yet. It has now. All greens.
Assuming lbragstad/morgan/mordred are on board, let's do it.
Thanks,
efried
On 07/22/2017 10:06 AM, Davanum Srinivas wrote:
> Lance,
>
> Ack. SHA needs to be fixed (https://review.opens
Lance,
Ack. SHA needs to be fixed (https://review.openstack.org/#/c/486279/)
Thanks,
Dims
On Sat, Jul 22, 2017 at 10:24 AM, Lance Bragstad wrote:
> Thanks Dims,
>
> Looks like Morgan and Monty have it working through the gate now.
>
> On Sat, Jul 22, 2017 at 7:26 AM, Davanum Srinivas wrote:
>>
Thanks Dims,
Looks like Morgan and Monty have it working through the gate now.
On Sat, Jul 22, 2017 at 7:26 AM, Davanum Srinivas wrote:
> Lance, other keystone cores,
>
> there's a request for 3.0.1, but one of the reviews that it needs is
> not merged yet
>
> https://review.openstack.org/#/c/4
Lance, other keystone cores,
there's a request for 3.0.1, but one of the reviews that it needs is
not merged yet
https://review.openstack.org/#/c/486231/
Thansk,
Dims
On Fri, Jul 21, 2017 at 11:40 PM, Lance Bragstad wrote:
>
>
> On Fri, Jul 21, 2017 at 9:39 PM, Monty Taylor wrote:
>>
>> On 0
On Fri, Jul 21, 2017 at 9:39 PM, Monty Taylor wrote:
> On 07/22/2017 07:14 AM, Lance Bragstad wrote:
>
>> After a little head scratching and a Pantera playlist later, we ended up
>> figuring out the main causes. The failures can be found in the gate [0].
>> The two failures are detailed below:
>>
On 07/22/2017 07:14 AM, Lance Bragstad wrote:
After a little head scratching and a Pantera playlist later, we ended up
figuring out the main causes. The failures can be found in the gate [0].
The two failures are detailed below:
1.) Keystoneauth version 3.0.0 added a lot of functionality and mig
After a little head scratching and a Pantera playlist later, we ended up
figuring out the main causes. The failures can be found in the gate [0].
The two failures are detailed below:
1.) Keystoneauth version 3.0.0 added a lot of functionality and might
return a different url depending on discovery
The patch to blacklist version 3.0.0 is working through the moment [0].
We also have a WIP patch proposed to handled the cases exposed by
keystonemiddleware [1].
[0] https://review.openstack.org/#/c/486223/
[1] https://review.openstack.org/#/c/486231/
On 07/21/2017 03:58 PM, Lance Bragstad wrot
We have a patch up to blacklist version 3.0.0 from global-requirements
[0]. We're also going to hold bumping the minimum version of
keystoneauth until we have things back to normal [1].
[0] https://review.openstack.org/#/c/486223/
[1] https://review.openstack.org/#/c/486160/1
On 07/21/2017 03:00
I started noticing some trivial changes failing in the
keystonemiddleware gate [0]. The failures are in tests that use the
keystoneauth1 library (8 tests are failing by my count), which we
released a new version of yesterday [1]. I've proposed a patch to
blacklist keystoneauth1 3.0.0 from keystonem
11 matches
Mail list logo
