February 2022 - openstack-discuss

[requirements] The version of zeroconf in upper constraints no longer supports python3.6
by William Szumski 01 Feb '22

01 Feb '22

The zeroconf package seems to have dropped support for python3.6 since 0.38.0, see: https://github.com/jstasiak/python-zeroconf#0380. We currently have 0.38.1 in upper-constraints. My understanding was that the yoga release would still support python3.6. This is important for RHEL8 based distributions that only ship python3.6. Do we need to constrain zeroconf to a version <=0.37.0?

7 6

[infra] Issue with the new pip
by Radosław Piliszek 01 Feb '22

01 Feb '22

Hi! It seems that the new pip is breaking on infra's package indices. Several jobs crash with: """ ValueError: HTML doctype missing or incorrect. Expected <!DOCTYPE html>. If you believe this error to be incorrect, try passing the command line option --use-deprecated=html5lib and please leave a comment on the pip issue at https://github.com/pypa/pip/issues/10825. [0m [31m """ Example from kolla: https://zuul.opendev.org/t/openstack/build/e1bab19dd7c1487e93afeb67284a695e Example from manila: https://zuul.opendev.org/t/openstack/build/984ed9f10f0845ceba59b573e25bbb87 -yoctozepto

4 6

[TripleO] Meeting Cancelled for February 1
by James Slagle 01 Feb '22

01 Feb '22

Hello TripleO'ers, with no items on the agenda for today's meeting, let's go ahead and cancel it. Please reach out on IRC if you need prioritized reviews. Thanks. -- -- James Slagle --

1 0

[magnum] dropping mesos code
by Mohammed Naser 01 Feb '22

01 Feb '22

Hi there, Does it make sense for us to drop the Mesos driver code from the code base? I don't know of anyone that actually uses it and I believe it's likely not been tested for years. Mohammed -- Mohammed Naser VEXXHOST, Inc.

4 5

[nova][placement] Openstack only building one VM per machine in cluster, then runs out of resources
by Eugen Block 01 Feb '22

01 Feb '22

Hi all, I would like to follow up on a discussion from last year [1] since the issue is still present. In a fresh Victoria deployment we faced the same issue and my colleague tracked it down to a reoccuring issue within MariaDB [2]. Quoting from his response to a different thread [3]: ---snip--- MariaDB is version 10.6.5. When running placement API in debug mode, its log reveals a message like "Over capacity for VCPU on resource provider . Needed: 1, Used: 4118, Capacity: 768.0" but checking the entries in the placement db / allocations table shows that "4118" is the sum of all resources for the resource provided, not only for the CPU class. The problem results from errors in the DBMS handling the "outer join" with a subquery while retrieving the currently allocated resources. ---snip--- We found a workaround for this environment, but I wanted to bring some more attention to this, hoping that this will be fixed in MariaDB. Regards, Eugen [1] https://lists.openstack.org/pipermail/openstack-discuss/2021-July/023430.ht… [2] https://jira.mariadb.org/browse/MDEV-25714 [3] https://serverfault.com/questions/1064579/openstack-only-building-one-vm-pe…

2 1