April 2023 - openstack-discuss - lists.openstack.org

[neutron] Deprecate networking-odl project
by Rodolfo Alonso Hernandez 24 May '23

24 May '23

Hello all: During the last releases, the support for "networking-odl" project has decreased. Currently there is no active developer or maintainer in the community. This project depends on https://www.opendaylight.org/; the latest version released is Sulfur (16) while the version still used in the CI is Sodium (11) [1]. I would like first to make a call for developers to update this project. But if this is not possible, I will then start the procedure to deprecate it [2] (**not to retire it**). Regards. [1] https://github.com/openstack/networking-odl/blob/db5c79b3ee5054feb8a17df130… [2] https://docs.openstack.org/project-team-guide/repository.html#deprecating-a…

3 3

Re: 答复: [ptl] Need PTL volunteer for OpenStack Sahara
by Ghanshyam Mann 18 May '23

18 May '23

Thanks Jerry, Brin for the updates and showing interest in Sahara project. In PTG discussion, there were some concern on Sahara maintenance even we had PTL volunteer to lead this project but not much things got merged and gate was broken many times. But let me discuss it in TC meeting tomorrow and update here. -gmann ---- On Mon, 10 Apr 2023 00:22:08 -0700 Brin Zhang(张百林) wrote --- > Hi Gmann, > Jerry Zhou works the same company as qiujunting (Qiujunting has out of the office, so he cannot response us, I am so sorry), and he will be involved in Sahara. > Hope TC can add him in Sahara team, let him gradually complete the maintenance of the Sahara project. > Thanks. > > brinzhang > > -----邮件原件----- > 发件人: Jerry Zhou (周鑫勇) zhouxinyong(a)inspur.com> > 发送时间: 2023年4月7日 11:10 > 收件人: gmann(a)ghanshyammann.com; Juntingqiu Qiujunting (邱军婷) qiujunting(a)inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org; Tom Guo(郭涛2810) guotao.bj(a)inspur.com>; Brin Zhang(张百林) zhangbailin(a)inspur.com>; Weiting Kong (孔维亭) kongweiting(a)inspur.com> > 主题: 答复: [ptl] Need PTL volunteer for OpenStack Sahara > > Hi Gmann, > I can lead this project. > > -----邮件原件----- > 发件人: Ghanshyam Mann gmann(a)ghanshyammann.com> > 发送时间: 2023年3月23日 2:35 > 收件人: Qiujunting qiujunting(a)inspur.com>; openstack-discuss openstack-discuss(a)lists.openstack.org> > 主题: [ptl] Need PTL volunteer for OpenStack Sahara > > Hi Qiu, > > I am reaching out to you as you were PTL for OpenStack Sahara project in the last cycle. > > There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project. > > - https://etherpad.opendev.org/p/2023.2-leaderless > > Also, if anyone else would like to help leading this project, this is time to let TC knows. > > -gmann > >

4 7

[heat][magnum][tacker] Future of SoftwareDeployment support
by Takashi Kajinami 10 May '23

10 May '23

Hello, We discussed this briefly in the past thread where we discussed maintenance of os-*-agent repos, and also talked about this topic during Heat PTG, but I'd like to formalize the discussion to get a clear agreement. Heat has been supporting SoftwareDeployment resources to configure software in instances using some agents such as os-collect-config[1]. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… This feature was initially developed to be used by TripleO (IIUC), but TripleO is retired now and we are losing the first motivation to maintain the feature. # Even TripleO replaced most of its usage of softwaredeployment by config-download lately. Because the heat project team has drunk dramatically recently, we'd like to put more focus on core features. For that aim we are now wondering if we can deprecate and remove this feature, and would like to hear from anyone who has any concerns about this. Quickly looking through the repos, it seems currently Magnum and Tacker are using SoftwareDeployment, and it'd be nice especially if we can understand their current requirements. 1. Magnum It seems SoftwareDeployment is used by k8s_fedora_atomic_v1 driver but I'm not too sure whether this driver is still supported, because Fedora Atomic was EOLed a while ago, right ? 2. Tacker SoftwareDeployment can be found in only test code in the tacker repo. We have some references kept in heat-translator which look related to TOSCA templates. Thank you, Takashi Kajinami

4 8

[all][tc][release] Hold the Python3.8 dropping
by Ghanshyam Mann 09 May '23

09 May '23

Hello Everyone, As you know the gate is breaking due to Python3.8 drop[1][2], which we discussed in the TC channel and meeting[3]. TC is preparing the guidelines on not dropping Python3.8 in 2023.2 pti. Meanwhile, governance guidelines are prepared, this email is a heads-up to hold the dropping of Python3.8 from your project/repo. Do not bump the min py version in setup.cfg (do not bump version in python_requires ). @Release team, It will be helpful if you can check/hold the release of any project/lib dropping the Python3.8. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033450.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033454.h… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… -gmann

1 1

[openstack-ansible] Proposing Neil Hanlon for core reviewer
by Dmitriy Rabotyagov 04 May '23

04 May '23

Hi everyone, I'm pleased to propose Neil Hanlon as OpenStack-Ansible Core Reviewer. Neil has helped us a lot lately with maintenance of RHEL-like distros - both CentOS Stream and Rocky Linux, and basically has brought in support for the last one. Neil is present at meetings and always is responsive in IRC. At the same time they were providing useful reviews lately [1] If there are no objections, I will add Neil to the team on 25th of April 2023. Until then, please feel free to provide your feedback/opinions on the matter. [1] https://www.stackalytics.io/report/contribution?module=openstackansible-gro…

6 7

[all][tc][vitrage] Final call for Vitrage project maintainers
by Ghanshyam Mann 03 May '23

03 May '23

Hello Everyone, You might have noticed that the Vitrage project is leaderless in this cycle[1]. Eyal, who was the previous PTL and the only maintainer of this project for more than two years[2], will not be able to continue in this project[3]. We thank and appreciate all previous maintainers' work on this project. This is the final call for maintainers. If anyone is using or interested in this project, this is the right time to step up and let us know in this email or IRC(OFTC) #openstack-tc channel. If there is no response by the end of April 2023, we will discuss the retirement of this project. [1] https://etherpad.opendev.org/p/2023.2-leaderless [2] https://www.stackalytics.io/?module=vitrage-group&release=wallaby [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033333.h… -gmann

2 2

[OpenvSwitch][Neutron] native flow based firewall Vs LinuxBridge Iptables firewall
by Satish Patel 02 May '23

02 May '23

Folks, As we know, openvswitch uses a linuxbridge based firewall to implement security-groups on openstack. It works great but it has so many packet hops. It also makes troubleshooting a little complicated. OpenvSwitch does support native firewall features in flows, Does it mature enough to implement in production and replace it with LinuxBridge based IPtables firewall? ~S

3 3

[horizon][nova][masakari] Instances created with "Any AZ" problem
by Nguyễn Hữu Khôi 02 May '23

02 May '23

Hello guys. I playing with Nova AZ and Masakari https://docs.openstack.org/nova/latest/admin/availability-zones.html Masakari will move server by nova scheduler. Openstack Docs describe that: If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I see that everyone usually creates instances with "Any Availability Zone" on Horzion and also we don't specify AZ when creating instances by cli. By this way, when we use Masakari or we miragrated instances( or evacuate) so our instance will be moved to other zones. Can we attach AZ to server create requests API based on Any Availability Zone to limit instances moved to other zones? Thank you. Regards Nguyen Huu Khoi

5 20

[kolla-ansible][all][nova][zed][latest] USB passthrough / Hot-plug / Cold-plug
by Modyngs 02 May '23

02 May '23

090c090cFolks, A USB device (not necessarily a mass/Flash drive) needs to be connected to one of the VMs (an openstack instance). Openstack installed with kolla-ansible{Latest version/ Also tested on Zed} ALL IN ONE Deployments on ubuntu server 22.04 ( Core i9 12900K). I found the [nova-libvirt] container which contains *virsh *and is able to edit it or use custom config for VMs. I've gone through lots of the docs, to name a few: https://libvirt.org/formatdomain.html https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://wiki.openstack.org/wiki/Nova/proposal_about_usb_passthrough https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-libvirt-config… https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/… but none of them worked for me!! To reproduce: *Cold-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *%Turn the Desired VM off* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running - instance-0000000a shut off *# virsh edit instance-0000000a* Add the changes [1][2][3][4],... ( many efforts have been done but few samples of them are) [1]: under <devices> added <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [2]:under <devices> added <controller type='usb' index='0'/> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [3]: under <devices> added <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [4]: under <devices> added <controller type='usb' model='nec-xhci' index='0'/> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [5]: <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='usb' bus='1' port='2'/> <controller type='usb' index='0'/> </hostdev> *%Start the VM* *expected behavior:* when login to the VM, lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *OR *virsh dumpxml instance-0000000a > instance-0000000a.xml and then change the configs as above and then virsh attach-device instance-0000000a --file /path/to/updated-instance-0000000a.xml --config *Hot-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running 20 instance-0000000a running *#nano USB.xml* *%add changes explained in *[1][2][3][4],... *$ virsh attach-device instance-0000000a /path/to/USB.xml/file* *expected behavior:* lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *Can you please guide me through this? Any recommendation would be much appreciated!Any custom changes comes to your mind ( Reply it) would be solution for this problem /;* Thanks Best regards

2 1

Offline Openstack Release:Train Deployment
by Vineet Thakur 02 May '23

02 May '23

Greetings openstack community members, It's regarding the deployment of openstack release: train on CentoOS 7.9 environment by using openstack-ansible tool. (Offline environment) We are facing challenges to download the packages, some package links are not accessible or somewhere PIP packages are not available as per the constraint requirement list. See: https://artifacts.ci.centos.org/sig-cloudinstance/centos-7-191001/x86-64/ce… For pip packages: https://opendev.org/openstack/requirements/raw/0cfc2ef6318b639bb4287fa051ea… During installation we are facing a lot of errors, and not sure what would be the best approach in such scenarios where packages are not available or need to be downloaded from random sites. We are in the mid of a mega deployment and appreciate it if you can guide us through. Awaiting your response, thank you. Kind Regards, Vineet Thakur

3 3

[kolla-ansible][zed][15.1.0] Horizon failed to load trunk and QoS
by Stefan Bryzga 01 May '23

01 May '23

Hi all, Some time ago I deployed a small cluster with kolla-ansible v15.1.0. Before deployment I enabled neutron_qos and neutron_trunk flags in /etc/kolla/globals.yml. Both functions work fine via cli and I can create new entries via dashboard however horizon won't display created trunks/qos on the page (It shows "No items to display"). In web browser console I get this error while loading page: TypeError: Cannot read properties of undefined (reading 'data') at addTrackBy (output.0a9483334bbd.js:1115:59) at processQueue (output.43a09e34a303.js:1581:786) at output.43a09e34a303.js:1585:110 at Scope.$digest (output.43a09e34a303.js:1636:200) at Scope.$apply (output.43a09e34a303.js:1643:269) at done (output.43a09e34a303.js:1356:123) at completeRequest (output.43a09e34a303.js:1375:20) at XMLHttpRequest.requestLoaded (output.43a09e34a303.js:1368:1) 'Possibly unhandled rejection: {}' Does anyone knows how to fix this? Should I modify any configs to display new entries in horizon? Best Regards, Stefan

2 1

[neutron] Neutron CI not working
by Rodolfo Alonso Hernandez 28 Apr '23

28 Apr '23

Hello Neutrinos: There are some problems in a set of nodes that we are using for tempest tests. This is also affecting other projects like Octavia. Please follow [1] for more information. Yatin has collected information of the error and the affected nodes. Actions: * Temporarily disable these nodes from the pool [2]. That will allow us (Neutron) to continue the CI testing. * Send a support ticket to the node provider. Once we have more information, we'll provide it. Before [2] is merged, please hold your rechecks for the tempest jobs in Neutron. Regards. [1]https://bugs.launchpad.net/neutron/+bug/2017992 [2]https://review.opendev.org/c/openstack/project-config/+/881810

1 1

[neutron] CI meeting on May 2nd cancelled
by Slawek Kaplonski 28 Apr '23

28 Apr '23

Hi, I will be on PTO next Tuesday so lets cancel CI meeting this time. See You on the meeting on May 9th. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[tripleo] Nominate dbengt for tripleo-core !
by Lukas Bezdicka 28 Apr '23

28 Apr '23

Hello, I'd like to nominate Daniel Bengtsson as tripleo-core. He works in upgrades and he'll have to maintain train, wallaby and zed for quite a while. He is a long term contributor to tripleo and oslo. I trust his judgement and I hope you'll support his nomination! Thanks, Lukas Bezdicka

6 6

[CloudKitty] Cancelling weekly meeting 1st May
by Rafael Weingärtner 28 Apr '23

28 Apr '23

Hello guys, May 1st is a public holiday for most of the core reviewers. Therefore, we will be canceling that meeting. If you need any assistance until the next meeting, you can reach me via e-mail. Best regards, -- Rafael Weingärtner

1 0

[kolla] Cancelling weekly meeting 3rd May
by Michał Nasiadka 28 Apr '23

28 Apr '23

Hello Koalas, Since 3rd of May is public holiday in Poland and other cores are on vacation - cancelling weekly meeting. Let’s meet again on 10th May. Best regards, Michal

1 0

[magnum] Propose deprecation of Docker Swarm, CoreOS, fedora-ironic
by Jake Yip 28 Apr '23

28 Apr '23

Hi, Due to limited resources, Magnum team has decided to put most effort into supporting the most popular use case - Kubernetes on Fedora CoreOS. In light of that, we are seeking maintainers for the less well maintained drivers / COE - Docker Swarm, CoreOS and fedora-ironic drivers. The reasons are as follows: - Docker Swarm - It uses Fedora Atomic which has been EOL [1] - CoreOS - It is EOL [2] - fedora-ironic - Not tested, unsure if it is still working If anyone wants to take up maintenance of any of the above, we will be glad. Please let us know either through the ML or at the Magnum meetings. If there are no suitable maintainers, we will start the deprecation of these before end of Antelope. Regards, Jake [1]: https://projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/ [2]: https://www.redhat.com/en/technologies/cloud-computing/openshift/what-was-c… -- Jake Yip Magnum Team

2 3

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 28 Apr '23

28 Apr '23

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Have a nice weekend!

1 0

Re: openstack-discuss Digest, Vol 54, Issue 88
by BEDDA Fadhel 28 Apr '23

28 Apr '23

Good morning, I am still looking for a complete and clear procedure to set up an openstack solution on a vmware worksation virtual machine: ubuntu or centos. THANKS Le lun. 17 avr. 2023 à 17:30, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. Re: [Kolla-ansible][Yoga] Cannot live migrate VMs (wodel youchi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 11 Apr 2023 12:57:47 +0100 > From: wodel youchi <wodel.youchi(a)gmail.com> > To: Pierre Riteau <pierre(a)stackhpc.com> > Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: Re: [Kolla-ansible][Yoga] Cannot live migrate VMs > Message-ID: > <CAJV_UBDH4tJ11pkOagYpWNVCrZHruTmA6A-k9P= > DLrqchPvNPg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > Indeed, there was a mistake in the cinder.conf file. > Thanks. > > Regards. > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > Le mar. 11 avr. 2023 ? 10:45, Pierre Riteau <pierre(a)stackhpc.com> a ?crit > : > > > You should check the status of your Cinder services. > > > > On Sun, 9 Apr 2023 at 19:43, wodel youchi <wodel.youchi(a)gmail.com> > wrote: > > > >> Hi, > >> > >> I cannot live-migrate any VM I have. > >> All my compute nodes are enabled. I have a few VMs, I am in the testing > >> phase. > >> I tried to live-migrate toward an empty node, then toward a node which > >> already had a VM in it. It is the same problem. > >> > >> In the log files I have : > >> > >> Source node : > >> Source > >> > >>> ==> /var/log/kolla/nova/nova-compute.log <== > >>> 2023-04-09 11:32:49.419 7 INFO nova.compute.resource_tracker > >>> [req-4e91d562-d7ad-4585-a827-3db6277fd81e - - - - -] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Updating resource usage from > >>> migration f60eb077-8e1c-404a-aca5-64e5609ca02c > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [-] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Pre live migration failed at > >>> computehci02: oslo_messaging.rpc.client.RemoteError: Remote error: > >>> ClientException Gateway Time-out (HTTP 504) > >>> ['Traceback (most recent call last):\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", > >>> line 165, in _process_incoming\n res = > >>> self.dispatcher.dispatch(message)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 309, in dispatch\n return self._do_dispatch(endpoint, method, > ctxt, > >>> args)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 229, in _do_dispatch\n result = func(ctxt, **new_args)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 72, in wrapped\n context, exc, binary)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 63, in wrapped\n return f(self, context, *args, **kw)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/utils.py", > >>> line 1439, in decorated_function\n return function(self, context, > *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 213, in decorated_function\n kwargs[\'instance\'], e, > >>> sys.exc_info())\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 201, in decorated_function\n return function(self, context, > *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8367, in pre_live_migration\n bdm.save()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8304, in pre_live_migration\n connector=connector, > >>> mountpoint=bdm.device_name)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 395, in wrapper\n res = method(self, ctx, *args, **kwargs)\n', > ' > >>> File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 433, in wrapper\n res = method(self, ctx, volume_id, *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 813, in attachment_create\n instance_uuid=instance_id)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 801, in attachment_create\n volume_id, _connector, > instance_id)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/api_versions.py", > >>> line 421, in substitution\n return method.func(obj, *args, > **kwargs)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/v3/attachments.py", > >>> line 39, in create\n retval = self._create(\'/attachments\', body, > >>> \'attachment\')\n', ' File > >>> "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/base.py", > >>> line 306, in _create\n resp, body = self.api.client.post(url, > >>> body=body)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 227, in post\n return self._cs_request(url, \'POST\', > **kwargs)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 215, in _cs_request\n return self.request(url, method, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 201, in request\n raise exceptions.from_response(resp, > body)\n', > >>> 'cinderclient.exceptions.ClientException: Gateway Time-out (HTTP > 504)\n']. > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Traceback (most recent call > last): > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8501, in _do_pre_live_migration_from_source > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] block_migration, disk, dest, > >>> migrate_data) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/rpcapi.py", > >>> line 948, in pre_live_migration > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] **msg_args) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/client.py", > >>> line 192, in call > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] retry=self.retry, > >>> transport_options=self.transport_options) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/transport.py", > >>> line 128, in _send > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] > >>> transport_options=transport_options) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", > >>> line 691, in send > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] > >>> transport_options=transport_options) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", > >>> line 681, in _send > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] raise result > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] > >>> oslo_messaging.rpc.client.RemoteError: Remote error: ClientException > >>> Gateway Time-out (HTTP 504) > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] ['Traceback (most recent call > >>> last):\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", > >>> line 165, in _process_incoming\n res = > >>> self.dispatcher.dispatch(message)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 309, in dispatch\n return self._do_dispatch(endpoint, method, > ctxt, > >>> args)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 229, in _do_dispatch\n result = func(ctxt, **new_args)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 72, in wrapped\n context, exc, binary)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 63, in wrapped\n return f(self, context, *args, **kw)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/utils.py", > >>> line 1439, in decorated_function\n return function(self, context, > *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 213, in decorated_function\n kwargs[\'instance\'], e, > >>> sys.exc_info())\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 201, in decorated_function\n return function(self, context, > *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8367, in pre_live_migration\n bdm.save()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8304, in pre_live_migration\n connector=connector, > >>> mountpoint=bdm.device_name)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 395, in wrapper\n res = method(self, ctx, *args, **kwargs)\n', > ' > >>> File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 433, in wrapper\n res = method(self, ctx, volume_id, *args, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 813, in attachment_create\n instance_uuid=instance_id)\n', ' > File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__\n self.force_reraise()\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise\n raise self.value\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 801, in attachment_create\n volume_id, _connector, > instance_id)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/api_versions.py", > >>> line 421, in substitution\n return method.func(obj, *args, > **kwargs)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/v3/attachments.py", > >>> line 39, in create\n retval = self._create(\'/attachments\', body, > >>> \'attachment\')\n', ' File > >>> "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/base.py", > >>> line 306, in _create\n resp, body = self.api.client.post(url, > >>> body=body)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 227, in post\n return self._cs_request(url, \'POST\', > **kwargs)\n', > >>> ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 215, in _cs_request\n return self.request(url, method, > >>> **kwargs)\n', ' File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 201, in request\n raise exceptions.from_response(resp, > body)\n', > >>> 'cinderclient.exceptions.ClientException: Gateway Time-out (HTTP > 504)\n']. > >>> 2023-04-09 11:33:30.118 7 ERROR nova.compute.manager [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] > >>> 2023-04-09 11:33:30.157 7 INFO nova.compute.manager [-] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Swapping old allocation on > >>> dict_keys(['2857ae62-3519-4b13-b700-858c827dd78d']) held by migration > >>> f60eb077-8e1c-404a-aca5-64e5609ca02c for instance > >> > >> > >> > >> In the destination node : > >> > >>> nova-compute.log > >>> > >>> > >>> > >>> > >>> *2023-04-09 11:32:30.052 7 WARNING os_brick.initiator.connectors.nvmeof > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] Process execution > error > >>> in _get_host_uuid: Unexpected error while running command.Command: > blkid > >>> overlay -s UUID -o valueExit code: 2Stdout: ''Stderr: '': > >>> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error > while > >>> running command.* > >>> > >>> 2023-04-09 11:33:05.354 7 INFO nova.compute.resource_tracker > >>> [req-9d480442-87f7-4d4e-a866-c46d645ac7f2 - - - - -] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Updating resource usage from > >>> migration f60eb077-8e1c-404a-aca5-64e5609ca02c > >>> 2023-04-09 11:33:05.392 7 WARNING nova.compute.resource_tracker > >>> [req-9d480442-87f7-4d4e-a866-c46d645ac7f2 - - - - -] Instance > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7 has been moved to another host > >>> computehci01(computehci01). There are allocations remaining against the > >>> source host that might need to be removed: {'resources': {'VCPU': 1, > >>> 'MEMORY_MB': 2048}}. > >>> 2023-04-09 11:33:30.086 7 ERROR nova.volume.cinder > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Create attachment failed for > volume > >>> 3d7bd0af-5e4c-48fc-a027-f6c9dd6280bb. Error: Gateway Time-out (HTTP > 504) > >>> Code: 504: cinderclient.exceptions.ClientException: Gateway Time-out > (HTTP > >>> 504) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] Exception during > >>> message handling: cinderclient.exceptions.ClientException: Gateway > Time-out > >>> (HTTP 504) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server Traceback > >>> (most recent call last): > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", > >>> line 165, in _process_incoming > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server res = > >>> self.dispatcher.dispatch(message) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 309, in dispatch > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> self._do_dispatch(endpoint, method, ctxt, args) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", > >>> line 229, in _do_dispatch > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server result = > >>> func(ctxt, **new_args) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 72, in wrapped > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server context, > >>> exc, binary) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__ > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> self.force_reraise() > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server raise > >>> self.value > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", > >>> line 63, in wrapped > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> f(self, context, *args, **kw) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/utils.py", > >>> line 1439, in decorated_function > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> function(self, context, *args, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 213, in decorated_function > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> kwargs['instance'], e, sys.exc_info()) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__ > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> self.force_reraise() > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server raise > >>> self.value > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 201, in decorated_function > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> function(self, context, *args, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8367, in pre_live_migration > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > bdm.save() > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__ > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> self.force_reraise() > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server raise > >>> self.value > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", > >>> line 8304, in pre_live_migration > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> connector=connector, mountpoint=bdm.device_name) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 395, in wrapper > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server res = > >>> method(self, ctx, *args, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 433, in wrapper > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server res = > >>> method(self, ctx, volume_id, *args, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 813, in attachment_create > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> instance_uuid=instance_id) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 227, in __exit__ > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> self.force_reraise() > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", > >>> line 200, in force_reraise > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server raise > >>> self.value > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/volume/cinder.py", > >>> line 801, in attachment_create > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > volume_id, > >>> _connector, instance_id) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/api_versions.py", > >>> line 421, in substitution > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> method.func(obj, *args, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/v3/attachments.py", > >>> line 39, in create > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server retval = > >>> self._create('/attachments', body, 'attachment') > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/base.py", > >>> line 306, in _create > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server resp, > body > >>> = self.api.client.post(url, body=body) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 227, in post > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> self._cs_request(url, 'POST', **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 215, in _cs_request > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server return > >>> self.request(url, method, **kwargs) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server File > >>> > "/var/lib/kolla/venv/lib/python3.6/site-packages/cinderclient/client.py", > >>> line 201, in request > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server raise > >>> exceptions.from_response(resp, body) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> cinderclient.exceptions.ClientException: Gateway Time-out (HTTP 504) > >>> 2023-04-09 11:33:30.115 7 ERROR oslo_messaging.rpc.server > >>> 2023-04-09 11:33:30.238 7 INFO nova.virt.block_device > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Attempting to driver detach > volume > >>> 3d7bd0af-5e4c-48fc-a027-f6c9dd6280bb from mountpoint /dev/vda > >>> 2023-04-09 11:33:30.239 7 WARNING nova.virt.block_device > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Detaching volume from unknown > instance > >>> 2023-04-09 11:33:30.240 7 WARNING nova.virt.libvirt.driver > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] During detach_volume, instance > >>> disappeared.: nova.exception.InstanceNotFound: Instance > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7 could not be found. > >>> 2023-04-09 11:33:30.678 7 INFO nova.virt.libvirt.driver [-] [instance: > >>> f4c3ee82-d5cf-4b79-8608-76be7faeb2c7] Instance destroyed successfully. > >>> 2023-04-09 11:33:30.682 7 INFO os_vif > >>> [req-69822759-d982-4d01-b448-232796077002 > 0439953e7cfe4a13a1b4bb118b5dc3c4 > >>> b0f76b5c6dcb457fa716762bbf954837 - default default] Successfully > unplugged > >>> vif > >>> > VIFBridge(active=True,address=fa:16:3e:9b:92:46,bridge_name='qbr46651303-65',has_traffic_filtering=True,id=46651303-65e1-4809-95cc-7c2d97acf16b,network=Network(532470c1-dd2f-4505-8557-ba24e9d4062b),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_delete=False,vif_name='tap46651303-65') > >>> > >> > >> All I can see is > >> > >> > >> > >> > >> *b0f76b5c6dcb457fa716762bbf954837 - default default] Process execution > >> error in _get_host_uuid: Unexpected error while running command.Command: > >> blkid overlay -s UUID -o valueExit code: 2Stdout: ''Stderr: '': > >> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error > while > >> running command.* > >> > >> Searching the web I didn't find anything useful about this error, and I > >> don't know if it's the origin of the problem. > >> > >> My default storage is ceph rbd, I have an HCI deployment, and all my VMs > >> are for now created on Ceph only. But I have configured two other cinder > >> backends, NFS and LVM, but they are node used for now. > >> > >> Thanks in advance. > >> > >> Regards. > >> > > >

2 1

[release][cinder] please delete cinderlib stable/ussuri branch
by Brian Rosmaita 28 Apr '23

28 Apr '23

Hello Release Team, Some changes were bot-proposed recently to the cinderlib stable/ussuri branch, which was weird because that branch was tagged EOL by change I75092342fe684892f8a73eab9ad5da4515cb1da5. The change merged on 2022-08-31, and the ussuri-eol tag exists in the code repository, but apparently the branch was never deleted. Could you please delete the branch? thanks!

2 3

OpenStack Swift quota
by Xu, Wei [E CPE] 27 Apr '23

27 Apr '23

Hello OpenStack community, Right now, because we tend to limit each user's individual storage capacity, we're trying to implement account and container-level quotas on our OpenStack Swift cluster (Yoga version). Every time we tried to execute a command like "swift post -m quota-bytes: 500" using the Swift CLI client to implement account quotas, it returned a 403 error saying "403 Forbidden [first 60 chars of response] <html><h1>Forbidden</h1><p>Access was denied to this resourc", even if we are using an account already with the reseller/ResellerAdmin role, and both quotas added to the [pipeline:main] on our proxy server. Could you help us identify what could be behind this issue and how to resolve it? Also, it seems like default OpenStack Swift only supports account-level and container-level quota implementation. Is it possible to implement not only user-level but also project-level and domain-level quotas? I'm looking forward to hearing back from you. Thank you very much! Yours sincerely, Wei Xu, M.S. Research Assistant Department of ECpE, Iowa State University

3 9

[kolla-ansible][watcher]Time zone issue in container
by Stefan Bryzga 27 Apr '23

27 Apr '23

Hi all, Recently I created fresh deployment based on kolla-ansible yoga and debian 11. Everything works correctly except Watcher services. Containers are in constant restart loop. On Debian host OS time-related files are as follows: lrwxrwxrwx 1 root root 33 Mar 21 07:53 localtime -> /usr/share/zoneinfo/Europe/Warsaw -rw-r--r-- 1 root root 14 Mar 21 07:53 timezone x@control01:/etc$ cat timezone Europe/Warsaw However every container have: lrwxrwxrwx 1 root root 27 Apr 11 02:00 localtime -> /usr/share/zoneinfo/Etc/UTC -rw-r--r-- 1 root root 14 Mar 21 07:53 timezone (nova-api)[root@control01 etc]# cat timezone Europe/Warsaw In watcher logs I found error: 2023-04-27 10:08:12.607 7 ERROR python-watcher tzlocal.utils.ZoneInfoNotFoundError: 'Multiple conflicting time zone configurations found:\n/etc/timezone: Europe/Warsaw\n/etc/localtime is a symlink to: UTC\nFix the configuration, or set the time zone in a TZ environment variable.\n' 2023-04-27 10:08:12.607 7 ERROR python-watcher Which I believe is caused by wrong symlink for /etc/localtime in containers. Did anyone experience similar issue and know how to resolve it. Best regards, Stefan

2 2

[kolla-ansible] all-in-one deployment on single NIC
by Satish Patel 27 Apr '23

27 Apr '23

Folks, I am trying to create a lab with a single server which has a single NIC card and as you know kolla-ansible needs two nic for all-in-one (api and neutron nic). I want to test VLAN base provider for VMs so can I configure single nic on trunk port and create two VLAN interfaces foo.10 and foo.20 bridge and assign foo.10 to api and foo.20 for neutron. Does that make sense and will help the test lab? I was also reading somewhere that you need to create a veth interface two split single nic for kolla. Did anyone test kolla with single nic with two bridges to create dual nic simulation?

1 0

[neutron] [kolla-ansible] alembic mismatch, schema differences
by Gregory Orange 27 Apr '23

27 Apr '23

Hi all, We've caused ourselves some bother with our neutron database, and I found the following thread instructive, so I hope we can get some help to resolve the bother. https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03131… We're running kolla-ansible train (yes, upgrades planned). We wanted to test something with a wallaby container, and while mainly just pulling train versions of containers on a single compute node, we also changed openstack_release variable to wallaby in globals.yml - this was the mistake. Later that day, we ran kolla-ansible deploy --limit $HOST for a new compute node. We stopped at the following error, realising the above mistake. --- 2023-04-05 12:25:50.487 7 ERROR nova nova.exception.TooOldComputeService: Current Nova version does not support computes older than Victoria but the minimum compute service level in your cell is 40 and the oldest supported service level is 52. 2023-04-05 12:25:50.487 7 ERROR nova --- Now when we deploy a node it gets to task "Running Neutron bootstrap container" and gives error: ---- "alembic.script.revision.ResolutionError: No such revision or branch '6135a7bd4425'" ---- Using insight from the above list thread, I fetched DB entries: MariaDB [neutron]> select * from alembic_version; +--------------+ | version_num | +--------------+ | 5c85685d616d | | 6135a7bd4425 | +--------------+ Running the same from the test cluster which was deployed in the same way: MariaDB [neutron]> select * from alembic_version; +--------------+ | version_num | +--------------+ | 5c85685d616d | | c613d0b82681 | +--------------+ Also, comparing `neutron-db-manage history --verbose` across the two clusters, output is the same in both test and prod, except for the order of 2 lines: ---- -Branches into: 56893333aa52, 30018084ed99 -Branches into: c40fbb377ad, 67c8e8d61d5 +Branches into: 30018084ed99, 56893333aa52 +Branches into: 67c8e8d61d5, c40fbb377ad ---- Finally, I looked at the schema of the neutron database across the two. There are significant differences. for i in `mysql neutron -bNe "show tables;"`; do echo "TABLE: $i"; mysql neutron -e "desc $i;"; done > prod-neutron-descs Repeat for test. $ cat prod-neutron-descs | nc termbin.com 9999 https://termbin.com/8ppi $ cat test-neutron-descs | nc termbin.com 9999 https://termbin.com/cfqz Our cluster and Neutron in particular is operating fine, but we can't deploy new nodes to it. May I have some help on how to resolve this? Thank you, Greg.

4 8

[kolla-ansible][swift][ceph]
by Nguyễn Hữu Khôi 27 Apr '23

27 Apr '23

Hello guys. I am working to make openstack swift save data on ceph. I am using kolla ansible and see it need enable swift first but I don't want to make swift ring on my controller. I just want use external ceph. Pls you give me some advices Thank you Nguyen Huu Khoi

5 8