February 2023 - openstack-discuss

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

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Sam 22 Feb '23

22 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ -- Best Regards， ------------------------------------------------ Sam Green Home Page: http://blog.csdn.net/batmancn Email:batmanzg@163.com

1 1

[PTL][release] 2023.1 Antelope Cycle Highlights
by Elõd Illés 21 Feb '23

21 Feb '23

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3]) Note that the deadline was the Feature Freeze date in previous cycles, but due to requests of PTLs it was decided to postpone one week in the future (to R-4 week). This is better for PTLs as they are usually very busy around Feature Freeze, on the other hand gives less time to marketing team to process the highlights. [1] https://releases.openstack.org/antelope/schedule.html [2] https://releases.openstack.org/antelope/schedule.html#a-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[requirements][oslo] RFE for oslo* deliverables
by Herve Beraud 21 Feb '23

21 Feb '23

1 0

Volume can not be detached/deleted properly & Available volume can not be attached with new instance
by sudeb ghosh 21 Feb '23

21 Feb '23

Hi Team, we are using opensource Openstack (Openstack foundation) in our environment. Facing following issues to fix. Need some guidance or suggestion to resolve the same. Problem Detail: 1. We are struggling to delete the volume which are in 'available' state. After deleting from Dashboard/CLI its showing 'deleting' only. 2. Can not detach the volume from any instance. Showing 'detaching' itself. 3. Once status of volume made available by updating table of Database, the volumes are showing 'available' but could not attach further with any existing instance. 4. Once status of volume made deleted by updating table of Database or by deleting the entries of table the volumes are showing status as 'deleted' in CLI(mysql query) & disappeared from Dashboard but reclaiming of space is not happening in storage or quota point of view. Request your guidance with steps to fix the issue pl. BR// Sudeb Ghosh 7044064878 9332034788

2 1