July 2024 - openstack-discuss - lists.openstack.org

[cinder][glance]Errors with patch bug/2059809
by Nguyễn Hữu Khôi 22 Jul '24

22 Jul '24

Hello, i encounter this error when apply patch about bug/2059809: raise exception.ImageConversionNotAllowed( 2024-07-20 03:35:28.067 736 ERROR oslo_messaging.rpc.server cinder.exception.ImageConversionNotAllowed: Image Conversion disallowed for image 7bacbdfb-2ea3-4ed8-90ad-3ec0e274a1d9: Image conversion is disabled. The volume type you have requested requires that the image it is being created from be in 'raw' format, but the image you are using has the disk_format property 'qcow2'. You must use an image with the disk_format property 'raw' to create a volume of this type. I am using Zed version. Could I have some suggestions? Thank you. Nguyen Huu Khoi

5 14

Kolla-Fluentd: not found: manifest unknown
by Ashok Thipe 22 Jul '24

22 Jul '24

Hi, I'm trying to deploy openstack using Kolla-ansible and encountering following error: TASK [common : Ensure fluentd image is present for label check] ****************** fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.9/site-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/local/lib/python3.9/site-packages/requests/models.py\", line 1021, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.46/images/create?tag=master-centos-stream9&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd\\n\\nThe above exception was the direct cause of the following exception:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_container_payload_7owwfp32/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_7owwfp32/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 522, in ensure_image\\n self.pull_image()\\n File \"/tmp/ansible_kolla_container_payload_7owwfp32/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 209, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) for line in self.dc.pull(\\n File \"/usr/local/lib/python3.9/site-packages/docker/api/image.py\", line 429, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.9/site-packages/docker/api/client.py\", line 270, in _raise_for_status\\n raise create_api_error_from_http_exception(e) from e\\n File \"/usr/local/lib/python3.9/site-packages/docker/errors.py\", line 39, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation) from e\\ndocker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.46/images/create?tag=master-centos-stream9&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd: Not Found (\"manifest for quay.io/openstack.kolla/fluentd:master-centos-stream9 not found: manifest unknown: manifest unknown\")\\n'"} ansible version used: ansible [core 2.15.12] Kolla-ansible version: kolla-ansible@master OS: CentOS 9 stream Please suggest workaround for the above issue. Thanks and regards, Ashok Thipe

2 1

encountering repos metadata issue during overcloud deployment
by Ashok Thipe 21 Jul '24

21 Jul '24

Hi, I'm trying to deploy openstack (zed version) using tripleo method and encountering "error while loading metadata for repos: centos 8" issue during running overcloud deployment. If there are any possible solutions this issue/bug, please care to share. With regards, Ashok Thipe

3 3

Assistance Needed for Trove Instance Creation
by Thamanna Farhath 20 Jul '24

20 Jul '24

Dear OpenStack Community, I am currently working with OpenStack Kolla Ansible 2023.1 1.setting up Trove instances as per the documentation https://docs.openstack.org/trove/2023.1/admin/building_guest_images.html Despite following the steps outlined, I am encountering some issues. Image Not Found: I followed the steps it downloads the required packages and it creates the image directory. However, the trove image is not present in the specified path $HOME/images. 2.I have also referred to https://satishdotpatel.github.io/trove-dbaas-openstack/ and followed each step, but below issue persists. Error with Messaging and Volume Configuration: While creating a Trove instance, I encountered the following errors: ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to declare consumer for topic 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3': Queue.declare: (406) PRECONDITION_FAILED - inequivalent arg 'x-queue-type' for queue 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3' in vhost '/': received the value 'quorum' of type 'longstr' but current is none guest-agent[802]: 2024-07-01 09:24:13.831 802 ERROR trove.guestagent.volume [-] Volume '/dev/vdb' was not formatted.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Steps Taken: Created and configured images as per the OpenStack documentation. Ensured that all Trove-related configurations are properly set up. Verified RabbitMQ configurations to avoid direct configurations and used Trove’s trove-guestagent configuration for managing RabbitMQ settings. /etc/kolla/config/trove.conf [DEFAULT] management_networks = ee2a2a81-178c-4d79-867b-8baf53ec236d nova_keypair = trove-ssh-key management_security_groups = 451e4b4a-58b4-4e9f-84a8-5bdb21e34cd5 /etc/kolla/config/trove-guestagent.conf [DEFAULT] transport_url = rabbit://openstack:<RABBITMQ_PASSWORD>@192.168.8.14:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.15:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.16:5672// control_exchange = trove root_grant = ALL root_grant_option = True debug = False [oslo_messaging_rabbit] heartbeat_in_pthread = false amqp_durable_queues = true rabbit_quorum_queue = true Request for Assistance: Are there any other recommended methods to build the Trove guest image if the documented steps do not work? Is there a known core issue related to the errors I am encountering with oslo.messaging and trove.guestagent.volume? What specific configurations or logs should I check to resolve these errors? Any additional steps or best practices for setting up Trove instances with Kolla Ansible? Thank you in advance for your help. Any insights or suggestions to resolve these issues would be greatly appreciated. Disclaimer : The content of 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. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 2

Kernel reported iSCSI connection [ID_SESSION]:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (1), conn 0 login rejected: initiator error - target not found (02/03)
by elgaplok12＠gmail.com 18 Jul '24

18 Jul '24

hi I have a problem with iscsid. so in the iscsiadm -m session there is still iqn-blablabla:.... when I want to delete or log out, there is an error Logout: iscsiadm --mode node --targetname iqn.2010-10.org.openstack:volume-blablabla --portal ip_address --logout Logging out of session [sid: 45, target: iqn.2010-10.org.openstack:volume-blablabla, portal: ip_address,port] iscsiadm: Could not logout of [sid: 45, target: iqn.2010-10.org.openstack:volume-blablabla, portal: ip_address,port]. iscsiadm: initiator reported error (32 - target likely not connected) iscsiadm: Could not logout of all requested sessions Delete: iscsiadm --mode node --targetname iqn.2010-10.org.openstack:volume-blablabla --portal ip_address --op delete iscsiadm: This command will remove the record [iface: default, target: iqn.2010-10.org.openstack:volume-blablabla, portal: ip_address,port], but a session is using it. Logout session then rerun command to remove record. iscsiadm: Could not execute operation on all records: session exists Sessions: tcp: [160] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) tcp: [161] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) tcp: [162] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) tcp: [163] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) tcp: [164] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla(non-flash) tcp: [44] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) tcp: [45] ip_address:3260,1 iqn.2010-10.org.openstack:volume-blablabla (non-flash) NB: blablabla is uuid volume

1 0

Re: Trove question
by Hirotaka Wakabayashi 18 Jul '24

18 Jul '24

Hello Ксения, Thanks for the contact! Trove team provides the following document for admins to upgrade your Trove service. https://docs.openstack.org/trove/latest/admin/upgrade.html Reading the docs above, you can easily try upgrading Trove for test by using `devstack`. https://docs.openstack.org/trove/latest/install/install-devstack.html If you have any questions, you can contact openstack-discuss@. https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… Best Regards,hirotaka On Wednesday, July 17, 2024 at 09:06:57 PM GMT+9, Ксения Петрова <xeniya.petrova(a)ps.kz> wrote: Hello! We're about to launch our DBaaS on trove in our cloud hosting platform. But we're uncertain about what would be the best way on applying a new version of a trove guest image to our customers databases. So what is the best practices for the process of upgrading guest image? Or nobody of cloud providers cares and upgrading is the completely client's concern? Real-world examples with companies who already sell DBaaS would be the best. Thank you in advance! Best regards, Xeniya Petrova PS Cloud Services

1 0

[Glance] Cancelling Weekly Meeting (July 18)
by Pranali Deore 18 Jul '24

18 Jul '24

Hello, I'm not feeling well, won't be able to chair today's meeting, so cancelling the same. See you next week! Thanks, Pranali Deore

1 0

[Diskimage-builder]Attempting to build opensuse failed.
by Junya Noguchi (Fujitsu) 18 Jul '24

18 Jul '24

To whom it may concern An attempt to build an OpenSUSE image using Diskimage-builder failed. It seems that dracut failed during initial image creation because /dev wasn't mounted. Is there a way to solve this problem? [xxxxxxx@xxxxxxxxxxx ~]$ cat /etc/os-release | grep PRETTY_NAME PRETTY_NAME="Rocky Linux 9.3 (Blue Onyx)" [xxxxxxx@xxxxxxxxxxx ~]$ [xxxxxxx@xxxxxxxxxxx ~]$ disk-image-create opensuse baremetal dhcp-all-interfaces -a amd64 grub2 -o opensuse_test 2024-07-05 02:06:02.796 | diskimage-builder version 3.32.0 2024-07-05 02:06:02.797 | Building elements: base opensuse baremetal dhcp-all-interfaces grub2 2024-07-05 02:06:02.948 | Expanded element dependencies to: package-installs base baremetal zypper cache-url install-bin sysprep dib-init-system install-types pkg-map dhcp-all-interfaces grub2 opensuse 2024-07-05 02:06:03.037 | Building in /tmp/dib_build.pTiDO08e 2024-07-05 02:06:03.041 | Searching elements for block-device[-amd64].yaml ... 2024-07-05 02:06:03.047 | ... done 2024-07-05 02:06:19.736 | Running hooks from /tmp/dib_build.pTiDO08e/hooks/extra-data.d 2024-07-05 02:07:17.361 | dracut: Stored kernel commandline: 2024-07-05 02:07:17.362 | dracut: No dracut internal kernel commandline stored in the initramfs 2024-07-05 02:07:17.363 | dracut: *** Creating image file '/boot/initrd-5.3.18-150300.59.106-default' *** 2024-07-05 02:07:24.019 | dracut: *** Creating initramfs image file '/boot/initrd-5.3.18-150300.59.106-default' done *** 2024-07-05 02:07:24.127 | update-bootloader: 2024-07-05 02:07:24 <3> update-bootloader-4241 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 1, output: 2024-07-05 02:07:24.129 | <<<<<<<<<<<<<<<< 2024-07-05 02:07:24.129 | + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg 2024-07-05 02:07:24.129 | /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). 2024-07-05 02:07:24.129 | >>>>>>>>>>>>>>>> 2024-07-05 02:07:24.129 | Updating bootloader failed 2024-07-05 02:07:24.204 | bootloader_entry: 2024-07-05 02:07:24 <3> bootloader_entry-1651 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 1, output: 2024-07-05 02:07:24.218 | <<<<<<<<<<<<<<<< 2024-07-05 02:07:24.218 | + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg 2024-07-05 02:07:24.218 | /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). 2024-07-05 02:07:24.218 | >>>>>>>>>>>>>>>> 2024-07-05 02:07:24.218 | Failed to get root password hash 2024-07-05 02:07:24.218 | Failed to import /etc/uefi/certs/40905999.crt 2024-07-05 02:07:24.220 | warning: %post(kernel-default-5.3.18-150300.59.106.1.x86_64) scriptlet failed, exit status 255 2024-07-05 02:07:24.221 | done] 2024-07-05 02:07:27.003 | Executing %posttrans script 'ca-certificates-mozilla-2.56-150200.24.1.noarch.rpm' [... 2024-07-05 02:07:27.003 | update-bootloader: 2024-07-05 02:07:27 <3> update-bootloader-1757 run_command.294: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: 2024-07-05 02:07:27.003 | <<<<<<<<<<<<<<<< 2024-07-05 02:07:27.003 | target = x86_64-efi 2024-07-05 02:07:27.003 | + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg --no-nvram --removable 2024-07-05 02:07:27.003 | /usr/sbin/grub2-probe: error: cannot find a device for /boot/efi (is /dev mounted?). 2024-07-05 02:07:27.003 | >>>>>>>>>>>>>>>> 2024-07-05 02:07:27.040 | update-bootloader: 2024-07-05 02:07:27 <3> update-bootloader-1757 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 1, output: 2024-07-05 02:07:27.040 | <<<<<<<<<<<<<<<< 2024-07-05 02:07:27.040 | + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg 2024-07-05 02:07:27.040 | /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). 2024-07-05 02:07:27.040 | >>>>>>>>>>>>>>>> 2024-07-05 02:07:27.089 | . 2024-07-05 02:07:27.089 | Creating initrd: /boot/initrd-5.3.18-150300.59.106-default 2024-07-05 02:07:27.304 | dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-5.3.18-150300.59.106-default 5.3.18-150300.59.106-default 2024-07-05 02:07:27.370 | dracut: Turning off host-only mode: '/run' is not mounted! 2024-07-05 02:07:54.459 | dracut: Stored kernel commandline: 2024-07-05 02:07:54.460 | dracut: No dracut internal kernel commandline stored in the initramfs 2024-07-05 02:07:54.461 | dracut: *** Creating image file '/boot/initrd-5.3.18-150300.59.138-default' *** 2024-07-05 02:08:01.205 | dracut: *** Creating initramfs image file '/boot/initrd-5.3.18-150300.59.138-default' done *** 2024-07-05 02:08:01.308 | update-bootloader: 2024-07-05 02:08:01 <3> update-bootloader-8343 run_command.294: '/usr/lib/bootloader/grub2-efi/config' failed with exit code 1, output: 2024-07-05 02:08:01.309 | <<<<<<<<<<<<<<<< 2024-07-05 02:08:01.309 | + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg 2024-07-05 02:08:01.309 | /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). 2024-07-05 02:08:01.309 | >>>>>>>>>>>>>>>> 2024-07-05 02:08:01.310 | Updating bootloader failed 2024-07-05 02:08:01.311 | warning: %posttrans(device-mapper-2.03.05_1.02.163-150200.8.49.1.x86_64.rpm) scriptlet failed, exit status 1 2024-07-05 02:08:11.000 | .....done] 2024-07-05 02:08:12.494 | There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs. 2024-07-05 02:08:12.494 | 2024-07-05 02:08:12.494 | Since the last system boot core libraries or services have been updated. 2024-07-05 02:08:12.494 | Reboot is suggested to ensure that your system benefits from these updates. 2024-07-05 02:08:12.541 | Unmount /tmp/dib_build.pTiDO08e/mnt/var/cache/zypp 2024-07-05 02:08:12.582 | Unmount /tmp/dib_build.pTiDO08e/mnt/tmp/in_target.d 2024-07-05 02:08:12.603 | Unmount /tmp/dib_build.pTiDO08e/mnt/sys 2024-07-05 02:08:12.623 | Unmount /tmp/dib_build.pTiDO08e/mnt/proc 2024-07-05 02:08:12.667 | Unmount /tmp/dib_build.pTiDO08e/mnt/dev/pts 2024-07-05 02:08:12.688 | Unmount /tmp/dib_build.pTiDO08e/mnt/dev 2024-07-05 02:08:12.882 | INFO diskimage_builder.block_device.blockdevice [-] State already cleaned - no way to do anything here [xxxxxxx@xxxxxxxxxxx ~]$

2 2

Inconsistent server rebuild behavior
by Andrew Bogott 17 Jul '24

17 Jul '24

I'm puzzled by nova instance rebuilds. When I run 'openstack server rebuild --image <whatever>' on a new test VM, it does what I expect: - throws away the old server image - boots up a brand new server using the requested image with the old user/vendor data - attaches new server to the old network port and cinder volumes. That's just what I want! Alas, when I try this with the actual old VMs in need of update, usually it does a totally different thing: - reboots the server - changes the nova db record to reflect the requested VM (so that the server /looks/ like it was rebuilt in 'openstack server show') - That's it! It absolutely does not rebuild the actual server disk image. So, for instance, any files that were present in '/' of the old server are still present post-rebuild. lsb_release still shows the OS of the original base image, disagreeing with the the OS version displayed by 'openstack server show'. I've been reading logfiles for days but I don't see nova ever complain (in either case) that it's doing something unexpected and in both cases the servers wind up in state 'Active'. Am I misunderstanding what this is supposed to do? If not, does anyone have thoughts about what might be going wrong? I assume nova is encountering a roadbump during the rebuild and doing a graceful revert, but if so it sure isn't telling me. Bobcat, kvm, VM images are hosted on ceph/rbd.

2 3

[rally] possibility to skip admin=True validation
by Benedikt Trefzer 17 Jul '24

17 Jul '24

Hi list I'd like to run rally against barbican. Since all barbican scenarios are tagged with @validation.add("required_platform", platform="openstack", admin=True) we cannot use them since our rally configuration does not have an admin user. (actually test itself should succeed, but the validation fails). Question: Is it somehow possible to skip (or unset admin=True requirement) for validation in the task configuration or do I have to rewrite the scenario ? Cheers Benedikt

1 0