May 2022 - openstack-discuss - lists.openstack.org

error creating image from volume
by Russell Stather 01 Jun '22

01 Jun '22

Hi Trying to create an image from a volume. Getting this very unhelpful error message. igadmin@ig-umh-maas:~$ openstack image create --volume 57bc3efa-6cdc-4e2d-a0e2-262340cc6180 commvaultimage upload_to_image() got an unexpected keyword argument 'visibility' Anyone seen this before? Thanks Russell

3 2

[kolla][Yoga][ubuntu][kolla-toolbox] kolla-toolbox build image Failed with status: error
by Vishwanath 01 Jun '22

01 Jun '22

Hello, I am trying to upgrade Xena to Yoga, as a per-requisite i have upgraded kolla to 14.0.0 and started kolla-build for 14.0.0. *kolla: 14.0.0* *Distributor ID: UbuntuDescription: Ubuntu 20.04.3 LTSRelease: 20.04Codename: focal* *upgrading to : Yoga* *upgrading from: xena* *kolla-build -t source kolla-toolbox -b ubuntu* following is the error message during the image build, issue occurs only on ubuntu whereas centos has no issues, In my environment we use ubuntu. How can this issue be resolved? INFO:kolla.common.utils.kolla-toolbox:ca-certificates is already the newest version (20210119~20.04.2). INFO:kolla.common.utils.kolla-toolbox:Some packages could not be installed. This may mean that you have INFO:kolla.common.utils.kolla-toolbox:requested an impossible situation or if you are using the unstable INFO:kolla.common.utils.kolla-toolbox:distribution that some required packages have not yet been created INFO:kolla.common.utils.kolla-toolbox:or been moved out of Incoming. INFO:kolla.common.utils.kolla-toolbox:The following information may help to resolve the situation: INFO:kolla.common.utils.kolla-toolbox:The following packages have unmet dependencies: INFO:kolla.common.utils.kolla-toolbox: rabbitmq-server : Depends: erlang-base (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: erlang-base-hipe (< 1:25.0) but it is not going to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-crypto (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-eldap (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-inets (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-mnesia (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-os-mon (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-parsetools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-public-key (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-runtime-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-ssl (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-syntax-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-tools (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox: Depends: erlang-xmerl (< 1:25.0) but 1:25.0-1rmq1ppa1~ubuntu20.04.1 is to be installed or INFO:kolla.common.utils.kolla-toolbox: esl-erlang (< 1:25.0) but it is not installable INFO:kolla.common.utils.kolla-toolbox:E: Unable to correct problems, you have held broken packages. INFO:kolla.common.utils.kolla-toolbox: INFO:kolla.common.utils.kolla-toolbox:Removing intermediate container 7ea161d0dbbd ERROR:kolla.common.utils.kolla-toolbox:Error'd with the following message ERROR:kolla.common.utils.kolla-toolbox:The command '/bin/sh -c apt-get update && apt-get -y install --no-install-recommends build-essential ca-certificates crudini gdisk git jq libffi-dev libssl-dev libxslt1-dev openvswitch-switch python3-dev rabbitmq-server && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100 INFO:kolla.common.utils:========================= INFO:kolla.common.utils:Successfully built images INFO:kolla.common.utils:========================= INFO:kolla.common.utils:base INFO:kolla.common.utils:=========================== INFO:kolla.common.utils:Images that failed to build INFO:kolla.common.utils:=========================== ERROR:kolla.common.utils:kolla-toolbox Failed with status: error INFO:kolla.common.utils:========================================= Thanks Vish

2 2

[blazar] IRC meeting of June 2 is cancelled
by Pierre Riteau 01 Jun '22

01 Jun '22

Hello, Due to unavailability of the usual participants, the Blazar IRC meeting of June 2 is cancelled. The next meeting will be on June 16. Thanks, Pierre Riteau (priteau)

1 0

[nova][placement] June 7th Meeting is CANCELLED
by Sylvain Bauza 31 May '22

31 May '22

Some of us will be traveling at the OIF Summit so we won't have a quorum for next week. The nova meeting will be back on June 15th. Thanks, -Sylvain

1 0

[qa][stable][gate] Gate fix for stable/ussuri and Tempest pin for stable/victoria
by Ghanshyam Mann 31 May '22

31 May '22

Hello Everyone, You might know the stable/ussuri gate is broken because we dropped the py36 support in zed cycle and Tempest master is used to test it which uses master constraints. To fix this, I am pinning Tempest 26.1.0 in stable/ussuri and tested it with compatible stable/ussuri constraints and tempest plugins. - https://review.opendev.org/q/topic:ussuri-pin-tempest at the same time, I am also pinning tempest in stable/victoria too as it is also in EM state - https://review.opendev.org/q/topic:victoria-pin-tempest Both stable branches pining is working fine and ready to merge now. I have proposed the fixes for a few tempest plugins and stable branches, and request them to merge because we are going to merge the tempest and devstack changes. Below is the complete set of changes we need: QA patches need to go first: - Tempest - https://review.opendev.org/c/openstack/tempest/+/843045 - https://review.opendev.org/c/openstack/tempest/+/843293/2 - Devstack: - https://review.opendev.org/c/openstack/devstack/+/838051 - https://review.opendev.org/c/openstack/devstack/+/843295 - Devstack-plugin-ceph - https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/843354 - https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/843355 (it is +A and waiting for depends-on devstack patch to merge) - Devstack-gate - https://review.opendev.org/c/openstack/devstack-gate/+/843689 Cinder: - https://review.opendev.org/c/openstack/cinder/+/843305 - https://review.opendev.org/c/openstack/cinder/+/843092 (it is +A and waiting for depends-on devstack patch to merge) - https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/843319 (merged) Cyborg: no action is needed - https://review.opendev.org/c/openstack/cyborg-tempest-plugin/+/843329 (it is +A and waiting for depends-on devstack patch to merge) Neutron: need review - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/838053 Designate: need review - https://review.opendev.org/c/openstack/designate/+/843709 - https://review.opendev.org/c/openstack/designate/+/843710 -gmann

1 1

[cinder] Zed R-18 virtual mid cycle on 1st June
by Rajat Dhasmana 31 May '22

31 May '22

Hello Argonauts, The first Zed mid cycle R-18 will be held on 1st June with the following details: Date: 01st June 2022 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 Etherpad: https://etherpad.opendev.org/p/cinder-zed-midcycles Please add topics to the etherpad and also mark the date and time on your calendar. Thanks and regards Rajat Dhasmana

1 0

SSL verify failed | Overcloud deploy step 4 | Wallaby | tripleo
by Swogat Pradhan 31 May '22

31 May '22

Hi, I am facing the below issue in step4 ' TASK | Clean up legacy Cinder keystone catalog entries': FATAL | Clean up legacy Cinder keystone catalog entries | undercloud | item={'service_name': 'cinderv2', 'service_type': 'volumev2'} | error={"ansible_index_var": "cinder_api_service", "ansible_loop_var": "item", "changed": false, "cinder_api_service": 0, "item": {"service_name": "cinderv2", "service_type": "volumev2"}, "module_stderr": "Failed to discover available identity versions when contacting https://overcloud.bdxworld.com:13000. Attempting to parse version from URL.\nTraceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 677, in urlopen\n chunked=chunked,\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 381, in _make_request\n self._validate_conn(conn)\n File \"/usr/lib/python3.6/site-packages/urllib3/connectionpool.py\", line 978, in _validate_conn\n conn.connect()\n File \"/usr/lib/python3.6/site-packages/urllib3/connection.py\", line 371, in connect\n ssl_context=context,\n File \"/usr/lib/python3.6/site-packages/urllib3/util/ssl_.py\", line 384, in ssl_wrap_socket\n return context.wrap_socket(sock, server_hostname=server_hostname)\n File \"/usr/lib64/python3.6/ssl.py\", line 365, in wrap_socket\n _context=self, _session=session)\n File \"/usr/lib64/python3.6/ssl.py\", line 776, in __init__\n self.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 1036, in do_handshake\n self._sslobj.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 648, in do_handshake\n self._sslobj.do_handshake()\nssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) Can you please suggest a workaround? With regards, Swogat pradhan

2 2

Ansible OpenStack Collection 2.0.0 and OpenStack SDK 1.0.0/0.99.0
by Jakob Meng 31 May '22

31 May '22

Hello contributors and users of the Ansible OpenStack collection [1]! This week a release candidate of the upcoming first major release of OpenStack SDK has been released [2],[3]. It streamlined and improved large parts of its codebase. For example, its Connection interface now consistently uses the Resource interfaces under the hood. This required breaking changes from older SDK releases though. The Ansible OpenStack collection is heavily based on OpenStack SDK. With OpenStack SDK becoming backward incompatible (for the better), so does our Ansible OpenStack collection. We simply lack the devpower to maintain a backward compatible interface in Ansible OpenStack collection across several SDK releases. We already split our codebase into two separate git branches: master and stable/1.0.0. The former will track the upcoming 2.x.x releases of Ansible OpenStack collection which will be compatible with OpenStack SDK 1.x.x (and its rcs 0.99.x) *only*. Our stable/1.0.0 branch will track the current 1.x.x releases of Ansible OpenStack collection which is compatible with OpenStack SDK prior to 0.99.0 *only*. Both branches will be developed in parallel for the time being. Our 2.0.0 release is currently under development and we still have a long way to go. "We" mainly are a couple of Red Hat employees working part-time on the collection. If you use modules of Ansible OpenStack collection and want to help us with porting them to the new SDK, please contact us! If you want to help, please reach out to us (e.g. [7],[8]) and we can give you a quick introduction into everything. We have extensive documentation on why, what and how we are adopting and reviewing the new modules [4], how to set up a working DevStack environment for hacking on the collection [5] and, most importantly, a list of modules where we are coordinating our porting efforts [6]. We are also hanging around on irc.oftc.net/#openstack-ansible-sig and #oooq 😎 [1] https://opendev.org/openstack/ansible-collections-openstack [2] https://github.com/openstack/openstacksdk/releases/tag/0.99.0 [3] https://pypi.org/project/openstacksdk/0.99.0/ [4] https://hackmd.io/szgyWa5qSUOWw3JJBXLmOQ?view [5] https://hackmd.io/PI10x-iCTBuO09duvpeWgQ?view [6] https://hackmd.io/7NtovjRkRn-tKraBXfz9jw?view [7] Rafael Castillo <rcastill(a)redhat.com> (rcastillo) [8] Jakob Meng <mail(a)jakobmeng.de>, <jmeng(a)redhat.com> (jm1) Best, Jakob

2 2

[dev][nova] How to add a column in table of Nova Database
by 韩光宇 31 May '22

31 May '22

Hi, I'm a beginner in OpenStack development. I would like to try modifying by adding a property to the 'Instances' database table. But I didn't find description in the documentation of the data model mechanism and how to extend the database. https://docs.openstack.org/nova/latest/ Now, I know that it involves versined object model and alembic. My question is: What is the process of adding a column to a table in the database? Could someone show me the process of modifying a database table or recommend me the relevant documentation Best wishes, Han

2 2

OpenStack logs on Opensearch - storage problem
by Daniel Pawlik 31 May '22

31 May '22

Hello, In the last few days there is increase amount of CI jobs that are running on Zuul CI gates, where later logs are pushed into the Opensearch cluster [1]. The current cluster storage is almost full, which causes one of the actions to be performed: temporarily changing log retention (currently it is set to 14 days) or removing temporary non-essential logs [2]. I recommend removing not important logs, so if projects leaders could check whether entries related to the project are needed, it would be really helpful. Otherwise, we will temporarily change log retention to 12 days. Dan [1] https://opensearch.logs.openstack.org/_dashboards/app/discover?security_ten… [2] https://opendev.org/openstack/ci-log-processing/src/branch/master/logscrape…

2 2