February 2023 - openstack-discuss

[Glance][infra][ci]docs and functional jobs are failing for some stable branches
by Pranali Deore 23 Feb '23

23 Feb '23

Hello Everyone, The openstack-tox-docs job is failing consistently for stable/wallaby branch[1] with below error, ----------------------------------------------------------------------------------------------------- autodoc: failed to import module 'manage' from module 'glance.cmd'; the following exception was raised: No module named 'sqlalchemy.databases' ----------------------------------------------------------------------------------------------------- and openstack-tox-functional job is failing for stable/train [2], seems we need to install some packages for python2.7[3]. Do we need similar changes[4] for openstack-tox-functional as well? These jobs are failing since quite long time and we have some import patches to merge in these stable branches, hence raising this on ML. [1]: https://review.opendev.org/c/openstack/glance/+/871621 [2]: https://review.opendev.org/c/openstack/glance/+/871630 [3]: https://bugs.launchpad.net/tripleo/+bug/2006479 [4]:https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873020/ Thanks & Regards, Pranali Deore

2 1

[Octavia] Feature freeze exception
by Gregory Thiemonge 23 Feb '23

23 Feb '23

Hi Folks, We would like to request a feature freeze exception for python-octaviaclient in Antelope. A late commit [0] added a dependency on munch, it was included in the 3.3.0 release (the final release for Antelope). But a more recent proposal [1] removes this dependency and updates the code with an easy patch. We are proposing a 3.4.0 release [2] that includes this commit, and we would like this release to become the official python-octaviaclient release for Antelope instead of 3.3.0 (and the starting point of the 2023.1 branch). Thanks. [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/872357 [1] https://review.opendev.org/c/openstack/python-octaviaclient/+/874553 [2] https://review.opendev.org/c/openstack/releases/+/874864

1 0

[ironic][QA][horizon][release][OpenStackSDK] Cycle With Intermediary without recent deliverables
by Herve Beraud 23 Feb '23

23 Feb '23

Hello, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest $series release available on release week. The following deliverables have done an Antelope release, but it was not refreshed in the last two months: bifrost horizon ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole python-openstackclient tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

3 2

[tempest][neutron] tempest-slow-py3 is failing
by Rajat Dhasmana 23 Feb '23

23 Feb '23

Hello, The tempest-slow-py3 job has been failing consistently since 21 February[1]. Looking at the failure, there is one failing test which looks neutron related[2] (but might be tempest related, not sure). *tempest.scenario.test_network_basic_ops.TestNetworkBasicOps. test_subnet_details* File "/opt/stack/tempest/tempest/lib/common/ssh.py", line 238, in exec_command raise exceptions.SSHExecCommandFailed( tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; cat /var/run/udhcpc.eth0.pid', exit status: 1, stderr: cat: can't open '/var/run/udhcpc.eth0.pid': No such file or directory Cinder is currently in the feature freeze exception phase and we have few patches that need to be merged within this week (before 24 Feb), hence raising the issue on ML. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tempest-slow-py3&proje… [2] https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks Rajat Dhasmana

6 6

OSP 17 v2 clone status
by Sofia Enriquez 22 Feb '23

22 Feb '23

17.1 Doesn't have v2 clone api enabled https://review.opendev.org/c/openstack/tripleo-ansible/+/803683 --> was reverted -- 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

Glance multistore config makes image service inaccessible Edit | openstack wallaby | tripleo
by Swogat Pradhan 22 Feb '23

22 Feb '23

Hi, Openstack wallaby | tripleo I am trying to setup DCN where i want to setup a glance multistore config in both central and edge sites as per the documentation. But when ever i run stack update with the following config for multistore: [stack@hkg2director ~]$ cat workplace/glance.yaml parameter_defaults: GlanceShowMultipleLocations: true GlanceBackend: rbd GlanceEnabledImportMethods: web-download,copy-image GlanceBackendID: ceph GlanceMultistoreConfig: dcn01: GlanceBackend: rbd GlanceStoreDescription: 'dcn01 rbd glance store' CephClusterName: dcn01 The image service becomes inaccessible. Giving the following error: (overcloud) [stack@hkg2director ~]$ openstack image list Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. The image service for :regionOne exists but does not have any supported versions. glance api.log from controller nodes: 2023-02-13 13:02:19.878 7 INFO glance.async_ [-] Threadpool model set to 'EventletThreadPoolModel' 2023-02-13 13:02:19.969 7 INFO keyring.backend [-] Loading KWallet 2023-02-13 13:02:19.977 7 INFO keyring.backend [-] Loading SecretService 2023-02-13 13:02:19.982 7 INFO keyring.backend [-] Loading Windows 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading chainer 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading macOS 2023-02-13 13:02:20.571 7 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2023-02-13 13:02:20.711 7 ERROR stevedore.extension [-] Could not load 'glance.store.s3.Store': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' 2023-02-13 13:02:20.719 7 ERROR stevedore.extension [-] Could not load 's3': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' Is there a patch to fix this issue??

5 17

[cinder] Bug Report | 22-08-2023
by Sofia Enriquez 22 Feb '23

22 Feb '23

Hello Argonauts. Hope you are all doing well! High - When creating a backup fails, the volume status is changed to None <https://bugs.launchpad.net/cinder/+bug/2007631>. - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/873862>. - Online extension not seen in guest instance without stop/start or re-attach of the volume <https://bugs.launchpad.net/cinder/+bug/2007779>. - *Status*: No fix proposed to master. - Failure to mount volumes with LUN ID > 255 <https://bugs.launchpad.net/cinder/+bug/2006960>. - *Status*: Same bugs as last week bug open against Cinder project. Medium - A restore from backup ought to keep the sparse volumes <https://bugs.launchpad.net/cinder/+bug/2007615>. - *Status*: No fix proposed to master. Low - The PowerStore driver doesn't allow more than 32 clones <https://bugs.launchpad.net/cinder/+bug/2008024>. - *Status*: No fix proposed to master. - NetApp NFS driver slow for creating a volume native python threads <https://bugs.launchpad.net/cinder/+bug/2008017>. - *Status*: No fix proposed to master. - image_utils: log message uses incorrect variable <https://bugs.launchpad.net/cinder/+bug/2008041>. - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. - image_utils: misleading log message <https://bugs.launchpad.net/cinder/+bug/2008043> - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. 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

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

22 Feb '23

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (today) will be held in video + IRC mode with details as follows: Date: 22nd February, 2023 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC. Thanks Rajat Dhasmana

1 0

[nova] Clean up "building" instances
by Eugen Block 22 Feb '23

22 Feb '23

Hi, we had a network issue two weeks ago in a HA Victoria cloud resulting in a couple of stale resources (in pending state). Most of them I could cleanup relatively easy, but two instances are left in "building" state, but not yet in the nova database so I can't just remove them via 'openstack server delete <UUID>'. I've been looking through the various nova databases where traces have been left to get an impression where I could intervene (although I don't like manipulating the database). The VMs are two amphora instances: control01:~ # openstack server list --project service | grep -v ACTIVE +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | 0453a7e5-e4f9-419b-ad71-d837a20ef6bb | amphora-0ee32901-0c59-4752-8253-35b66da176ea | BUILD | | amphora-x64-haproxy_1.0.0 | amphora | | dc8cdc3a-f6b2-469b-af6f-ba2aa130ea9b | amphora-4990a47b-fe8a-431a-90ec-5ac2368a5251 | BUILD | | amphora-x64-haproxy_1.0.0 | amphora |+--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ The database tables referring to the UUID 0453a7e5-e4f9-419b-ad71-d837a20ef6bb are these: nova_cell0/instance_id_mappings.ibd nova_cell0/instance_info_caches.ibd nova_cell0/instance_extra.ibd nova_cell0/instances.ibd nova_cell0/instance_system_metadata.ibd octavia/amphora.ibd nova_api/instance_mappings.ibd nova_api/request_specs.ibd My first approach would be to update the nova_cell0.instances table and edit the fields 'vm_state' and 'task_state', or even remove the intire row. But I don't know about the implications this would have on the other tables, so I'd like to know how you would recommend to deal with these orphans. Any comment is appreciated! Thanks, Eugen

3 7

[all][tc] Technical Committee next weekly meeting on 2023 Feb 22 at 1600 UTC
by Ghanshyam Mann 22 Feb '23

22 Feb '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Feb 22, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Feb 21 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1