June 2024 - openstack-discuss - lists.openstack.org

[ironic][docs] Ironic docs audit draft report
by Jay Faulkner 13 Jun '24

13 Jun '24

Hi all, Dave from Expert Support has been doing a docs audit for Ironic, as some of you are aware. The preliminary draft of the report is ready for review: https://docs.google.com/document/d/1e9URuPHKNTx5QXdkCFAzsS0EAAxPJ-xQC4BEpDw… -- please add comments if you have them. I've added discussion of this as an agenda item for next Ironic meeting on Monday June 17. I anticipate the next steps will be as follows: - Ironic cores and other interested parties review -- now - ~June 24th - Revise report and action items as needed - Turn action items into documentation bugs against Ironic, tagged as docs-audit-2024, for completion by the community. Dave has spent some time interviewing Ironic operators and contributors, as well as looking over our docs from the perspective of a long-time tech writer with cloud, but not OpenStack, experience. I've found his insights very useful so far, and I think this document is worth a read even if you're not specifically invested in Ironic docs. Thanks, Jay Faulkner

1 0

[neutron] ovs: multiple rows in Manager patch
by stream_unpicked390＠simplelogin.com 13 Jun '24

13 Jun '24

Hi everyone! this is my first time on a mailing list, so please excuse any "obvious" mistakes and feel free to correct me :) I'm currently setting up a minimal OpenStack system manually on one server. The setup is nearly complete but I'm running into issues with neutron. After fully completing the neutron setup as mentioned in the docs, the neutron-ovs-service refuses to start, showing the error message multiple rows in Manager patch "ptcp:6640:127.0.0.0" I dumped the ovs database which only shows one row in the Manager table. After many days of debugging and googleing I'm out of ideas how this could be solved.. I already posted this issue on serverfault (https://serverfault.com/questions/1160418/openstack-ovs-multiple-rows-in-ma…), only after that post finding this mailing list! Best regards Talooola

2 3

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 13 Jun '24

13 Jun '24

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! I will also be offline and unavailable for a couple of days, back on June 18th. -Brian

1 0

Caracal Magnum: magnum-api-wsgi fails to start because of a problem retrieving the version
by Michel Jouvin 13 Jun '24

13 Jun '24

Hi, Moving forward with my current upgrades, I tried to upgrade our preprod Magnum to Caracal. Unfortunately, every components using the Magnum module fails with: ---- File "/usr/bin/magnum-api-wsgi", line 52, in <module> application = build_wsgi_app() File "/usr/lib/python3.9/site-packages/magnum/api/app.py", line 74, in build_wsgi_app service.prepare_service(sys.argv) File "/usr/lib/python3.9/site-packages/magnum/common/service.py", line 27, in prepare_service config.parse_args(argv) File "/usr/lib/python3.9/site-packages/magnum/common/config.py", line 32, in parse_args version=version.version_info.release_string(), File "/usr/lib/python3.9/site-packages/pbr/version.py", line 490, in release_string return self.semantic_version().release_string() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 498, in semantic_version self._semantic = self._get_version_from_importlib_metadata() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 483, in _get_version_from_importlib_metadata return SemanticVersion.from_pip_string(result_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 156, in from_pip_string return klass._from_pip_string_unsafe(version_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 163, in _from_pip_string_unsafe version_string = version_string.lstrip('vV') AttributeError: 'NoneType' object has no attribute 'lstrip' ---- It also affects magnum-db-manage where the traceback is litle bit different but the exception happens at the same place so I guess it is a common cause: ------ File "/usr/bin/magnum-db-manage", line 5, in <module> from magnum.cmd.db_manage import main File "/usr/lib/python3.9/site-packages/magnum/__init__.py", line 18, in <module> __version__ = pbr.version.VersionInfo( File "/usr/lib/python3.9/site-packages/pbr/version.py", line 505, in version_string return self.semantic_version().brief_string() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 498, in semantic_version self._semantic = self._get_version_from_importlib_metadata() File "/usr/lib/python3.9/site-packages/pbr/version.py", line 483, in _get_version_from_importlib_metadata return SemanticVersion.from_pip_string(result_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 156, in from_pip_string return klass._from_pip_string_unsafe(version_string) File "/usr/lib/python3.9/site-packages/pbr/version.py", line 163, in _from_pip_string_unsafe version_string = version_string.lstrip('vV') AttributeError: 'NoneType' object has no attribute 'lstrip' ------ For magnum-db-manage a workaround is to comment the __version__ line in __init__.but it doesn't help for the API. I wanted to check in the Magnum release notes if I missed some requirements but unfortunately they are not linked from https://releases.openstack.org/caracal/#caracal-magnum and I was not able to locate them elsewhere... Thanks in advance for any help/hint. Best regards, Michel

1 2

[manila] stuck at connecting ceph backend with manila
by Shubham Kumar Yadav 13 Jun '24

13 Jun '24

hello, I'm trying to install manila in my openstack cloud but having problem with "*Authorizing the driver to communicate with Ceph*" *1 -> *i have created a configmap with these confs and mounted it on manila-share pod [client.manila]client mount uid = 0client mount gid = 0log file = /opt/stack/logs/ceph-client.manila.logadmin socket = /opt/stack/status/stack/ceph-$name.$pid.asokkeyring = /etc/ceph/manila.keyring *2 -> *then i have created a secret with client.manila keyring and attached it to the manila-share pod at keyring = /etc/ceph/manila.keyring *3 -> *inside manila-share pod i see the logs 2024-06-03 09:00:53.682 6 INFO manila.share.drivers.cephfs.driver [None req-22cd7b29-a383-44cd-8cb8-1c639a3034dc - - - - - -] [CEPHFSNATIVE1] Ceph client found, connecting... 2024-06-03 09:00:53.713 6 ERROR manila.share.manager [None req-22cd7b29-a383-44cd-8cb8-1c639a3034dc - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-2@cephfsnative1: manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-06-03 09:00:53.713 6 ERROR manila.share.manager Traceback (most recent call last): 2024-06-03 09:00:53.713 6 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 421, in rados_client 2024-06-03 09:00:53.713 6 ERROR manila.share.manager self._rados_client.connect() 2024-06-03 09:00:53.713 6 ERROR manila.share.manager File "rados.pyx", line 690, in rados.Rados.connect 2024-06-03 09:00:53.713 6 ERROR manila.share.manager rados.IOError: [errno 5] RADOS I/O error (error connecting to the cluster) 2024-06-03 09:00:53.713 6 ERROR manila.share.manager 2024-06-03 09:00:53.713 6 ERROR manila.share.manager During handling of the above exception, another exception occurred: 2024-06-03 09:00:53.713 6 ERROR manila.share.manager 2024-06-03 09:00:53.713 6 ERROR manila.share.manager Traceback (most recent call last): 2024-06-03 09:00:53.713 6 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/manager.py", line 371, in _driver_setup 2024-06-03 09:00:53.713 6 ERROR manila.share.manager self.driver.do_setup(ctxt) 2024-06-03 09:00:53.713 6 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 274, in do_setup 2024-06-03 09:00:53.713 6 ERROR manila.share.manager rados_client=self.rados_client, 2024-06-03 09:00:53.713 6 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 424, in rados_client 2024-06-03 09:00:53.713 6 ERROR manila.share.manager raise exception.ShareBackendException( 2024-06-03 09:00:53.713 6 ERROR manila.share.manager manila.exception.ShareBackendException: [%(be)s] Ceph client failed to connect. 2024-06-03 09:00:53.713 6 ERROR manila.share.manager 2024-06-03 09:00:53.714 6 DEBUG manila.utils [None req-22cd7b29-a383-44cd-8cb8-1c639a3034dc - - - - - -] Finished call to 'manila.share.manager.ShareManager.init_host.<locals>._driver_setup' after 2222.651(s), this was the 12th time calling it. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/after.py:44 2024-06-03 09:00:53.714 6 DEBUG manila.utils [None req-22cd7b29-a383-44cd-8cb8-1c639a3034dc - - - - - -] Retrying manila.share.manager.ShareManager.init_host.<locals>._driver_setup in 600.0 seconds as it raised ShareBackendException: [%(be)s] Ceph client failed to connect.. log_it /var/lib/openstack/lib/python3.10/site-packages/tenacity/before_sleep.py:65 *4 -> *My ceph cluster is healthy 5 -> My manila confs look like (what could be wrong here)? conf: manila: DEFAULT: debug: true enabled_share_protocols: NFS,CIFS,CEPHFS enabled_share_backends: cephfsnative1 cephfsnative1: driver_handles_share_servers: False share_backend_name: CEPHFSNATIVE1 share_driver: manila.share.drivers.cephfs.driver.CephFSDriver cephfs_conf_path: /etc/ceph/ceph.conf cephfs_protocol_helper_type: CEPHFS cephfs_auth_id: manila cephfs_cluster_name: rook-ceph ( my rook-ceph cluster name) cephfs_filesystem_name: myfs (i created this fs manually) *6 -> P*ermissions for the user manila ceph auth get-or-create client.manila -o manila.keyring \ mgr 'allow rw' \ mon 'allow r' *7 -> *ceph --version ceph version 17.2.6 (d7ff0d10654d2280e08f1ab989c7cdf3064446a5) quincy (stable) openstackhelm Manila Chart name: manila version: 0.1.7 Hope to hear from you soon with a solution Thank you!

2 1

Openstack unable to login
by Lohit S 13 Jun '24

13 Jun '24

Hi Team, I am new to OpenStack. I have completed DevStack development, and I used OpenStack during that time without any issues. However, now when I try to log in to the OpenStack dashboard, it shows the message "An error occurred authenticating. Please try again later." How can I fix this issue? while checking the "systemctl status devstack@*" command -------------------------------------------------- devstack(a)etcd.service - Devstack devstack(a)etcd.service Loaded: loaded (/etc/systemd/system/devstack(a)etcd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2024-06-12 23:48:33 IST; 13min ago Process: 1534 ExecStart=/opt/stack/bin/etcd --name lohit22-VirtualBox --data-dir /opt/stack/data/etcd --initial-cluster-state new --initial-cluster-token etcd-cluster-01 --initial-cluster lohit22-Vir> Main PID: 1534 (code=exited, status=1/FAILURE) CPU: 23ms Notice: journal has been rotated since unit was started, output may be incomplete. ------------------------------

1 0

[kolla] Cancelling weekly meeting today (12th June 2024)
by Michał Nasiadka 12 Jun '24

12 Jun '24

Hello Koalas, Sorry for late notice - but I need to cancel the weekly meeting today due to absence of key contributors. Let’s meet next week. Best regards, Michal

1 0

[oslo] Remove eventlet from openstack.
by Daniel Bengtsson 12 Jun '24

12 Jun '24

Hi there, In the project to remove eventlet from openstack[1], we need to adapt oslo.service. The oslo.service project is strongly linked to eventlet, so rather than adapting the project, it would be wiser to deprecate it and replace it with cotyledon and futurist. The cotyledon project was created by openstack maintainers to replace oslo.service. It is already used in openstack by the telemetry project, for example. The oslo.service project has been created on top of eventlet to offer two main functionalities, periodic tasks and workers process management. The first feature has been replaced by another library called futurist[2] and the second is surpassed by cotyledon. More details in the project readme[3] about the difference with oslo.service. I would like to have your feedback and opinion on the deprecation of olso.service and it's replacement by cotyledon and futurist. In any case, we'll have to adapt the project, which is why replacing oslo.service with cotyledon seems to me the best solution, rather than having two similar projects doing the same thing. [1] https://review.opendev.org/c/openstack/governance/+/902585 [2] http://docs.openstack.org/developer/futurist/ [3] https://github.com/sileht/cotyledon/blob/main/README.rst -- Daniel Bengtsson Software Engineer

8 16

[nova] Spec review day on July 1th
by Sylvain Bauza 11 Jun '24

11 Jun '24

Hey folks, We'll have a second specs review day on Monday July 1th. Please make sure to update your specs before that day, so we can start to review it. Some folks would maybe off due to some holidays but they'll try to review all the specs during this week. Thanks, -Sylvain

1 0

[openstack charm][tc] openstack-charms still need PTL appointment
by Ghanshyam Mann 11 Jun '24

11 Jun '24

Hello Felipe, openstack-charm team, I tried to reach out to you on IRC but could not connect. This is regarding openstack-charm PTL appointment for the 2024.2 cycle. I am not sure if you noticed or not but there are some comments for you to fix on your PTL appointment. Please check the below Gerrit change and fix the same or let us know if there is a change in the plan. - https://review.opendev.org/c/openstack/governance/+/914254 -gmann

2 3