Open Stack

The issue triggered by gabbi 2.5.0 was temporarily resolved by pinning it
to 2.4.0 .
The gate is unblocked, I believe (We found an issue with a functional job
for stable/train which is being fixed now).
We can remove that pin once the issue with urllib3 is resolved.

> Should we consider using only https for endpoint access in the future?
Maybe ? But this is a separate topic, IMHO, and I don't have any strong
opinion about this.
There are several devstack plugins (like heat, aodh, ...) which don't
support
setting up tls-proxy for https endpoints yet and we need to fix each plugin
if we take this direction.


On Tue, Jan 18, 2022 at 10:21 PM Martin Kopec <mkopec at redhat.com> wrote:

> Thank you Takashi for looking into this.
>
> Should we consider using only https for endpoint access in the future?
>
> On Tue, 18 Jan 2022 at 09:35, Takashi Kajinami <tkajinam at redhat.com>
> wrote:
>
>> I have opened an issue for urllib3[1], too, and created a PR to discuss a
>> potential fix.
>>  [1] https://github.com/urllib3/urllib3/issues/2534
>>
>> Because it'd take some time until we get feedback from these two
>> communities,
>> I've proposed a change to pin gabbi to 2.4.0[2].
>>  [2] https://review.opendev.org/c/openstack/requirements/+/825044
>>
>> The issue might affect other projects using gabbi as well, unless https,
>> instead of http,
>> is used for endpoint access.
>>
>>
>> On Tue, Jan 18, 2022 at 11:42 AM Takashi Kajinami <tkajinam at redhat.com>
>> wrote:
>>
>>> I've looked into this but it seems the following error was actually
>>> caused by the latest release of gabbi(2.5.0).
>>>  TypeError: __init__() got an unexpected keyword argument
>>> 'server_hostname'
>>>
>>> I've reported that issue to gabbi in [1] but if my observation is
>>> correct the problem should be
>>> fixed in urllib3 which gabbi is dependent on.
>>>  [1] https://github.com/cdent/gabbi/issues/309
>>>
>>> On Tue, Jan 18, 2022 at 2:34 AM Martin Kopec <mkopec at redhat.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> most of the tests of heat-tempest-plugin have started failing. We
>>>> noticed that in interop [1], however, we reproduced that in the project's
>>>> gates as well [2].
>>>>
>>>> I suspect it might be an issue with the new gabbi package - there has
>>>> been an update recently.
>>>> Could you please have a look.
>>>>
>>>> [1]
>>>> https://review.opendev.org/c/openinfra/ansible-role-refstack-client/+/824832
>>>> [2] https://review.opendev.org/c/openstack/heat-tempest-plugin/+/823794
>>>>
>>>> Thank you,
>>>> --
>>>> Martin Kopec
>>>> Senior Software Quality Engineer
>>>> Red Hat EMEA
>>>>
>>>>
>>>>
>>>>
>
> --
> Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220119/efe30d01/attachment-0001.htm>