- openstack-discuss - lists.openstack.org

[infra][stable] Request for Designate stable core status
by Michael Johnson 25 Mar '21

25 Mar '21

I would like to request stable core status for the Designate repositories. As PTL I am currently unable to approve even the release bot patches for some Designate stable branches[1]. I have been a stable reviewer for Octavia for years and if there are concerns about my stable policy track record I hope that my work on Octavia would highlight my respect for the stable release policy. Thanks, Michael [1] https://review.opendev.org/c/openstack/designate-dashboard/+/783056

2 1

[tripleo][ci] tripleo gate is hung
by Wesley Hayutin 25 Mar '21

25 Mar '21

Greetings, https://zuul.openstack.org/status top of the gate patch is hung 774500,1 Infra is looking into it. See #openstack-infra for details Thanks fungi!!

2 2

[qa][ptg] Xena PTG
by Martin Kopec 25 Mar '21

25 Mar '21

Hello, we signed up for the following slots [1] at Cactus room: * Mon Apr. 19th 13 - 15 UTC (2 slots) * Tue Apr. 20th 13 - 14 UTC (1 slot) * Wed Apr. 21th 13 - 14 UTC (1 slot) The PTG etherpad [2] with the topics we have so far. If you have something else you wanna discuss, feel free to add it to the agenda [2]. [1] https://etherpad.opendev.org/p/qa-xena-ptg [2[ https://etherpad.opendev.org/p/qa-xena-ptg See you at PTG, -- *Martin Kopec*

1 0

[policy pop-up] Xena PTG planning
by Ghanshyam Mann 25 Mar '21

25 Mar '21

Hello Everyone, We have booked 2 hrs slot for the policy popup team in the Xena virtual PTG. The time for the slot is 15.00-17.00 UTC Monday, April 19 (2 hours; Essex Room). I have created the etherpad to collect the discussion point. Please add the topic you would like to discuss - https://etherpad.opendev.org/p/policy-popup-xena-ptg We request more and more projects to participate in this and discuss the various queries or plan to switch to the new policy in a single place instead of duplicating the discussion in each project slot. -gmann & lbragstad

1 0

[ops][victoria] DNS for Tenants
by DHilsbos＠performair.com 25 Mar '21

25 Mar '21

All; How do we provide DNS services to tenant networks? We're running Victoria, and have Designate installed and configured, but it doesn't seem to have a presence on the tenant networks. I assume if the instance can route to an IP on the network node then the installed Bind can be used. I'd rather not have to deal with this, however. I would like the DNS to operate in a relay fashion to our previously configured DNS servers, though I assume that standard Bind configuration for relay should take care of this. Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 3

[TripleO] Xena PTG is coming 19 April
by Marios Andreou 25 Mar '21

25 Mar '21

Hello tripleo friends o/ It's PTG time again \o/ and I have started reaching out to/harassing folks this week about topics. I want to send a *HUGE* thanks to all the usual suspects who have already proposed some sessions. Like last time let's collect all the topics into the topic etherpad at [1] and then around Monday 5th April or so we can start to work out the schedule (2 weeks before PTG). I have reserved 1300-1700 UTC on Monday/Tue/Wed/Thu as noted there [2] - we may not need all of those days it depends how many sessions we will have proposed. So over the next few days please think about the Wallaby or Xena tripleo related things you'd like to discuss/provide updates on/socialise with the wider TripleO team. Then go add them into [1] using the template there (Topic/Description/Etherpad Link/Proposer). BUT before you do any of that make sure you go and register for PTG at [3]. I hope we get a great turn out like last time! regards, marios [1] https://etherpad.opendev.org/p/tripleo-xena-topics [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020953.ht… [3] https://april2021-ptg.eventbrite.com/

1 0

[telemetry] OpenStack Telemetry Xena PTG planning
by Matthias Runge 25 Mar '21

25 Mar '21

Hi there, The next virtual PTG is getting near very quickly. If you haven't registered yet, please do so as soon as possible[1]. We have signed up for slots on Tuesday and Wednesday April 20 and 21 for the slots between 13 and 16 UTC. If there is anything you would like to talk about or something you'd like to address/to work on, please feel free to add it to the etherpad[2]. Thank you and see you there! Matthias [1] https://april2021-ptg.eventbrite.com/ [2] https://etherpad.opendev.org/p/telemetry-xena-ptg

1 0

[oslo.db][Zaqar] test_models_sync failed because oslo.db raise "AttributeError: can't set attribute"
by hao wang 25 Mar '21

25 Mar '21

Hi, There is an issue about test_models_sync test when openstack-tox-lower-constraints job running that I can't figure out why it's here, could anyone help me about this? zaqar.tests.unit.storage.sqlalchemy_migration.test_migrations.TestMigrationsMySQL.test_models_sync [0.306333s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/oslo_db/sqlalchemy/test_base.py", line 178, in setUp self.useFixture( File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testtools/testcase.py", line 760, in useFixture reraise(*exc_info) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testtools/_compat3x.py", line 16, in reraise raise exc_obj.with_traceback(exc_tb) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testtools/testcase.py", line 735, in useFixture fixture.setUp() File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/oslo_db/sqlalchemy/test_base.py", line 65, in setUp testresources.setUpResources( File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testresources/__init__.py", line 786, in setUpResources setattr(test, resource[0], resource[1].getResource(result)) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testresources/__init__.py", line 522, in getResource self._setResource(self._make_all(result)) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testresources/__init__.py", line 551, in _make_all dependency_resources[name] = resource.getResource() File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testresources/__init__.py", line 522, in getResource self._setResource(self._make_all(result)) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/testresources/__init__.py", line 552, in _make_all resource = self.make(dependency_resources) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/oslo_db/sqlalchemy/provision.py", line 133, in make url = backend.provisioned_database_url(db_token) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/oslo_db/sqlalchemy/provision.py", line 337, in provisioned_database_url return self.impl.provisioned_database_url(self.url, ident) File "/home/zuul/src/opendev.org/openstack/zaqar/.tox/lower-constraints/lib/python3.8/site-packages/oslo_db/sqlalchemy/provision.py", line 498, in provisioned_database_url url.database = ident AttributeError: can't set attribute There is the test log: https://zuul.opendev.org/t/openstack/build/57eb103379b144abaa2517d41ef67610…

3 2

[kolla-ansible][Neutron]Limiting bandwidth per Project/Domain/Tenant?
by Adam Tomas 25 Mar '21

25 Mar '21

Hi, Is there any way to limit bandwidth per project, domain or tenant? According to the neutron documentation limit can be set per port (router,FIP etc.) but what if I need to limit whole project (which can have multiple routers, FIPs, etc.) - incoming and outgoing traffic? Best regards, Adam

2 1

[neutron][stable] neutron-lib stable branches core reviewers
by Slawek Kaplonski 25 Mar '21

25 Mar '21

Hi, I just noticed that neutron-lib project has got own group "neutron-lib-stable-maint" which has +2 powers in neutron-lib stable branches [1]. As I see now in gerrit that group don't have any members. Would it be maybe possible to remove that group and add "neutron-stable-maint" to the neutron-lib stable branches instead? If yes, should I simply propose patch to change [1] or is there any other way which I should do it? [1] https://github.com/openstack/project-config/blob/master/gerrit/acls/opensta… -- Slawek Kaplonski Principal Software Engineer Red Hat

4 5

Re: [glance][openstack-ansible] Snapshots disappear during saving
by Oliver Wenz 25 Mar '21

25 Mar '21

Hi Dmitriy, thanks for your answer! I tried inserting the options into user_variables.yml and running the installation playbooks again but glance still shows 'Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token.' and the snapshot keeps disappearing. In addition, I'm seeing the following swift error: Mar 25 11:19:56 infra1-swift-proxy-container-27169fa7 proxy-server[90]: Pipeline was modified. New pipeline is "catch_errors gatekeeper healthcheck proxy-logging cache listing_formats container_sync bulk tempurl ratelimit authtoken keystoneauth staticweb copy container-quotas account-quotas slo dlo versioned_writes proxy-logging proxy-server". Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: Starting Keystone auth_token middleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "use_stderr" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "bind_ip" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "bind_port" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "workers" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "user" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "log_name" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "auth_url" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "project_domain_id" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "user_domain_id" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "project_name" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "username" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "password" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "revocation_cache_time" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: STDERR: The option "__name__" is not known to keystonemiddleware Mar 25 11:19:57 infra1-swift-proxy-container-27169fa7 proxy-server[90]: AuthToken midd Kind regards Oliver > Oh, I have a guess what this might actually be. During snapshot upload process > user token that is used for the upload might get expired. If that's the case, > following changes in user_variables might help to resolve the issue: > > glance_glance_api_conf_overrides: > keystone_authtoken: > service_token_roles_required: True > service_token_roles: service >

1 0

Re: [glance][openstack-ansible] Snapshots disappear during saving
by Oliver Wenz 25 Mar '21

25 Mar '21

I manually set the fallocate_reserve values to 1% on the swift host and the services don't show errors anymore (I also tried with higher values than 1%). However, when trying to take the snapshot it still disappears and I still get the following for the swift-proxy service: Mar 25 08:55:53 infra1-swift-proxy-container-27169fa7 proxy-server[84]: Client disconnected without sending last chunk (txn: tx5590a6d463f645caaaf67-00605c4fe4) (client_ip: 192.168.110. 106) 192.168.110.106 is the IP of eth1 on my glance container so maybe that indicates that this is a glance problem after all? Because of the following log from the glance-api service: Mar 25 08:54:59 infra1-glance-container-99614ac2 glance-wsgi-api[6177]: 2021-03-25 08:54:59.046 6177 INFO glance.api.v2.image_data [req-42a0c48b-895c-4776-9e9c-586eb596b540 956806468e9f43dbaad1807a5208de52 ebe0fe5f3893495e82598c07716f5d45 - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. Mar 25 08:55:54 infra1-glance-container-99614ac2 uwsgi[6177]: Thu Mar 25 08:55:54 2021 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2/images/16f50adc-ebec-4812-96bd-2bbf6d2014b5/file (ip 192.168.110.214) !!! I checked the logs on the compute host (192.168.110.214) where the instance I'm trying to take a snapshot of is running and I found this in the logs: Mar 25 08:55:15 bc1bl14 nova-compute[2252]: 2021-03-25 08:55:15.050 2252 INFO nova.virt.libvirt.imagecache [req-24323bc9-65bc-47b6-8ef1-81fc88b2b267 - - - - -] image c27e2055-8c3c-49d7-9c12-44999b1e7e0f at (/var/lib/nova/instances/_base/4102ded7765e7306705acece9b2b1c4e88087478): checking Mar 25 08:55:15 bc1bl14 nova-compute[2252]: 2021-03-25 08:55:15.052 2252 INFO nova.virt.libvirt.imagecache [req-24323bc9-65bc-47b6-8ef1-81fc88b2b267 - - - - -] image e73512b8-7099-4691-aa48-966aa35b59ff at (/var/lib/nova/instances/_base/573a84fb0420a038702c616b848169b07e2bb7f3): checking Mar 25 08:55:15 bc1bl14 nova-compute[2252]: 2021-03-25 08:55:15.759 2252 INFO nova.virt.libvirt.imagecache [req-24323bc9-65bc-47b6-8ef1-81fc88b2b267 - - - - -] Active base files: /var/lib/nova/instances/_base/4102ded7765e7306705acece9b2b1c4e88087478 /var/lib/nova/instances/_base/573a84fb0420a038702c616b848169b07e2bb7f3 Mar 25 08:55:57 bc1bl14 nova-compute[2252]: 2021-03-25 08:55:57.102 2252 INFO nova.compute.manager [req-42a0c48b-895c-4776-9e9c-586eb596b540 956806468e9f43dbaad1807a5208de52 ebe0fe5f3893495e82598c07716f5d45 - default default] [instance: 46d45c54-eba1-4624-8e5a-19dc157484ae] Successfully reverted task state from image_uploading on failure for instance. Mar 25 08:55:57 bc1bl14 nova-compute[2252]: 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server [req-42a0c48b-895c-4776-9e9c-586eb596b540 956806468e9f43dbaad1807a5208de52 ebe0fe5f3893495e82598c07716f5d45 - default default] Exception during message handling: glanceclient.exc.HTTPInternalServerError: HTTP 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 2478, in snapshot 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server metadata['location'] = root_disk.direct_snapshot( 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/virt/libvirt/imagebackend.py", line 452, in direct_snapshot 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise NotImplementedError(_('direct_snapshot() is not implemented')) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server NotImplementedError: direct_snapshot() is not implemented 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/exception_wrapper.py", line 76, in wrapped 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server _emit_exception_notification( 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/six.py", line 703, in reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise value 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 188, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server LOG.warning("Failed to revert task state for instance. " 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/six.py", line 703, in reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise value 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 159, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/utils.py", line 1434, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 216, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server compute_utils.add_instance_fault_from_exc(context, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/six.py", line 703, in reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise value 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 205, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 236, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server compute_utils.delete_image( 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/six.py", line 703, in reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise value 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 232, in decorated_function 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return function(self, context, image_id, instance, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 3908, in snapshot_instance 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self._snapshot_instance(context, image_id, instance, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/compute/manager.py", line 3941, in _snapshot_instance 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self.driver.snapshot(context, instance, image_id, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 2549, in snapshot 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server self._image_api.update(context, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 1247, in update 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return session.update(context, image_id, image_info, data=data, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 696, in update 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server _reraise_translated_image_exception(image_id) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 1035, in _reraise_translated_image_exception 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise new_exc.with_traceback(exc_trace) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 694, in update 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server image = self._update_v2(context, sent_service_image_meta, data) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 713, in _update_v2 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server image = self._upload_data(context, image_id, data) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 589, in _upload_data 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server utils.tpool_execute(self._client.call, 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/utils.py", line 694, in tpool_execute 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server eventlet.tpool.execute(func, *args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/eventlet/tpool.py", line 129, in execute 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server six.reraise(c, e, tb) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/six.py", line 703, in reraise 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise value 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/eventlet/tpool.py", line 83, in tworker 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server rv = meth(*args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/nova/image/glance.py", line 192, in call 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server result = getattr(controller, method)(*args, **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/glanceclient/common/utils.py", line 600, in inner 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return RequestIdProxy(wrapped(*args, **kwargs)) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/glanceclient/v2/images.py", line 289, in upload 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server resp, body = self.http_client.put(url, headers=hdrs, data=body) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/keystoneauth1/adapter.py", line 404, in put 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return self.request(url, 'PUT', **kwargs) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/glanceclient/common/http.py", line 380, in request 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server return self._handle_response(resp) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server File "/openstack/venvs/nova-22.1.0/lib/python3.8/site-packages/glanceclient/common/http.py", line 120, in _handle_response 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server raise exc.from_response(resp, resp.content) 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server glanceclient.exc.HTTPInternalServerError: HTTP 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. 2021-03-25 08:55:57.106 2252 ERROR oslo_messaging.rpc.server Any hints where the error might be coming from are much appreciated! Kind regards, Oliver

2 1

[neutron] Drivers meeting agenda for 26.03.2021
by Slawek Kaplonski 25 Mar '21

25 Mar '21

Hi, Agenda for tomorrow's drivers meeting is at [1]. We have 2 new RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1920065 - Automatic rescheduling of BGP speakers on DrAgents Patch for that is already proposed too https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/780675 * https://bugs.launchpad.net/neutron/+bug/1921126 -[RFE] Allow explicit management of default routes Spec for that one is also proposed already https://review.opendev.org/c/openstack/neutron-specs/+/781475 Please read through them so we can discuss them tomorrow on the meeting. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[sdk][cli] OpenStackSDK/CLI Xena PTG
by Artem Goncharov 25 Mar '21

25 Mar '21

Hi, all The Xena PTG is scheduled for Apr 19-23 (15:00-17:00 UTC) We are organizing 2 hours in Wed 12 Apr for SDK/CLI project talks. Please add your PTG topics in the etherpad: https://etherpad.opendev.org/p/xena-ptg-sdk-cli <https://etherpad.opendev.org/p/xena-ptg-sdk-cli> P.S. And don’t forget to register for PTG participation Regards, Artem (gtema)

1 0

[horizon] [ptg] Xena PTG
by vishal manchanda 24 Mar '21

24 Mar '21

Hi everyone, As discussed in yesterday horizon weekly meeting and based on the doodle poll I have booked available slots for Horizon Xena PTG. Please find below the schedule for the same: Monday April 19, 14:00 - 17:00 UTC Tuesday April 20, 05:00 - 07:00 UTC and 16:00 - 17:00 UTC Wednesday April 21, 16:00 - 17:00 UTC I have also created Etherpad to collect topics for ptg discussion [1]. Feel free to add your topics. Please Let me know and Ivan in case you have any topics to discuss and above schedule doesn't work for you and We will see how to manage that. Thank you, Vishal Manchanda(irc: vishalmanchanda) [1] https://etherpad.opendev.org/p/xena-ptg-horizon-planning

1 0

[tripleo][ansible] Openstack Ansible collections (modules) Xena PTG
by Sagi Shnaidman 24 Mar '21

24 Mar '21

Hi, all The Xena PTG is scheduled for Apr 19-23 We are organizing 2 hours in Wed 12 Apr for Openstack Ansible collections project talks.[1] Please add your PTG topics in the etherpad: https://etherpad.opendev.org/p/xena-ptg-os-ansible-collections [1] https://opendev.org/openstack/ansible-collections-openstack Thanks -- Best regards Sagi Shnaidman

1 0

[kolla] Plan to deprecate and finally drop the chrony container
by Radosław Piliszek 24 Mar '21

24 Mar '21

Hello Fellow OpenStackers interested in Kolla's way. The topic should be pretty self-explanatory but let me provide the details and background. We are currently working on the Wallaby release and, since we are cycle-trailing, it is the right moment for us to reflect upon the various cleanup plans we had (and have). One of those is the drop of the chrony container. Chrony serves the time synchronization purpose which is required for healthy operations (I hope I don't need to explain this point further, time sync is essential for most services nowadays). It is still deployed by default by Kolla Ansible. The point is, most default (even minimal ones) host OS installations come with some form of NTP client, be it chrony, ntpd, timesyncd or whatever else there is. :-) This applies also to provisioning solutions like MAAS or Foreman. And Kolla Ansible actually stands on its head to detect and disable those to avoid multiple time sync daemons hell as it may disrupt normal operations (mostly due to having different time sources but also due to different compensation algorithms [or rather just their actual configuration] and the fact that each tool assumes to be the only source of time changes). We seem to have placed a relatively sane precheck to detect this but effective disabling may prove tricky, especially since it is very easy to get it installed at any point. The NTP client is considered a very basic service these days. It also seems that several users known to us do not use the chrony container and instead orchestrate timesync elsewhere. Hence, our current plan is to: 1) Deprecate the chrony container in the Wallaby cycle. - in Kolla Ansible this would mean also warning users that they use it and defaulting to not using it (with docs and a reno); docs would suggest an Ansible way to coordinate timesync - in Kolla docs and a reno 2) Drop the chrony container from both the places I know Kayobe (the "highest-level" member of the Kolla project) is planning to incorporate timesync handling by external Ansible role means so their users should be covered. Please let us know if you have any comments on the plan above. Or generally any suggestions you would like us to hear. Cheers! -yoctozepto

1 1

[VOLUNTEER NEEDED] Wallaby Release Demo
by helena＠openstack.org 24 Mar '21

24 Mar '21

Hi everyone! We are closely approaching the Wallaby release (Yay!) and I would like to put together a demo video for the OpenInfra YouTube channel. The demo videos we have for Havana [1] and Juno [2] are our top-performing videos of all time. I am wondering if there is anyone in the community who would like to film a Wallaby demo for the channel. I would need the video by April 9th. In addition to the demo video, we will also have a community meeting. I will be reaching out to ptls soon on content for this. [1] [ https://www.youtube.com/watch?v=vm7aHJtQMQE ]( https://www.youtube.com/watch?v=vm7aHJtQMQE ) [2] [ https://www.youtube.com/watch?v=TgPTjrf1y0A ]( https://www.youtube.com/watch?v=TgPTjrf1y0A ) Cheers, Helena Open Infrastructure Foundation helens(a)openstack.org

1 0

[nova] Cannot use --fields in one of our headnodes
by Mauricio Tavares 24 Mar '21

24 Mar '21

Easy question of the day: One of our headnodes is barking when I use --fields with nova. nova list --all --fields=host,instance_name,status ERROR (TypeError): '<' not supported between instances of 'str' and 'NoneType' This works fine with the other headnodes, and all 3 are supposed to be the same (hardware, software). Would that indicate a bad installation or something else? Where should I be looking for answers?

2 1

[tripleo][ci] quay.io is down
by Wesley Hayutin 24 Mar '21

24 Mar '21

0/ We can't have nice things. quay.io is currently down. quay.io is utilized for non-tripleo containers like grafana, etc. This has caused jobs to fail. We'll keep you posted. Thanks!

4 5

[vpnaas-neutron][Victoria] - could not load neutron_vpnaas
by Luke Camilleri 24 Mar '21

24 Mar '21

We are configuring Neutron's vpnaas extension and although the guide seems to be quite short, it looks like that there are some dependencies that we are not aware of since we are receiving this error when we start the neutron server: WARNING stevedore.named [req-dca2e9a8-1799-45c7-9380-f247510af7e5 - - - - -] Could not load neutron_vpnaas.services.vpn.device_drivers.libreswan_ipsec.LibreSwanDriver We have followed this guide https://docs.openstack.org/neutron/latest/admin/vpnaas-scenario.html and before that we have also installed the below packages from the repos: openstack-neutron-vpnaas-17.0.0-2.el8.noarch libreswan-3.32-7.el8_3.x86_64 our config files are the below: l3_agent.ini [DEFAULT] interface_driver = linuxbridge debug = true [AGENT] extensions = vpnaas [vpnagent] vpn_device_driver = neutron_vpnaas.services.vpn.device_drivers.libreswan_ipsec.LibreSwanDriver neutron_vpnaas.conf [service_providers] service_provider = VPN:openswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default vpn_agent.ini is empty since the guide documents the changes in the l3_agent.ini file in neutron.conf we have also added the below: service_plugins = router,vpnaas At this point, my main question would be, is VPNaaS supported with linux bridge or just with OpenvSwitch? Thanks in advance

1 0

[cyborg] No meeting tomorrow March 25th
by Wang, Xin-ran 24 Mar '21

24 Mar '21

Hi guys, The Cyborg IRC meeting tomorrow has been cancelled. We will meet again at the regular time next week. Please feel free to contact the team on IRC channel, or send out mail here. Thanks for your understanding. Thanks, Xin-Ran

1 0

[kolla] Feedback request: removing OracleLinux support
by Stefan Kelber 24 Mar '21

24 Mar '21

Hello, i just found this thread, in the situation to apparently have to move to ORACLE Linux, away from CentOS, as long as potential licening implications are up in the air, if i got all that right so far. My questions actually are now: - Would i have trouble today, if using ORACLE Linux for implementing Victoria via Kolla-Ansible? - And/or would it be feasible for the mid term to reactivate support for ORACLE LINUX, until the dust has settled? - On the long: will streaming change how OpenStack will be deployed via Kolla-Ansible? Unfortunately i have to implement a project these days, not allowing me to wait until then. Unfortunate timing... Best Stefan

2 1

[rabbitmq][kolla-ansible] - RabbitMQ disconnects - 60s timeout
by Adam Tomas 24 Mar '21

24 Mar '21

Hi, I have a problem with rabbitmq heartbeats timeout (described also here: https://bugzilla.redhat.com/show_bug.cgi?id=1711794 <https://bugzilla.redhat.com/show_bug.cgi?id=1711794>). Although I have threads=1 the problem still persists, generating a lot of messages in logs: 2021-03-18 15:17:17.482 [error] <0.122.51> closing AMQP connection <0.122.51> (x.x.x.100:60456 -> x.x.x.100:5672 - mod_wsgi:699:9a813fcb-c29f-4886-82bc-00bf478b6b64): missed heartbeats from client, timeout: 60s 2021-03-18 15:17:17.484 [info] <0.846.51> Closing all channels from connection '<<x.x.x.100:60456 -> x.x.x.100:5672">>' because it has been closed 2021-03-18 15:18:15.918 [error] <0.150.51> closing AMQP connection <0.150.51> (x.x.x.111:41934 -> x.x.x.100:5672 - mod_wsgi:697:b608c7b8-9644-434e-93af-c00222c0a700): missed heartbeats from client, timeout: 60s 2021-03-18 15:18:15.920 [error] <0.153.51> closing AMQP connection <0.153.51> (x.x.x.111:41936 -> x.x.x.100:5672 - mod_wsgi:697:77348197-148b-41a6-928f-c5eddfab57c9): missed heartbeats from client, timeout: 60s 2021-03-18 15:18:15.920 [info] <0.1527.51> Closing all channels from connection '<<x.x.x.111:41934 -> x.x.x.100:5672">>' because it has been closed 2021-03-18 15:18:15.922 [info] <0.1531.51> Closing all channels from connection '<<x.x.x.111:41936 -> x.x.x.100:5672">>' because it has been closed 2021-03-18 15:20:16.080 [info] <0.2196.51> accepting AMQP connection <0.2196.51> (x.x.x.111:34826 -> x.x.x.100:5672) 2021-03-18 15:20:16.080 [info] <0.2199.51> accepting AMQP connection <0.2199.51> (x.x.x.111:34828 -> x.x.x.100:5672) I’ve set heartbeat = 600 in rabbitmq.conf and still get disconnections after 60s timeout… How to set proper timeout to avoid disconnections? Best regards Adam

2 4

[cinder] Bug deputy report for week of 2021-03-15
by Sofia Enriquez 23 Mar '21

23 Mar '21

Hello, This is a bug report from 2021-03-16 to 2021-03-24. You're welcome to join the next Cinder Bug Meeting tomorrow. - Weekly on Wednesday at 1500 UTC in #openstack-cinder - Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting Critical:- High: - https://bugs.launchpad.net/oslo.db/+bug/1814199 :" soft_delete is wrong". Assigned to Gorka Eguileor. Medium: - https://bugs.launchpad.net/cinder/+bug/1298135 :" Cinder should handle token expiration for long ops". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1920870 :" [Storwize] Fix issue while extending a volume with replication enabled". Assigned to Venkata krishna Thumu (venkatakt). - https://bugs.launchpad.net/cinder/+bug/1920237 :" race in backup manager remove_export call". Assigned to Eric Harney. Low:- Incomplete: - https://bugs.launchpad.net/cinder/+bug/1920912. " Add volume to a group which was created from a group snapshot of another consistency group fails and the group goes into error state". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1920890: " Retype of in use Hyperswap volume failing". Unassigned. Regards, Sofi -- L. Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[neutron] vPTG meetings
by Slawek Kaplonski 23 Mar '21

23 Mar '21

Hi, Based on infomation from doodle, I just booked for us 4 slots, 3h each: * Monday 1300 - 1600 UTC * Tuesday 1300 - 1600 UTC * Thursday 1300 - 1600 UTC * Friday 1300 - 1600 UTC I think that this should be enough. If not we can try to set some ad-hoc meeting during the PTG week if that will be needed. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder][nova] Running parallel iSCSI/LVM c-vol backends is causing random failures in CI
by Lee Yarwood 23 Mar '21

23 Mar '21

Hello all, I reported the following bug last week but I've yet to get any real feedback after asking a few times in irc. Running parallel iSCSI/LVM c-vol backends is causing random failures in CI https://bugs.launchpad.net/cinder/+bug/1917750 AFAICT tgtadm is causing this behaviour. As I've stated in the bug with Fedora 32 and lioadm I don't see the WWN conflict between the two backends. Does anyone know if using lioadm is an option on Focal? Thanks in advance, Lee

6 11

[largescale-sig] Video meeting Mar 24: "Scaling RabbitMQ Clusters"
by Thierry Carrez 23 Mar '21

23 Mar '21

Hi everyone, The Large Scale SIG organizes video meetings around specific scaling topics, just one hour of discussion bootstrapped by a short presentation from operators of large scale deployments of OpenStack. Last month we did one on "Regions vs. Cells" which was pretty popular. Our next video meeting will be next Wednesday, March 24, at 1500utc on Zoom (link/password will be provided on this thread the day before the event). The theme will be: "Scaling RabbitMQ Clusters" quickstarted by a presentation from Gene Kuo (LINE). To see how 1500UTC will translate into in your corner of the world, you can doublecheck: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210324T15 If you're interested in sharing your experience on this topic, or just want to learn more about that, please mark your calendar and join us next Wednesday ! -- Thierry Carrez (ttx)

1 1

[cinder] review priorities right now
by Brian Rosmaita 23 Mar '21

23 Mar '21

Please focus on the following two items in preparing for RC-1 on Thursday. 1. There are a few follow-up patches fixing bugs in driver features listed at the top of this etherpad: https://etherpad.opendev.org/p/cinder-wallaby-features 2. There's also a series of patches fixing bugs in Cinder quotas, which as you all know, have been a perennial pain point for operators. Most of these already have at least one +2. Start here: https://review.opendev.org/c/openstack/cinder/+/778182 and work your way up the "Relation chain" displayed in gerrit. Here's the complete list: https://review.opendev.org/q/topic:%22unused-quota-classes%22+(status:open%… Happy Reviewing! brian

1 0

Re: [Release-job-failures] Release of openstack/monasca-grafana-datasource for ref refs/tags/1.3.0 failed
by Thierry Carrez 23 Mar '21

23 Mar '21

We had a release job failure during the processing of the tag event when 1.3.0 was (successfully) pushed to openstack/monasca-grafana-datasource. Tags on this repository trigger the release-openstack-javascript job, which failed during pre playbook when trying to run yarn --version with the following error: /usr/share/yarn/lib/cli.js:46100 let { ^ SyntaxError: Unexpected token { at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:373:25) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (/usr/share/yarn/bin/yarn.js:24:13) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) See https://zuul.opendev.org/t/openstack/build /cdffd2a26a0d4a5b8137edb392fa5971 This prevented the job from running (likely resulting in nothing being uploaded to NPM? Not a JS job specialist), which in turn prevented announce-release job from announcing it. -- Thierry Carrez (ttx)

5 7

[CloudKitty] vPTG meeting dates
by Rafael Weingärtner 23 Mar '21

23 Mar '21

Hello guys, We need to pick a date for our vPTG meeting. The suggested date and time is Monday April 19 13UTC - 14UTC (https://ethercalc.net/oz7q0gds9zfi) which would fit exactly in one of our Monday meetings. Does everybody else agree with this date and time? Let me know if that works for you. If it does, I will book the room. -- Rafael Weingärtner

2 2

[nova][placement] Xena PTG
by Balazs Gibizer 23 Mar '21

23 Mar '21

Hi, As you probably already know that the next PTG will be held between Apr 19 - 23. To organize the gathering I need your help: 1) Please fill the doodle[1] with timeslots when you have time to join to our sessions. Please do this before end of 21st of March. 2) Please add your PTG topic in the etherpad[2]. If you feel your topic needs a cross project cooperation please note that in the etherpad which other teams are needed. Cheers, gibi [1] https://doodle.com/poll/ib2eu3c4346iqii3 [2] https://etherpad.opendev.org/p/nova-xena-ptg

1 1

[openstack-helm] No meeting tomorrow March 23rd
by Gage Hugo 22 Mar '21

22 Mar '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, March 23rd, we will cancel it. Our next IRC meeting will be March 30th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

Re: OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.
by Stefan Kelber 22 Mar '21

22 Mar '21

1 0

[heat-translator] Ask new release 2.2.1 to fix Zuul jobs
by Yoshito Ito 22 Mar '21

22 Mar '21

Hi heat-translator core members, I'd like you to review the following patches [1][2], and to ask if we can release 2.2.1 with these commits to fix our Zuul jobs. In release 2.2.0, our Zuul jobs are broken [3] because of new release of tosca-parser 2.3.0, which provides strict validation of required attributes in [4]. The patch [1] fix this issue by updating our wrong test samples. The other [2] is now blocked by this issue and was better to be merged in 2.2.0. I missed the 2.2.0 release patch [5] because none of us was added as reviewers. So after merging [1] and [2], I will submit a patch to make new 2.2.1 release. [1] https://review.opendev.org/c/openstack/heat-translator/+/779642 [2] https://review.opendev.org/c/openstack/heat-translator/+/778612 [3] https://bugs.launchpad.net/heat-translator/+bug/1918360 [4] https://opendev.org/openstack/tosca-parser/commit/00d3a394d5a3bc13ed7d2f1d7… [5] https://review.opendev.org/c/openstack/releases/+/777964 Best regards, Yoshito Ito

2 2

Re: [infra][tact-sig] Extracting commits data for the first and the last code review revisions
by Chouchen, Moataz 22 Mar '21

22 Mar '21

Hi Jermey, Thank you for your quick answer! That's what I am looking for and I am very grateful to you and to all the community. Best regards, Moataz. ________________________________ From: Jeremy Stanley Sent: Monday, March 22, 2021 8:41 AM To: openstack-discuss(a)lists.openstack.org Cc: Chouchen, Moataz Subject: Re: [infra][tact-sig] Extracting commits data for the first and the last code review revisions [I'm keeping you in Cc since you don't appear to be subscribed to this mailing list.] On 2021-03-22 15:00:03 +0000 (+0000), Chouchen, Moataz wrote: [...] > I extracted the revision IDs for the first and the last revisions > (supposed to be first and last commit hashes) for each code review > in puppet projects. However, when we have more than one revision, > we were unable to find the commits for the first revision in the > git for all the projects and we only have commits data for the > last revision. I would like to know if the commit of the first > revision does exist in the CVS, and it's possible to extract? [...] Conveniently, Gerrit stores all of this in the repository and we replicate it to our Git server farm. The complication is that, because of the amend/rebase-oriented nature of Gerrit's code review workflow, those earlier revisions don't appear in the branch history. Instead, they are tracked with named references which look like changes/XX/YYYY/Z where YYYY is the numeric index identifier for the change, XX is the last two digits of YYYY (for sharding purposes), and Z is the revision number starting from 1. Let's take this puppet-nova change as an example: https://opendev.org/openstack/puppet-nova/commit/d385ca8 There you can see Gitea is displaying an indicator that there is a named ref of changes/63/764763/5 associated with the commit. That means it was revision 5 of change 764763 in Gerrit. You can fetch that ref like so: git fetch origin changes/63/764763/5 That will fill FETCH_HEAD which you can then use with checkout, show, or any other relevant subcommands. Conveniently, if you instead want the first revision of 764763, all you have to do differently is adjust the revision number: git fetch origin changes/63/764763/1 Hopefully that's what you're looking for? -- Jeremy Stanley

1 0

Extracting commits data for the first and the last code review revisions
by Chouchen, Moataz 22 Mar '21

22 Mar '21

Dear Openstack community, Hope you are doing well. I am Moataz Chouchen a Ph.D. student from ETS Montreal. I am interested in studying the impact of code review on the quality of puppet files. For this reason, I am interested in studying the code reviews containing puppet files (We investigate puppet projects.) and comparing puppet files in the first revision and the last revision for each code review. To achieve this, I extracted the revision IDs for the first and the last revisions (supposed to be first and last commit hashes) for each code review in puppet projects. However, when we have more than one revision, we were unable to find the commits for the first revision in the git for all the projects and we only have commits data for the last revision. I would like to know if the commit of the first revision does exist in the CVS, and it's possible to extract? In case these commits do not exist, how could, we retrieve the files in the first version of a review? Thank you very much, Best regards, Moataz

2 1

[oslo] Wallaby branches are now cut for oslo world
by Herve Beraud 22 Mar '21

22 Mar '21

Hello Osloers, As $subject (FYI) Thanks for your attention -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

2 1

Re: [glance][openstack-ansible] Snapshots disappear during saving
by Oliver Wenz 22 Mar '21

22 Mar '21

Hi Dmitriy, I tried the fix anyways, i.e. I replaced the value of swift_fallocate_reserve as shown here: https://review.opendev.org/c/openstack/openstack-ansible-os_swift/+/782117/… Now I'm getting the same error with '%%%' instead of '%%': Mar 22 15:04:49 bc1bl12 systemd[1]: swift-account-reaper.service: Main process exited, code=exited, status=1/FAILURE Mar 22 15:04:49 bc1bl12 systemd[1]: swift-account-reaper.service: Failed with result 'exit-code'. Mar 22 15:04:51 bc1bl12 systemd[1]: swift-account-reaper.service: Scheduled restart job, restart counter is at 171887. Mar 22 15:04:51 bc1bl12 systemd[1]: Stopped swift-account-reaper service. Mar 22 15:04:51 bc1bl12 systemd[1]: Started swift-account-reaper service. Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: Traceback (most recent call last): Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", line 803, in config_fallocate_val> Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: reserve_value = float(reserve_value[:-1]) Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: ValueError: could not convert string to float: '1%%' Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: During handling of the above exception, another exception occurred: Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: Traceback (most recent call last): Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: File "/openstack/venvs/swift-22.1.0/bin/swift-account-reaper", line 23, in <module> Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: run_daemon(AccountReaper, conf_file, **options) Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/daemon.py", line 304, in run_daemon Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: utils.config_fallocate_value(conf.get('fallocate_reserve', '1%')) Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", line 809, in config_fallocate_val> Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: raise ValueError('Error: %s is an invalid value for fallocate' Mar 22 15:04:52 bc1bl12 swift-account-reaper[322101]: ValueError: Error: 1%%% is an invalid value for fallocate_reserve. Kind regards, Oliver > Message: 3 > Date: Mon, 22 Mar 2021 12:06:19 +0200 > From: Dmitriy Rabotyagov <noonedeadpunk(a)ya.ru> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [glance][openstack-ansible] Snapshots disappear during > saving > Message-ID: <984511616407178(a)mail.yandex.ru> > Content-Type: text/plain; charset=utf-8 > > Well, looking into the fix I suggested, I'm not sure if it's valid one. > There's really be a mess in patches, and according to the log provided, config > needs just `1%` instead of the `1%%` you currently have. > > And it feels like that's what default behaviour should do with [1]. But I'm > pretty sure that this error was making swift fail and thus having weird issues > while operating. > > So I'm not sure what specifily wrong with value of swift_fallocate_reserve - > maybe we've missed some config to define it or it has been overriden > somewhere, but it feels like current default should cover issue you see in > swift... > > [1] > https://opendev.org/openstack/openstack-ansible-os_swift/src/branch/stable/… > > 22.03.2021, 11:56, "Dmitriy Rabotyagov" <noonedeadpunk(a)ya.ru>: > > Yes, 1%% is smth we're fighting for years, as this setting changes on the > > swift side from time to time, and I really lost account which one is valid > > at the moment. > > > > Here's related SWIFT bug: > > > > https://bugs.launchpad.net/swift/+bug/1844368 > > > > I've just pushed > > https://review.opendev.org/c/openstack/openstack-ansible-os_swift/+/782117 to > > cover this issue. Can you try applying this change manually to see if this > > works? > > > > 22.03.2021, 11:25, "Oliver Wenz" <oliver.wenz(a)dhbw-mannheim.de>: > >> Hi Dmitriy, > >> thanks for your answer! Yes, we do use swift and its use as glance backend > >> is > >> intentional. > >> > >> I got the following from the swift-proxy-server logs in the swift container > >> on > >> the infra host after taking a snapshot: > >> > >> Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]: > >> Client > >> disconnected without sending last chunk (txn: > >> txa7c64547baf0450eb0034-006058588b) (client_ip: 192.168.110. > >> 106) > >> Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]: > >> 192.168.110.106 192.168.110.211 22/Mar/2021/08/43/43 PUT > >> /v1/AUTH_024cc551782f41e395d3c9f13582ef7d/glance_images/3ec63ec2-aa3b-4c3b-a904-b55d1a6ec878 > >> -00001 HTTP/1.0 499 - python-swiftclient-3.10.1 gAAAAABgWFiKMz9R... > >> 204800000 89 > >> - txa7c64547baf0450eb0034-006058588b - 52.2991 - - 1616402571.623875856 > >> 1616402623.922997952 0 > >> > >> On the swift host some services logs contain errors. E.g. the > >> swift-container-updater service: > >> > >> Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Main > >> process exited, code=exited, status=1/FAILURE > >> Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Failed > >> with > >> result 'exit-code'. > >> Mar 22 08:42:21 bc1bl12 systemd[1]: swift-container-updater.service: > >> Scheduled > >> restart job, restart counter is at 162982. > >> Mar 22 08:42:21 bc1bl12 systemd[1]: Stopped swift-container-updater > >> service. > >> Mar 22 08:42:21 bc1bl12 systemd[1]: Started swift-container-updater > >> service. > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most > >> recent > >> call last): > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File > >> "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", > >> line 803, in config_fallocate_value > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: reserve_value = > >> float(reserve_value[:-1]) > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: could > >> not > >> convert string to float: '1%' > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: During handling of > >> the > >> above exception, another exception occurred: > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most > >> recent > >> call last): > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File > >> "/openstack/venvs/swift-22.1.0/bin/swift-container-updater", line 23, in > >> <module> > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: > >> run_daemon(ContainerUpdater, conf_file, **options) > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File > >> "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/daemon.py", > >> line 304, in run_daemon > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: > >> utils.config_fallocate_value(conf.get('fallocate_reserve', '1%')) > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File > >> "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", > >> line 809, in config_fallocate_value > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: raise > >> ValueError('Error: %s is an invalid value for fallocate' > >> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: Error: > >> 1%% > >> is an invalid value for fallocate_reserve. > >> > >> The same exit-code and traceback shows in the logs of > >> swift-container-auditor, > >> swift-account-auditor and swift-account-reaper services. Does this tell you > >> anything useful? > >> > >> We didn't experience any problems when uploading files to containers, only > >> when > >> taking snapshots of instances. > >> > >> Kind regards, > >> Oliver > >> > >>> ------------------------------ > >>> > >>> Message: 4 > >>> Date: Thu, 18 Mar 2021 12:44:47 +0200 > >>> From: Dmitriy Rabotyagov <noonedeadpunk(a)ya.ru> > >>> To: "openstack-discuss(a)lists.openstack.org" > >>> <openstack-discuss(a)lists.openstack.org> > >>> Subject: Re: [glance][openstack-ansible] Snapshots disappear during > >>> saving > >>> Message-ID: <374941616064157(a)mail.yandex.ru> > >>> Content-Type: text/plain; charset=utf-8 > >>> > >>> Hi Olver, > >>> > >>> Am I right that you're also using OpenStack Swift and it's intentional to > >>> store images there? > >>> Since the issue is related to the upload process into the Swift. So also > >>> checking Swift logs > >>> be usefull as well. > > > > -- > > Kind Regards, > > Dmitriy Rabotyagov > > > -- > Kind Regards, > Dmitriy Rabotyagov > > > > ------------------------------ > > Message: 4 > Date: Mon, 22 Mar 2021 12:35:37 +0100 > From: Bernard Cafarelli <bcafarel(a)redhat.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: Re: [neutron][stable] neutron-lib stable branches core > reviewers > Message-ID: > <CABHdKwrEN99b3VS89U0M8BRYevV2oqGLSPkSfVzdjCZNFoKHpA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Thu, 18 Mar 2021 at 14:48, Slawek Kaplonski <skaplons(a)redhat.com> wrote: > > > Hi, > > > > I just noticed that neutron-lib project has got own group > > "neutron-lib-stable-maint" which has +2 powers in neutron-lib stable > > branches [1]. As I see now in gerrit that group don't have any members. > > Would it be maybe possible to remove that group and add > > "neutron-stable-maint" to the neutron-lib stable branches instead? If yes, > > should I simply propose patch to change [1] or is there any other way which > > I should do it? > > > I guess we never spotted that "neutron-lib-stable-maint" before, as it > seems neutron cores had +2 powers before: > https://review.opendev.org/c/openstack/neutron-lib/+/717093 > > But yes it could be useful to have either of these groups (neutron cores or > stable cores) in, backports to neutron-lib are rare but some happen - I > remember one some time ago where it was valid to have a patch backported. > > > > [1] > > https://github.com/openstack/project-config/blob/master/gerrit/acls/opensta… > > > > -- > > Slawek Kaplonski > > Principal Software Engineer > > Red Hat > > > > -- > Bernard Cafarelli >

1 0

[neutron] Bug deputy report for week of March 15th
by Brian Haley 22 Mar '21

22 Mar '21

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * UT are failing when runs with neutron-lib master - https://bugs.launchpad.net/neutron/+bug/1919280 - https://review.opendev.org/c/openstack/neutron/+/780802 * Functional tests failing due to timeout while spawning metadata proxy - https://bugs.launchpad.net/neutron/+bug/1919344 * Functional tests failing due to timeout while killing process - https://bugs.launchpad.net/neutron/+bug/1919345 * [OVN] "OVS_SYSCONFDIR" should be created before writing the OVS system-id file - https://bugs.launchpad.net/neutron/+bug/1920634 - Devstack patch proposed by Slawek High bugs --------- * [OVN] Do not enable send_periodic on router ports which are connected to provider networks - https://bugs.launchpad.net/neutron/+bug/1919347 - https://review.opendev.org/c/openstack/neutron/+/780916 * Project administrators are allowed to view networks across projects - https://bugs.launchpad.net/neutron/+bug/1919386 - https://review.opendev.org/c/openstack/neutron-lib/+/781075 * Creation of floating ip with new rbac policies fails - https://bugs.launchpad.net/neutron/+bug/1920001 Low bugs -------- * [L3][L2 pop] Is it necessary to enforce enabling the option arp_responder and l2_population? - https://bugs.launchpad.net/neutron/+bug/1919107 - Can be reverted now that other DVR changes are being reverted * [OVN][FT] FT tests log a SQL exception - https://bugs.launchpad.net/neutron/+bug/1919352 - https://review.opendev.org/c/openstack/neutron/+/780926 Wishlist bugs ------------- * Automatic rescheduling of BGP speakers on DrAgents - https://bugs.launchpad.net/neutron/+bug/1920065 - RFE

1 0

[nova] When are "_del" directories deleted?
by Eugen Block 22 Mar '21

22 Mar '21

Hi *, I stumbled across a different issue when I noticed there's a <UUID>_del directory in /var/lib/nova/instances/. It's a shared directory to enable live-migration. I noticed these "_del" directories before but I didn't really investigate, everything seems to work as expected. But I would like to understand what exactly happens with such a directory, for example currently there's just one instance having also a _del directory. The timestamp is from 2 years ago when the instance was resized the first time. Looking in the nova code [1] I found the reference to the resize function, I just don't quite understand what would happen with that instance if it was shutdown. Would nova delete it to "clean up"? Can I remove that directory safely to prevent nova from doing anything destructive to that instance? I'd appreciate any insights about this. Just to be safe I created an RBD snapshot of the disk to prevent a deletion. Best regards, Eugen [1] https://opendev.org/openstack/nova/src/commit/146b27f22327f8d60c1017c22ccf1…

2 2

[ironic] How to move node from active state to manageable
by Igal Katzir 22 Mar '21

22 Mar '21

Hello Forum, I have an overcloud that gone bad and I am trying to re-deploy it, Running rhos16.1 with one director and two overcloud nodes (compute and controller) I have re-installed undercloud and having both nodes in an active provisioning state. Do I need to run introspection again? Here is the outputted for baremetal node list: (undercloud) [stack@interop010 ~]$ openstack baremetal node list +--------------------------------------+------------+--------------------------------------+-------------+--------------------+-------------+ | UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance | +--------------------------------------+------------+--------------------------------------+-------------+--------------------+-------------+ | 97b9a603-f64f-47c1-9fb4-6c68a5b38ff6 | interop025 | c7bf16b7-eb3c-4022-88de-7c5a78cda174 | power on | active | False | | 4b02703a-f765-4ebb-85ed-75e88b4cbea5 | interop026 | 99223f65-6985-4815-92ff-e19a28c2aab1 | power on | active | False | +--------------------------------------+------------+--------------------------------------+-------------+--------------------+-------------+ When I want to move each node from active > manage I get an error: (undercloud) [stack@interop010 ~]$ openstack baremetal node manage 4b02703a-f765-4ebb-85ed-75e88b4cbea5 The requested action "manage" can not be performed on node "4b02703a-f765-4ebb-85ed-75e88b4cbea5" while it is in state "active". (HTTP 400) How do I get to a state which is ready for deployment (available) ? Thanks, Igal

2 3

Re: [glance][openstack-ansible] Snapshots disappear during saving
by Oliver Wenz 22 Mar '21

22 Mar '21

Hi Dmitriy, thanks for your answer! Yes, we do use swift and its use as glance backend is intentional. I got the following from the swift-proxy-server logs in the swift container on the infra host after taking a snapshot: Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]: Client disconnected without sending last chunk (txn: txa7c64547baf0450eb0034-006058588b) (client_ip: 192.168.110. 106) Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]: 192.168.110.106 192.168.110.211 22/Mar/2021/08/43/43 PUT /v1/AUTH_024cc551782f41e395d3c9f13582ef7d/glance_images/3ec63ec2-aa3b-4c3b-a904-b55d1a6ec878 -00001 HTTP/1.0 499 - python-swiftclient-3.10.1 gAAAAABgWFiKMz9R... 204800000 89 - txa7c64547baf0450eb0034-006058588b - 52.2991 - - 1616402571.623875856 1616402623.922997952 0 On the swift host some services logs contain errors. E.g. the swift-container-updater service: Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Main process exited, code=exited, status=1/FAILURE Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Failed with result 'exit-code'. Mar 22 08:42:21 bc1bl12 systemd[1]: swift-container-updater.service: Scheduled restart job, restart counter is at 162982. Mar 22 08:42:21 bc1bl12 systemd[1]: Stopped swift-container-updater service. Mar 22 08:42:21 bc1bl12 systemd[1]: Started swift-container-updater service. Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most recent call last): Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", line 803, in config_fallocate_value Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: reserve_value = float(reserve_value[:-1]) Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: could not convert string to float: '1%' Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: During handling of the above exception, another exception occurred: Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most recent call last): Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File "/openstack/venvs/swift-22.1.0/bin/swift-container-updater", line 23, in <module> Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: run_daemon(ContainerUpdater, conf_file, **options) Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/daemon.py", line 304, in run_daemon Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: utils.config_fallocate_value(conf.get('fallocate_reserve', '1%')) Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: File "/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py", line 809, in config_fallocate_value Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: raise ValueError('Error: %s is an invalid value for fallocate' Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: Error: 1%% is an invalid value for fallocate_reserve. The same exit-code and traceback shows in the logs of swift-container-auditor, swift-account-auditor and swift-account-reaper services. Does this tell you anything useful? We didn't experience any problems when uploading files to containers, only when taking snapshots of instances. Kind regards, Oliver > ------------------------------ > > Message: 4 > Date: Thu, 18 Mar 2021 12:44:47 +0200 > From: Dmitriy Rabotyagov <noonedeadpunk(a)ya.ru> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [glance][openstack-ansible] Snapshots disappear during > saving > Message-ID: <374941616064157(a)mail.yandex.ru> > Content-Type: text/plain; charset=utf-8 > > Hi Olver, > > Am I right that you're also using OpenStack Swift and it's intentional to > store images there? > Since the issue is related to the upload process into the Swift. So also > checking Swift logs > be usefull as well. >

2 2

[oslo] Cancel meeting today
by Herve Beraud 22 Mar '21

22 Mar '21

Hello Osloers, I won't be around to run the meeting today. If someone else from the Oslo team wants to run it, please feel free. Thanks for your understanding -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[release] Xena PTG
by Herve Beraud 22 Mar '21

22 Mar '21

Oï releasers, The PTG is fast approaching (Apr 19 - 23). To help to organize the gathering: 1) please fill the doodle[1] with the time slots that fit well for you; 2) please add your PTG topics in our etherpad[2]. Voting will be closed on the 21st of March. Thanks for your reading, [1] https://doodle.com/poll/8d8n2picqnhchhsv [2] https://etherpad.opendev.org/p/xena-ptg-os-relmgt -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 2

Authenticating to devstack and listing nova flavors + servers
by Joe Wolfe 21 Mar '21

21 Mar '21

Hi All, I am working on an api and would like to get some more context behinds authenticating into the api - so I am trying to get a list out of available flavors 1 and servers to start off with. I am able to get a token that I can interact with against keystone which shows up as https://mydevstackurl/identity/ <https://mydevstackurl/identity/> however when I try and run a simple curl against my compute as follows: curl -H "X-Auth-Token: $OS_TOKEN" -s https://http://mydevstackurl/compute/api/v2.1/servers <https://http//mydevstackurl/compute/api/v2.1/servers> I got no response back from curl - no 200 ,no 30x no 4xx nothing. Can anyone help to get me started ? The documents seem to be pretty detailed - but the methods provided don’t seem to work either in the tutorial: for example: curl -s -H "X-Auth-Token: $OS_TOKEN" \ $OS_COMPUTE_API/flavors \ | python -m json.tool Only returns: zsh: no matches found: http://mydevstackurl/identity/v3/auth/tokens?nocatalog <http://mydevstackurl/identity/v3/auth/tokens?nocatalog> Expecting value: line 1 column 1 (char 0) Thanks

2 1

Re: [openstack-community] Authenticating to devstack and listing nova flavors + servers
by Jeremy Stanley 21 Mar '21

21 Mar '21

On 2021-03-21 16:39:42 -0400 (-0400), Joe Wolfe wrote: > I am working on an api and would like to get some more context > behinds authenticating into the api - so I am trying to get a list > out of available flavors 1 and servers to start off with. I am > able to get a token that I can interact with against keystone > which shows up as https://mydevstackurl/identity/ however when I > try and run a simple curl against my compute as follows: > > curl -H "X-Auth-Token: $OS_TOKEN" -s https://http://mydevstackurl/compute/api/v2.1/servers > > I got no response back from curl - no 200 ,no 30x no 4xx nothing. > > Can anyone help to get me started ? The documents seem to be > pretty detailed - but the methods provided don’t seem to work > either in the tutorial: for example: > > curl -s -H "X-Auth-Token: $OS_TOKEN" \ > $OS_COMPUTE_API/flavors \ > | python -m json.tool > > Only returns: > > zsh: no matches found: http://mydevstackurl/identity/v3/auth/tokens?nocatalog > Expecting value: line 1 column 1 (char 0) As the description of the community mailing list states, "This list does not provide support for OpenStack software." I have Cc'd the openstack-discuss mailing list which is intended for "Discussion of OpenStack use and development." Please follow up there with your question. I'm keeping you in the To header in case you're not subscribed there, so that people who reply to this will hopefully include you directly. -- Jeremy Stanley

1 0

Fw: Aw: Re: OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.
by Stefan Kelber 21 Mar '21

21 Mar '21

1 1

OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.
by Stefan Kelber 21 Mar '21

21 Mar '21

3 2

iPXE update/configuration for the undercloud.
by Kendrick 20 Mar '21

20 Mar '21

I have a melanox connectx3 and a few broadcom systems that do not properly pxe boot, using maas the broadcoms work fine. I was looking around and one of the solutions to similar problems from 2017 and 19 were to use a different version of the ipxe files. I was hoping to know what settings/changes/scripts openstack undercloud used so i can make sure the connectx3 support is built in to the ipxe file and what files needed to be copied where from the source buld to the containers since the containers have about 20 sets of the ipxe files from what i can see when i use find to locate them from the host. Regards Kendrick

1 0