March 2021 - openstack-discuss - lists.openstack.org

[TripleO] next irc meeting Tuesday Mar 30 @ 1400 UTC in #tripleo
by Marios Andreou 26 Mar '21

26 Mar '21

Reminder that the next TripleO irc meeting is: ** Tuesday 30 March at 1400 UTC in #tripleo ** ** https://wiki.openstack.org/wiki/Meetings/TripleO ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to highlight at https://etherpad.opendev.org/p/tripleo-meeting-items This can be recently completed things, ongoing review requests, blocking issues, or anything else tripleo you want to share. Our last meeting was on Mar 16 - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-03-16-14.… Hope you can make it on Tuesday, regards, marios

1 0

[kolla] Train Centos7 -> Centos8 upgrade fails on masakari
by Braden, Albert 26 Mar '21

26 Mar '21

I've created a heat stack and installed Openstack Train to test the Centos7->8 upgrade following the document here: https://docs.openstack.org/kolla-ansible/train/user/centos8.html#migrating-… Everything seems to work fine until I try to deploy the first replacement controller into the cluster. I upgrade RMQ, ES and Kibana, then follow the "remove existing controller" process to remove control0, create a Centos 8 VM, bootstrap the cluster, pull containers to the new control0, and everything is still working. Then I type the last command "kolla-ansible -i multinode deploy --limit control" The RMQ install works and I see all 3 nodes up in the RMQ admin, but it takes a long time to complete "TASK [service-ks-register : masakari | Creating users] " and then hangs on "TASK [service-ks-register : masakari | Creating roles]". At this time the new control0 becomes unreachable and drops out of the RMQ cluster. I can still ping it but console hangs along with new and existing ssh sessions. It appears that the CPU may be maxed out and not allowing interrupts. Eventually I see error "fatal: [control0]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}" RMQ seems fine on the 2 old controllers; they just don't see the new control0 active: (rabbitmq)[root@chrnc-void-testupgrade-control-2 /]# rabbitmqctl cluster_status Cluster status of node rabbit@chrnc-void-testupgrade-control-2 ... [{nodes,[{disc,['rabbit@chrnc-void-testupgrade-control-0', 'rabbit@chrnc-void-testupgrade-control-0-replace', 'rabbit@chrnc-void-testupgrade-control-1', 'rabbit@chrnc-void-testupgrade-control-2']}]}, {running_nodes,['rabbit@chrnc-void-testupgrade-control-1', 'rabbit@chrnc-void-testupgrade-control-2']}, {cluster_name,<<"rabbit(a)chrnc-void-testupgrade-control-0.dev.chtrse.com">>}, {partitions,[]}, {alarms,[{'rabbit@chrnc-void-testupgrade-control-1',[]}, {'rabbit@chrnc-void-testupgrade-control-2',[]}]}] After this the HAProxy IP is pingable but openstack commands are failing: (openstack) [root@chrnc-void-testupgrade-build openstack]# osl Failed to discover available identity versions when contacting http://172.16.0.100:35357/v3. Attempting to parse version from URL. Gateway Timeout (HTTP 504) After about an hour my open ssh session on the new control0 responded and confirmed that the CPU is maxed out: [root@chrnc-void-testupgrade-control-0-replace /]# uptime 17:41:55 up 1:55, 0 users, load average: 157.87, 299.75, 388.69 I built new heat stacks and tried it a few times, and it consistently fails on masakari. Do I need to change something in my masakari config before upgrading Train from Centos 7 to Centos 8? I apologize for the nonsense below. I have not been able to stop it from being attached to my external emails. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

4 5

[release] Release countdown for week R-2 Mar 29 - Apr 02
by Herve Beraud 26 Mar '21

26 Mar '21

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Wallaby deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/wallaby branch creation for all deliverables that have not branched yet, using the latest available Wallaby release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/wallaby branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/wallaby branch before releasing out of the stable/wallaby branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Xena development, though the focus should still be on finishing up Wallaby until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Wallaby release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Wallaby version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: 08 April, 2021 (R-1 week) Final Wallaby release: 14 April, 2021 Xena virtual PTG: 19 - 23 April, 2021 Thank you 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-----

1 0

[nova][placement] Wallaby release
by Balazs Gibizer 26 Mar '21

26 Mar '21

Hi, We are getting close to the Wallaby release. So I create a tracking etherpad[1] with the schedule and TODOs. One thing that I want to highlight is that we will hit Feature Freeze on 11th of March. As the timeframe between FF and RC1 is short I'm not plannig with FFEs. Patches that are approved before 11 March EOB can be rechecked or rebased if needed and then re-approved. If you have a patch that is really close but not approved before the deadline, and you think there are two cores that willing to review it before RC1, then please send a mail to the ML with [nova][FFE] subject prefix not later than 16th of March EOB. Cheers, gibi [1] https://etherpad.opendev.org/p/nova-wallaby-rc-potential

2 3

[glance] [ops] Glance deployed on 2 nodes with rbd. Do I need a shared filesystem for the reserved stores ?
by Massimo Sgaravatto 26 Mar '21

26 Mar '21

We are using OpenStack Train but we plan to migrate soon to something newer The glance-api service is deployed on 2 nodes. We used to have 2 backends for glance (file and rbd) but now we want to use only ceph. So I guess the configuration for the stores can be simply something like this [*] Reading: https://docs.openstack.org/glance/train/admin/multistores.html is not too clear to me if I have to configure somewhere filesystem_store_datadir. In particular do I have to configure the [os_glance_tasks_store] and [os_glance_staging_store] reserved stores ? If so, do I still need shared (between the 2 glance-api nodes )filesystems for them ? Thanks, Massimo [*] [DEFAULT] enabled_backends = rbd:rbd [glance_store] default_backend = rbd [rbd] store_description = Ceph in replica 3 rbd_store_pool = glance-cloudtest rbd_store_user = glance-cloudtest rbd_store_ceph_conf = /etc/ceph/ceph.conf rbd_store_chunk_size = 8

2 3

[cyborg][ptg] Xena PTG
by Wang, Xin-ran 26 Mar '21

26 Mar '21

Hi all, we signed up for the following slots [1] at Cactus room: * Tue Apr. 20th 6:00- 8:00 UTC (2 slots) * Wed Apr. 21th 6:00- 8:00 UTC (2 slots) * Thu Apr. 22th 6:00- 8:00 UTC (2 slots) * Fri Apr. 23th 6:00- 8:00 UTC (2 slots) If you want add some topic to discuss, please feel free to add it to the etherpad [2]. [1] https://ethercalc.net/oz7q0gds9zfi [2] https://etherpad.opendev.org/p/cyborg-xena-ptg Thanks, Xin-Ran

1 0

[all][elections][tc] TC Vacancy Special Election Nominations Kickoff
by Jeremy Stanley 26 Mar '21

26 Mar '21

Nominations for one vacant OpenStack TC (Technical Committee) position are now open and will remain open until Apr 08, 2021 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/xena/<Project_Name or "TC">/<email_address> (for example, "candidates/xena/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for the vacant seat on the Technical Committee. This TC vacancy special election will be held from Apr 8, 2021 23:45 UTC through to Apr 15, 2021 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Victoria to Wallaby timeframe, Apr 24, 2020 00:00 UTC - Mar 08, 2021 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. Note that the contribution qualifying period for this special election is being kept the same as what would have been used for the original TC election. The four already elected TC members for this term are listed as candidates in the special election, but will not appear on any resulting poll as they have already been officially elected. Only new candidates in addition to the four elected TC members for this term will appear on a subsequent poll for the TC vacancy special election. Please find below the timeline: nomination starts @ Mar 25, 2021 23:45 UTC nomination ends @ Apr 08, 2021 23:45 UTC elections start @ Apr 08, 2021 23:45 UTC elections end @ Apr 15, 2021 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their preferred email addresses in Gerrit prior to 2021-04-01 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -- Jeremy Stanley on behalf of the OpenStack Technical Elections Officials

1 0

[cinder] need core reviewers for small driver fix
by Belogrudov, Vladislav 26 Mar '21

26 Mar '21

Dear core reviewers, I would like to ask for help in reviewing a small bug fix in Cinder driver for Dell EMC PowerStore. It's just 2 chars, the driver wrongly used "eq" operator in PostgREST request instead of "cs" for finding a value in an array. The fix is under review [1]. Official API guide for PowerStore [2] says that ip_pool_address endpoint returns address instances with array of purposes, where the driver searches for iSCSI purpose. If there are more purposes configured for an iSCSI target address, the driver fails to operate. It would be great if the fix could go to Wallaby. Best regards, Vladislav Belogrudov [1] https://review.opendev.org/c/openstack/cinder/+/782087 [2] https://downloads.dell.com/manuals/common/pwrstr-apig_en-us.pdf

2 1

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

26 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 26 Mar '21

26 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 26 Mar '21

26 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 26 Mar '21

26 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 26 Mar '21

26 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 26 Mar '21

26 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 26 Mar '21

26 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 26 Mar '21

26 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 25 Mar '21

25 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 25 Mar '21

25 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 25 Mar '21

25 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