May 2023 - openstack-discuss - lists.openstack.org

[neutron] Bug Deputy Report May 22 - 28
by Yatin Karel 29 May '23

29 May '23

Hello Neutron Team !! Please find bug report from May 22nd to 28th, Undecided bugs needs further triage:- *Critical:-* - https://bugs.launchpad.net/neutron/+bug/2020363 - [stable/train/] openstacksdk-functional-devstack fails with POST_FAILURE Fixed with https://review.opendev.org/c/openstack/neutron/+/883890 Assigned to ykarel *High:-* - https://bugs.launchpad.net/neutron/+bug/2020698 - neutron-tempest-plugin-bgpvpn-bagpipe job unstable Job made non voting temporary with https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/884270 Assigned to bhaley - https://bugs.launchpad.net/neutron/+bug/2021457 - [fwaas]The firewall group without any port in active status Fix proposed https://review.opendev.org/c/openstack/neutron-fwaas/+/884335 Assigned to ZhouHeng *Medium:-* - https://bugs.launchpad.net/neutron/+bug/2020802 - Make DB migration "Add indexes to RBACs" conditional Unassigned *Low:-* - https://bugs.launchpad.net/neutron/+bug/2020552 - trunk_details missing sub port MAC addresses for LIST Requested more info Unassigned *Wishlist:-* - https://bugs.launchpad.net/neutron/+bug/2020358 - [RFE] Allow to limit conntrack entries per tenant to avoid "nf_conntrack: table full, dropping packet" Unassigned - https://bugs.launchpad.net/neutron/+bug/2020823 - [RFE] Add flavor/service provider support to routers in the L3 OVN plugin Assigned to Miguel Lavalle *Undecided:-* - https://bugs.launchpad.net/neutron/+bug/2020771 - [ml2/ovn] Binding_host_id shouldn't be set when a port is down Requested more info - https://bugs.launchpad.net/neutron/+bug/2020349 - Neutron Dynamic Routing : Connection to peers lost Discussion ongoing, possible misconfiguration - https://bugs.launchpad.net/neutron/+bug/2020328 - Concurrent create VM failed because of vif plug timeout Requested more info Thanks and Regards Yatin Karel

1 0

[nova][ops] EOL'ing stable/train ?
by Sylvain Bauza 26 May '23

26 May '23

Hi folks, in particular operators... We discussed yesterday during the nova meeting [1] about our stable branches and eventually, we were wondering whether we should EOL [2] the stable/train branch for Nova. Why so ? Two points : 1/ The gate is failing at the moment for the branch. 2/ Two CVEs (CVE-2022-47951 [3] and CVE-2023-2088 [4]) aren't fixed in this branch. It would be difficult to fix the CVEs in the upstream branch but hopefully AFAIK all the OpenStack distros already fixed them for their related releases that use Train. So, any concerns ? TBH, I'm not really happy with EOL, but it would be bizarre if we say "oh yeah we support Train backports" but we don't really fix the most important issues... -Sylvain (who will propose the train-eol tag change next week if he doesn't see any concern before) [1] https://meetings.opendev.org/meetings/nova/2023/nova.2023-05-23-16.01.log.h… [2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… [3] https://security.openstack.org/ossa/OSSA-2023-002.html [4] https://security.openstack.org/ossa/OSSA-2023-003.html

4 3

[nova]vnc and spice used together in openstack
by 啧啧啧 26 May '23

26 May '23

Hi, When using the console, we enabled both nova spicehtml5proxy and nova novancproxy on the controller node, and enabled vnc and spice on compute1 and compute2, respectively. We found that there was a problem with the coexistence of the two, The log is as follows.  ERROR oslo_messaging.rpc.server [req-28674cdd-f06e-466f-8611-516efc8fbe3c 069c1371a95e4ebaa59eea6ee70362bc dd4e9ff713be4311978334ae0d0c0a5e - default default] Exception during message handling: ValueError: Field `port' cannot be None 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-05-25 10:58:05.851 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-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 235, in inner 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     return func(*args, **kwargs) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     function_name, call_dict, binary, tb) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     self.force_reraise() 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     six.reraise(self.type_, self.value, self.tb) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/usr/lib/python3.6/site-packages/six.py", line 693, in reraise 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     raise value 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     return f(self, context, *args, **kw) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     kwargs['instance'], e, sys.exc_info()) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     self.force_reraise() 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     six.reraise(self.type_, self.value, self.tb) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/usr/lib/python3.6/site-packages/six.py", line 693, in reraise 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     raise value 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     return function(self, context, *args, **kwargs) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/nova/compute/manager.py", line 5906, in get_spice_console 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     access_url_base=CONF.spice.html5proxy_base_url, 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_versionedobjects/base.py", line 307, in __init__ 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     setattr(self, key, kwargs[key]) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_versionedobjects/base.py", line 72, in setter 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     field_value = field.coerce(self, name, value) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_versionedobjects/fields.py", line 207, in coerce 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     return self._null(obj, attr) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server   File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_versionedobjects/fields.py", line 185, in _null 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server     raise ValueError(_("Field `%s' cannot be None") % attr) 2023-05-25 10:58:05.851 7 ERROR oslo_messaging.rpc.server ValueError: Field `port' cannot be None I don't know why there is an appeal issue or what special mechanism OpenStack has for the console. I can only choose one. I hope you can help us. Thank you very much.

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 26 May '23

26 May '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

pep8 error of newest devstack
by Alex Song (宋文平) 26 May '23

26 May '23

Hi, When I check pep8 with the newest devstack env by the cmd ��tox �Ce pep8��, it raise many packages conflict. The log is as follows. root@song-ctrl:/opt/stack/cyborg# tox -e pep8 pep8 create: /opt/stack/cyborg/.tox/shared pep8 installdeps: -chttps://releases.openstack.org/constraints/upper/master, -r/opt/stack/cyborg/requirements.txt, -r/opt/stack/cyborg/test-requirements. txt ERROR: invocation failed (exit code 1), logfile: /opt/stack/cyborg/.tox/shared/log/pep8-1.log ============================================================================ ============================================================== log start ============================================================================ ============================================================== Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Collecting pbr!=2.1.0,>=0.11 (from -r /opt/stack/cyborg/requirements.txt (line 5)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/01/06/4ab11bf70db5a60689fc521b636 849c8593eb67a2c6bdf73a16c72d16a12/pbr-5.11.1-py2.py3-none-any.whl (112 kB) Collecting pecan!=1.0.2,!=1.0.3,!=1.0.4,!=1.2,>=1.0.0 (from -r /opt/stack/cyborg/requirements.txt (line 6)) Using cached pecan-1.4.2-py3-none-any.whl Collecting WSME>=0.10.1 (from -r /opt/stack/cyborg/requirements.txt (line 7)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/d2/a0/54b71fd2e1ab4f838acf472726a 14dadb6d1c77adc18d7e2c062dd955ff9/WSME-0.11.0-py3-none-any.whl (59 kB) Collecting eventlet>=0.26.0 (from -r /opt/stack/cyborg/requirements.txt (line 8)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/90/97/928b89de2e23cc67136eccccf1c 122adf74ffdb65bbf7d2964b937cedd4f/eventlet-0.33.3-py2.py3-none-any.whl (226 kB) Collecting oslo.i18n>=1.5.0 (from -r /opt/stack/cyborg/requirements.txt (line 9)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/62/5a/ced9667f5a35d712734bf3449af ad763283e31ea9a903137eb42df29d948/oslo.i18n-6.0.0-py3-none-any.whl (46 kB) Collecting oslo.config!=4.3.0,!=4.4.0,>=1.1.0 (from -r /opt/stack/cyborg/requirements.txt (line 10)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/ce/15/97fb14b7a1692693610a8e00e2a 08e4186d6cdd875b6ac24c912a429b665/oslo.config-9.1.1-py3-none-any.whl (128 kB) Collecting oslo.log>=5.0.0 (from -r /opt/stack/cyborg/requirements.txt (line 11)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/9c/24/526545a76513c741c65eeb70a85 c93287f10665147c7cff7e0eb24918d43/oslo.log-5.2.0-py3-none-any.whl (71 kB) Collecting oslo.context>=2.9.0 (from -r /opt/stack/cyborg/requirements.txt (line 12)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/7f/69/3a16785c49890cce2f7f14ee652 5c76e7116f9dad44f122f5e3670e43970/oslo.context-5.1.1-py3-none-any.whl (20 kB) ERROR: Cannot install oslo.messaging>=14.1.0 because these package versions have conflicting dependencies. The conflict is caused by: The user requested oslo.messaging>=14.1.0 The user requested (constraint) oslo-messaging===14.3.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dep endency-conflicts ============================================================================ =============================================================== log end ============================================================================ =============================================================== ERROR: could not install deps [-chttps://releases.openstack.org/constraints/upper/master, -r/opt/stack/cyborg/requirements.txt, -r/opt/stack/cyborg/test-requirements. txt]; v = InvocationError('/opt/stack/cyborg/.tox/shared/bin/python -m pip install -chttps://releases.openstack.org/constraints/upper/master -r/opt/stack/cyborg/requirements.txt -r/opt/stack/cyborg/test-requirements.txt', 1) ____________________________________________________________________________ _______________________________________________________________ summary ____________________________________________________________________________ _______________________________________________________________ ERROR: pep8: could not install deps [-chttps://releases.openstack.org/constraints/upper/master, -r/opt/stack/cyborg/requirements.txt, -r/opt/stack/cyborg/test-requirements. txt]; v = InvocationError('/opt/stack/cyborg/.tox/shared/bin/python -m pip install -chttps://releases.openstack.org/constraints/upper/master -r/opt/stack/cyborg/requirements.txt -r/opt/stack/cyborg/test-requirements.txt', 1) I hope you can help us. Thank you very much.

3 5

[Glance] [Ceph] [Zed] Glance no longer working after upgrading Ceph cluster to 17.2.6
by Yuri Blas 26 May '23

26 May '23

2 2

[kolla-ansible][yoga] Installation failure while `creating shard root mysql user`
by Rob Jefferson 25 May '23

25 May '23

I'm trying to set up Yoga (as part of a way of upgrading from Xena to Yoga to Zed) using kolla-ansible, and I'm finding that I'm getting the following error at the `kolla-ansible/ansible/roles/mariadb/tasks/register.yml` playbook: TASK [mariadb : Creating shard root mysql user] [...] fatal: [control01]: FAILED! => { "changed": false, "msg": "Can not parse the inner module output: b'[WARNING]: Failure using method (v2_playbook_on_play_start) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): 'Play' object has no attribute 'get_path' [WARNING]: Failure using method (v2_playbook_on_task_start) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): list index out of range [WARNING]: Failure using method (v2_runner_on_ok) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): list index out of range { "custom_stats": {}, "global_custom_stats": {}, "plays": [], "stats\": { "localhost": { "changed\": 0, "failures\": 0, "ignored\": 0, "ok": 1, "rescued\": 0, "skipped\": 0, "unreachable\": 0 } } }' "} I am not sure how to fix this error, or determine what's causing it. I've tried matching up Ansible versions between my installation environment and Yoga, I've tried upgrading Kolla, and so forth. For the installation environment, I'm using: * Debian 11 * Ansible 4.10.0 * ansible-core 2.11.2 * docker-ce 5.20.10 Any help with this would be most appreciated. Thanks, Rob

4 6

Cinder Bug Report 2023-05-25
by Sofia Enriquez 25 May '23

25 May '23

Hello Argonauts, Sorry for the late email. Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Low* - Cached images duplicated per host. <https://bugs.launchpad.net/cinder/+bug/2020733> - *Status:* Unassigned. - [rbac] User with Reader role can extend/reserve/retype/unreserve/update_readonly volume. <https://bugs.launchpad.net/cinder/+bug/2020261> - *Status:* Tempest proposed to master. <https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/883182> - [rbac] User with Reader role can create/delete/update/set-bootable volume. <https://bugs.launchpad.net/cinder/+bug/2020113> - *Status:* Tempest proposed to master. <https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/878672> 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

[ironic] Deploy images crashing Dell server BIOS using UEFI boot
by Mike Currin 25 May '23

25 May '23

Hi All, We have a Xena based Openstack deployment, recently we deployed 60+ nodes in our research cluster with Ironic which worked well. All of these were deployed using a standard process I'll describe below. We recently took delivery of a new Dell R6625 server with NVMe devices onlym which only support UEFI boot, so we are trying to get that working. The server PXEs and downloads the RAM disk and then the Deploy image, once running that it immediately crashes (I assume when running linuxefi). We tested UEFI deploy on an existing Dell R640 server, that server works with BIOS but we swapped it over to UEFI and it does the same, so it wasn't due to the much bigger/different architecture (AMD vs Intel) server. We have a few older servers in a test setup (which are Dell R630's) which are working fine and don't do this behaviour. We haven't tried them on our production setup as if even if they worked it wouldn't help us move forward. I made a video showing this: https://www.dropbox.com/s/5jbn1qpylxaevqb/uefiboot2.mov?dl=0 In the iDRAC we just get that the "System BIOS has halted" and somewhere I said to change hardware that you recently added, which feels unlikely as 2 different servers both working elsewhere with totally different hardware,. I've done a iDRAC Serial console debug but it isn't showing me much that is of any use. This is our entire process to deploy a node (some is once off of course, I've not included the network setup): openstack flavor create --ram 256000 --disk 20 --vcpus 32 --public our-baremetal openstack flavor set our-baremetal --property capabilities:boot_mode="uefi" We downloaded the latest (Xena) images from: https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/ I also tried the latest Centos9 ones just to try them, made no difference. We then extract the image and make a small mod to the service start (we found it didn't bring the NIC immediately up so put a ping delay in the ExecStart), but that's not part of this problem. openstack image create --disk-format aki --container-format aki --public --file ironic-agent.kernel deploy-vmlinuz openstack image create --disk-format ari --container-format ari --public --file ironic-agent.initramfs-ping-patched deploy-initrd Then to do the deploy: export HOSTNAME=<hostname> export MGMTIP=<idracip> openstack baremetal node create --driver ipmi --name $HOSTNAME --driver-info ipmi_port=623 --driver-info ipmi_username=root --driver-info 'ipmi_password=<ourpassword>' --driver-info ipmi_address=$MGMTIP --resource-class baremetal-resource-class --property cpus=32 --property memory_mb=256000 --property local_gb=20 --property cpu_arch=x86_64 --driver-info deploy_ramdisk=$(openstack image show deploy-initrd -f value -c id) --driver-info deploy_kernel=$(openstack image show deploy-vmlinuz -f value -c id) NODE=$(openstack baremetal node show -f value -c uuid $HOSTNAME) openstack baremetal node set $NODE --property capabilities='boot_mode:uefi' openstack baremetal port create <MACADDRESS> --node $NODE --physical-network physnet3 openstack baremetal node manage $NODE --wait && openstack baremetal node list && openstack baremetal node provide $NODE && openstack baremetal node list openstack server create --use-config-drive --image <ourimage> --flavor our-baremetal --security-group worker --network ironic-network --key-name <ourkeyname> servername Does any one have any more info to help or any suggestions as to something more I could try, I'm out of ideas. I know that UEFI itself works on both the servers, we have a setup with Ubuntu MAAS and it can deploy perfectly fine using its process with the UEFI setup so, it's something on the Ironic deploy image that's causing us this problem. Regards, Mike

2 1

upgrade issue with nova/cinder and api version error
by Jim Kilborn 25 May '23

25 May '23

Hello, First time posting here. We have been running a production openstack environment at my office since the kilo release. We are currently on train, and I'm trying to get up to a more recent version. To make it more difficult, we are on centos7, so having to switch to ubuntu as we update versions. The problem that I am having after updaing to victoria, is that when I delete a vm via horizon, the instance disappears but the cinder volume doesn't delete the attachment. It appears this is due to the following error in /var/log/apache2/cinder_error.log ERROR cinder.api.middleware.fault novaclient.exceptions.NotAcceptable: Version 2.89 is not supported by the API. Minimum is 2.1 and maximum is 2.87. (HTTP 406) When I look at the /usr/lib/python3/dist-packages/cinder/compute/nova.py I can see it's using 2.89 in get_server_volume def get_server_volume(context, server_id, volume_id): # Use microversion that includes attachment_id nova = novaclient(context, api_version='2.89') return nova.volumes.get_server_volume(server_id, volume_id) I am not sure why cinder and nova are in disagreement on the api_version. I have verified that they are both upgraded to the victoria release. Anyone have any ideas as to why I would be getting this error or a possible fix? I haven't been able to find any information on this error. Here are the nova package versions: nova-api/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-common/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-conductor/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-novncproxy/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-scheduler/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] python3-nova/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] python3-novaclient/focal-updates,now 2:17.2.1-0ubuntu1~cloud0 all [installed,automatic] Here are the cinder package versions: cinder-api/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] cinder-common/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed,automatic] cinder-scheduler/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] cinder-volume/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] python3-cinder/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed,automatic] python3-cinderclient/focal-updates,now 1:7.2.0-0ubuntu1~cloud0 all [installed] Thanks in advance for any ideas!

3 4