December 2021 - openstack-discuss

[all] Pending patches proposed by release bot
by Takashi Kajinami 15 Dec '21

15 Dec '21

(I'm using all tag instead of project specific tags because the list can be too long) Hi all, I noticed that many patches proposed by release bot are still pending on reviews. Because of this, I see several projects like; - unit tests are executed in old test runtimes, - release note for specific release is missing ... https://review.opendev.org/q/owner:infra-root%2540openstack.org+status:open I'd like to encourage each project to take a moment to move these forward, or abandon them if these are unnecessary. I'm trying to list up all projects affected but I might be missing some of them. So please check the above query to find anything maintained by your project. - heat - keystone - mistral - sahara - magnum - adjutant - monasca - murano - barbican - freezer - openstacksdk - zaqar - watcher - telemetry(ceilometer/aodh/panko) Thank you, Takashi

2 2

[baremetal-sig][ironic] Tue Dec 14, 2021, 2pm UTC: Metal3 Overview
by Arne Wiebalck 15 Dec '21

15 Dec '21

Dear all, The Bare Metal SIG will meet tomorrow Tue Dec 14, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Dmitry Tantsur (dtantsur) with an "Overview of Metal3" (and I hear there might be a demo even!) As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome: come along, learn from the expert and bring your questions! Cheers, Arne

1 1

[swift][tempest][kolla]
by Michal Arbet 15 Dec '21

15 Dec '21

Hello to eveyrone, Please, could someone help me with swift capabilities not working when I'm tempesting openstack test stack ? Tempest : rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest (.venv) root@ca6353106d83:/opt/refstack-client# rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest 2021-12-13 17:44:33.001 4358 INFO tempest [-] Using tempest config file /etc/tempest/tempest.conf 2021-12-13 17:44:33,839 refstack_client:518 INFO Starting Tempest test... 2021-12-13 17:44:33.839 4358 INFO refstack_client [-] Starting Tempest test... {0} setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) [0.000000s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ============================== Failed 1 tests - output below: ============================== setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) ---------------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ====== Totals ====== Ran: 1 tests in 0.0000 sec. - Passed: 0 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 0.0000 sec. TEMPEST LOG : Response - Headers: {'content-type': 'application/json', 'content-length': '114', 'www-authenticate': 'Keystone uri=" http://192.168.205.254:5000"', 'x-trans-id': 'tx815e181e33fb4854b2631-0061b7787a', 'x-openstack-request-id': 'tx815e181e33fb4854b2631-0061b7787a', 'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'connection': 'close', 'status': '401', 'content-location': ' https://api.refstack.ultimum.cloud:8080/info'} Body: b'{"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}' _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 Test from command line and from curl . /etc/kolla/refstack.sh ; curl -H "X-Auth-Token: $(openstack token issue -f value -c id)" https://api.refstack.ultimum.cloud:8080/info {"swift": {"version": "2.27.1.dev9", "strict_cors_mode": true, "policies": [{"name": "Policy-0", "aliases": "Policy-0", "default": true}], "allow_account_management": true, "account_autocreate": true, "max_file_size": 5368709122, "max_meta_name_length": 128, "max_meta_value_length": 256, "max_meta_count": 90, "max_meta_overall_size": 4096, "max_header_size": 8192, "max_object_name_length": 1024, "container_listing_limit": 10000, "account_listing_limit": 10000, "max_account_name_length": 256, "max_container_name_length": 256, "extra_header_count": 0}, "container_sync": {"realms": {}}, "bulk_upload": {"max_containers_per_extraction": 10000, "max_failed_extractions": 1000}, "bulk_delete": {"max_deletes_per_request": 10000, "max_failed_deletes": 1000}, "tempurl": {"methods": ["GET", "HEAD", "PUT", "POST", "DELETE"], "incoming_remove_headers": ["x-timestamp"], "incoming_allow_headers": [], "outgoing_remove_headers": ["x-object-meta-*"], "outgoing_allow_headers": ["x-object-meta-public-*"], "allowed_digests": ["sha1", "sha256", "sha512"]}, "ratelimit": {"account_ratelimit": 0.0, "max_sleep_time_seconds": 60.0, "container_ratelimits": [], "container_listing_ratelimits": []}, "container_quotas": {}, "account_quotas": {}, "slo": {"max_manifest_segments": 1000, "max_manifest_size": 8388608, "yield_frequency": 10, "min_segment_size": 1, "allow_async_delete": false}} Python Swiftclient : ubuntu@deploy:/opt/kolla-ansible$ . /etc/kolla/refstack.sh ; swift --os-auth-url http://192.168.205.254:5000/v3 --auth-version 3 --os-project-name refstack --os-project-domain-name default --os-username refstack --os-user-domain-name default --os-password SECRET capabilities Capabilities GET failed: http://192.168.205.254:8080/info 401 Unauthorized [first 60 chars of response] b'{"error": {"code": 401, "title": "Unauthorized", "message": ' Failed Transaction ID: txc1d8607e26eb4cd587459-0061b7791b It looks like swift client is broken, isn't it ? Or ? Maybe kolla-ansible is creating bad roles and config ? (operator_roles, reselleradmin_roel ..etc ? ) Tempest is from master Thank you very much, Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

3 5

[Diversity] D&I WG Meeting Time and IRC vs Video Poll
by Amy Marrich 15 Dec '21

15 Dec '21

Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz)

1 1

[keystone] OAuth2.0 implementation in Yoga
by Hiromu Asahina 15 Dec '21

15 Dec '21

Hi, Please, could any of the keystone core members give me some advice on this spec? https://review.opendev.org/c/openstack/keystone-specs/+/813152 We'd like to make the following points clear by the end of this year to forward the implementation. So, please kindly check it and please let me know your opinion. - OAuth2.0 scope [1]: As there are differences between OAuth2.0 scope format and the Application credentials access rule format and we haven't found a good solution to map them, we'd like to omit the implementation of the OAuth2.0 scope in Yoga. Is there any concerns? - Access policy configuration: - Which one is appropriate? (i) End-users can use the OAuth2.0 API if they have permission for the OAuth2.0 API even if they don't have permission for the Application credentials API (ii) End-users can use the OAuth2.0 API only if they have permission for both the OAuth2.0 API and the Application credentials API. - API endpoint: - Which one is appropriate? (i) `/identity/v3/auth/OS-OAUTH2/<user_id>/clients` (ii) `/identity/v3/users/{user_id}/OS-AUTH2/clients` (iii) other [1] https://datatracker.ietf.org/doc/html/rfc6749#page-23 Thanks, Hiromu Asahina (h_asahina)

1 0

[nova] Spawning instance that will do PXE booting
by Thomas Goirand 15 Dec '21

15 Dec '21

Hi, In order to test OCI [1] within OpenStack itself, I would need my instances to do PXE booting. This would be with something like this on the qemu command line: qemu-system-x86_64 -boot n I believe this would also mean setting-up network cards that can do PXE booting, like the e1000, which Qemu supports. If that is possible, then I would setup DHCP + tftp-hpa on another instance, wired on the same private network. Your thoughts? Is this possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

8 18

[all] testtools and support for Python 3.10 (error du to deprecation of distutils)
by Thomas Goirand 14 Dec '21

14 Dec '21

Hi, When I try to build rally-openstack, I get this, in the test discovery: /usr/lib/python3/dist-packages/rally/common/cfg.py:19: in <module> from oslo_config import fixture # noqa /usr/lib/python3/dist-packages/oslo_config/fixture.py:18: in <module> import fixtures /usr/lib/python3/dist-packages/fixtures/__init__.py:81: in <module> from fixtures.fixture import ( /usr/lib/python3/dist-packages/fixtures/fixture.py:34: in <module> from fixtures.callmany import ( /usr/lib/python3/dist-packages/fixtures/callmany.py:31: in <module> MultipleExceptions = try_import( /usr/lib/python3/dist-packages/testtools/helpers.py:30: in try_import __import__(module_name) /usr/lib/python3/dist-packages/testtools/__init__.py:99: in <module> from testtools.distutilscmd import TestCommand /usr/lib/python3/dist-packages/testtools/distutilscmd.py:7: in <module> from distutils.core import Command /usr/lib/python3.10/distutils/__init__.py:19: in <module> warnings.warn(_DEPRECATION_MESSAGE, E DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives This warning makes it impossible to discover rally-openstack tests, because of the imports here: https://github.com/testing-cabal/testtools/blob/master/testtools/distutilsc… Can someone work on removing distutils support from Testtools? Or is there a way to trick pytest to not fail? Help would be greatly appreciated here. Cheers, Thomas Goirand (zigo)

4 8

bug deputy report (week of Dec 6)
by Akihiro Motoki 14 Dec '21

14 Dec '21

Hi, I was a bug deputy last week. Here is a summary of last week. Two needs-attention bugs need what neutron should behave, so they need more investigation. Two OVN bugs and one gate-failure bug also need assignees and investigations. Thanks, Akihiro Motoki (amotoki) # Needs attention - https://bugs.launchpad.net/neutron/+bug/1953478 Resize and shelve server fails in the multinode CI jobs intemittent It was reported to nova by slawek, but gibi moved it to neutron as there is a question on when neutron send vif-plugged event to nova. We need to clarify when the vif-plugged event is sent and what is the expected behavior. - https://bugs.launchpad.net/neutron/+bug/1954384 Neutron doesn't use set dns-domain for Nova instance It would be nice if folks familiar with DNS integration can look into it. # OVN https://bugs.launchpad.net/neutron/+bug/1953510 neutron_ovn_metadata_agent doesn`t work after reconnect to new OVN Southbound leader DB https://bugs.launchpad.net/neutron/+bug/1953295 neutron-ovn-metadata-agent AttributeError: 'MetadataAgent' object has no attribute 'sb_idl' # Gate failures https://bugs.launchpad.net/neutron/+bug/1953479 Timeout in the scenario jobs' execution # Assigned https://bugs.launchpad.net/neutron/+bug/1953716 Improve message in the NetworkInUse exception # In Progress https://bugs.launchpad.net/neutron/+bug/1954316 In VXLAN interface creation, we must provide always a device https://bugs.launchpad.net/neutron/+bug/1954662 Quota driver "DbQuotaNoLockDriver" can lock when removing the expired reservations https://bugs.launchpad.net/neutron/+bug/1953480 Agents API test failed due to not expected "alive" status of the agent

1 0

[wallaby][ovn][Open vSwitch] HA for OVN DB servers using pacemaker
by Faisal Sheikh 14 Dec '21

14 Dec '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic - compute node1 172.16.30.1 - compute node2 172.16.30.3 - controller-khi01/Network node/Primary ovs-db IP 172.16.30.46 - backup ovs-db 172.16.30.47 I want to run OVSDB server to run in Active/Passive mode. Active OVSDB-server is on node "controller-khi01" and Passive OVSDB-server is on "controller02-khi01". I have setup Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovn-db server. You can see the "pcs status" output below. But I am unable to replicate database state between primary and backup OVSDB server. If i execute "ovsdb-server --sync-from=server" command, getting below error. root@controller-khi01# ovsdb-server --sync-from=172.16.30.47 2021-12-14T09:16:29Z|00001|lockfile|WARN|/var/lib/openvswitch/.conf.db.~lock~: cannot lock file because it is already locked by pid 14121 ovsdb-server: I/O error: /etc/openvswitch/conf.db: failed to lock lockfile (Resource temporarily unavailable) root@controller-khi01# pcs status Cluster name: cluster1 Cluster Summary: * Stack: corosync * Current DC: controller-khi01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Tue Dec 14 07:53:06 2021 * Last change: Tue Dec 14 06:16:21 2021 by hacluster via crmd on controller02-khi01 * 2 nodes configured * 3 resource instances configured Node List: * Online: [ controller-khi01 controller02-khi01 ] Full List of Resources: * Clone Set: ovndb_servers-clone [ovndb_servers] (promotable): * Masters: [ controller-khi01 ] * Slaves: [ controller02-khi01 ] * ovn-virtual-ip (ocf::heartbeat:IPaddr2): Started controller-khi01 Failed Resource Actions: * ovndb_servers_monitor_10000 on controller02-khi01 'master' (8): call=17, status='complete', exitreason='', last-rc-change='2021-12-14 06:48:26Z', queued=0ms, exec=0ms Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

[tripleo] Initial plans around stable/wallaby branch on CentOS Stream 9
by Chandan Kumar 14 Dec '21

14 Dec '21

Hello, The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9. During adding the support of CentOS Stream 9 for tripleo master, we have added lots of patches for example: * tripleo-common: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * tripleo-heat-templates: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started. In order to avoid that, we are coming with following plan: - Pick the major change and backport that one and add all the remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511 - Make sure these backported changes passed on CentOS-8 CI jobs - Once the RDO CS9 wallaby packages are available, Start bootstrapping the container and Image build job on CS9 via testproject. Let us know your thoughts around this. Thanks, Chandan Kumar

3 3