September 2022 - openstack-discuss

[kolla-ansible] Error while upgrading from xena to yoga
by wodel youchi 28 Sep '22

28 Sep '22

Hi, I am trying to upgrade from xena to yoga. I have created a test environment that resembles the production one using VMs. The deployment consists of 03 controllers and 03 compute/storage nodes. I am using Rokcy 8 as my base OS and I am using another VM as a deployer with a local registry. I followed the documentation here : https://docs.openstack.org/kolla-ansible/yoga/user/operating-kolla.html The precheks went well, but when deploying I got the following error : fatal: [ctrl02]: FAILED! => {"changed": true, "msg": "'Traceback (most > recent call last):\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 268, in _raise_for_status\\n > response.raise_for_status()\\n File > \"/usr/local/lib/python3.6/site-packages/requests/models.py\", line 960, > in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\n > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: > http+docker://localhost/v1.41/images/create?tag=yoga& > fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq\\n\\nDuring > handling of the above exception, > another exception occurred:\\n\\nTraceback (most recent call last):\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", > line 381, > in main\\n File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 660, in recreate_or_restart_container\\n self.pull_image()\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 451, in pull_image\\n repository=image, tag=tag, stream=True\\n > File \ > "/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, > in pull\\n self._raise_for_status(response)\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 270, in _raise_for_status\\n > raise create_api_error_from_http_exception(e)\\n File > \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", > line 31, in create_api_error_from_http_exception\\n raise cls(e, > response=response, explanation=explanation)\\n > docker.errors.NotFound: 404 Client Error for > http+docker://localhost/v1.41/images/create?tag=yoga > &fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq: > Not Found > *(\"manifest for > 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga > <http://10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga> not > found: manifest unknown: manifest unknown\")\\n'"}* > [deployer@deployer yoga]$ sudo docker images | grep yoga | grep rabbit quay.io/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB Any ideas? Regards.

2 2

[release][requirements][oslo][nova] How to fix a bug and release the fix in oslo.concurrency 4.5.x series
by Balazs Gibizer 28 Sep '22

28 Sep '22

Hi, So we have a bug[1] that was fixed in oslo.concurrency on master[2] and released as 5.0.1 and Zed is released with 5.0.1. The issue is present in stable/yoga as well. There we have oslo.concurrency upper constraint pinned to 4.5.0 [3]. 1) How can I backport [2] to the 4.5.x series of oslo.concurrency to release 4.5.2 with the fix? I don't see a branch that I could use for this. 2) If #1) is solved and 4.5.2 is released can I propose an upper constraint bump on stable/yoga from 4.5.0 to 4.5.2? 3) If #1) and #2) is done. Can I propose a minimum requirement bump in nova's requirements.txt from >= 4.5.0 to >= 4.5.2 on stable/yoga? Cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1988311 [2] https://review.opendev.org/c/openstack/oslo.concurrency/+/855714 [3] https://github.com/openstack/requirements/blob/e64217c9f9316675f57e14ff559b…

4 5

[cinder] Bug Report 09-28-2022
by Sofia Enriquez 28 Sep '22

28 Sep '22

This is a bug report from 09-21-2022 to 09-28-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1990053 "Cinder NFS backend with image-volume cache creates volumes with the wrong size." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990846 "NetApp FC: Not filterings WWPNs correctly in multiple HA pair deployments." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990946 "Dell PowerFlex: Size shown for a volume doesn't match powerflex backend allocation." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1991068 "Duplicate config option barbican in tempest plugins cinder and barbican." Unassigned. - https://bugs.launchpad.net/os-brick/+bug/1939390 "Missing dependency: lsscsi." Unassigned. Incomplete - https://bugs.launchpad.net/os-brick/+bug/1990825 "Should wait for all devices to appear?." Cheers, -- 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

Regarding Magnum configuration on Xena Openstack
by Adivya Singh 28 Sep '22

28 Sep '22

Hi Team, Can we have standard inputs to put and test to implement Containerization in Xena Openstack installed using ansible Regards Adivya Singh

2 3

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 27 Sep '22

27 Sep '22

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with details as follows: Date: 28th September, 2022 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC since we do roll call and also discuss topics on IRC (if the author is more comfortable in written format). Thanks and regards Rajat Dhasmana

1 0

Unable to create access rules 'state:error' | Wallaby | Tripelo | NetApp
by Swogat Pradhan 27 Sep '22

27 Sep '22

Hi, When i am trying to create access rule for manila share, the rules are created in error state. Here is the manila share log: 2022-09-23 19:03:58.557 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:01.720 26 INFO manila.share.manager [req-3d66c534-a782-414b-a0a7-2bdd57f57b8f - - - - -] Updating share status 2022-09-23 19:04:58.554 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server [req-5f035b4a-7dc8-4e61-bbd5-d38d4b81a00d c1905e3c5a374924980e851840e7f028 5d922243077045c48fe4b075e386551b - - -] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 216, in wrapped 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/utils.py", line 568, in wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3965, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server_id=share_server_id) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3981, in update_access_for_instances 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 302, in update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 341, in _update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 409, in _update_rules_through_share_driver 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/drv_single_svm.py", line 104, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server delete_rules, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py", line 2347, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server helper.update_access(share, share_name, access_rules) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 36, in wrapped_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return source_func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 34, in source_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 115, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server auth_methods = self._get_auth_methods() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 222, in _get_auth_methods 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server kerberos_enabled = self._client.is_kerberos_enabled() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_cmode.py", line 1896, in is_kerberos_enabled 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = self.send_request('kerberos-config-get', api_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_base.py", line 90, in send_request 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server use_zapi=use_zapi) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 710, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server na_element, api_args=api_args, enable_tunneling=enable_tunneling) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 380, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server raise NaApiError(code, msg) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist Please suggest how to mitigate this issue. With regards, Swogat Pradhan

2 2

[tacker] Critical bug report and backport the fix
by Yuta Kazato 27 Sep '22

27 Sep '22

Hi tacker team, As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`. I think this is a critical issue because users often set resource names that contain `-`. Fortunately, the fix patch [2] has already been submitted. I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think? [1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206 Yuta -- Yuta Kazato (風戸雄太) NTT Network Innovation Center. tel: +81-422-59-6754 mail: yuta.kazato.nw(a)hco.ntt.co.jp

3 2

Create the TripleO container images using the command in Xena
by Suranga Prabhath 27 Sep '22

27 Sep '22

Hi All, I.m going to install OpenStack Xena on CentOS 8.5. I'm following the TripleO in RDO Xena Release. I followed the RDO guide & enable the required packages. Package installation is successful, but the pulling of the triple container imagers using the command was unsuccessful. Here is the command I use. openstack tripleo container image build --base ubi8 --debug --distro centos \ --namespace tripleoxena --prefix openstack --tag cloudsig-xena \ --push --registry 172.22.1.10::8787 \ --volume /etc/yum.repos.d:/etc/distro.repos.d:z --volume /etc/pki/rpm-gpg:/etc/pki/rpm-gpg:z --volume /etc/dnf/vars:/etc/dnf/vars:z \ --work-dir ~/workdir After executing the above command error was received & I attach it to this mail. Please provide me with a solution for this. -- Thanks & Regards, *Suranga Prabhath,* System Administrator hSenid Software International *Sri Lanka* *M* : +94 00 000 0000 *P* : +94 11 268 3751 *F* : +94 11 268 3951 *Singapore* *M* : +65 00 000 000 *P* : +65 65 332 140 *F* : +65 62 910 023 <http://www.hsenid.com/> <http://www.hsenidmobile.com/> <https://www.facebook.com/hSenid.Software.International/> <https://twitter.com/hsenid_biz> <https://www.linkedin.com/company/hsenid-business-solutions> <https://www.youtube.com/user/hsenidbiz> *www.hSenid.com* <http://www.hsenid.com/> <https://www.google.com/url?q=http://www.hsenidmobile.com/&source=gmail-html…> *Disclaimer*: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. The content and opinions contained in this email are not necessarily those of hSenid Mobile Solutions. If you have received this email in error please contact the sender.

1 0

[kolla-ansible][Yoga] What are the benefits to run libvirt daemon on host rather on a container?
by wodel youchi 27 Sep '22

27 Sep '22

Hi, What are the benefits to run libvirt daemon directly on the host rather than on a container? In Yoga's release note, it is said : "Currently this is only supported for fresh deployments without an existing nova_libvirt container" But Also it it is said : "Adds a kolla-ansible nova-libvirt-cleanup command, which may be used to clean up the nova_libvirt container. This may be useful if switching to a host libvirt daemon". Is switching supported? I am in ther verge of upgrading from Xena to Yoga and I ma wondering about this. - What is the gain to use libvirt daemon? - Could the switch be done after the upgrade to Yoga? Regards.

2 1

[kolla-ansible] question about network nodes number
by wodel youchi 27 Sep '22

27 Sep '22

Hi, Is it a good idea to configure more than 02 network nodes? Regards.

2 1