August 2023 - openstack-discuss - lists.openstack.org

[openstack][kolla-ansible]about group node config overwrite
by Nguyễn Hữu Khôi 30 Oct '25

30 Oct '25

Hello Koller. I want to ask if we can overwrite config for a group of nodes. For example, compute01 >> compute10 will have the same nova configuration compute11 >> compute20 will have the same nova configuration. It will be very nice if we support this way. Thank you. Regards Nguyen Huu Khoi

4 7

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Swogat Pradhan 24 Dec '24

24 Dec '24

Hi, I am currently trying to deploy openstack wallaby using tripleo arch. I created the network jinja templates, ran the following commands also: #openstack overcloud network provision --stack overcloud --output networks-deployed-environment.yaml custom_network_data.yaml # openstack overcloud network vip provision --stack overcloud --output vip-deployed-environment.yaml custom_vip_data.yaml # openstack overcloud node provision --stack overcloud --overcloud-ssh-key /home/stack/sshkey/id_rsa overcloud-baremetal-deploy.yaml and used the environment files in the openstack overcloud deploy command: (undercloud) [stack@hkg2director ~]$ cat deploy.sh #!/bin/bash THT=/usr/share/openstack-tripleo-heat-templates/ CNF=/home/stack/ openstack overcloud deploy --templates $THT \ -r $CNF/templates/roles_data.yaml \ -n $CNF/workplace/custom_network_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e $CNF/templates/node-info.yaml \ -e $CNF/templates/scheduler-hints.yaml \ -e $CNF/workplace/networks-deployed-environment.yaml \ -e $CNF/workplace/vip-deployed-environment.yaml \ -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ -e $CNF/workplace/custom-net-bond-with-vlans.yaml Now when i run the ./deploy.sh script i encounter an error stating: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command.: tripleoclient.exceptions.InvalidConfiguration: Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command. 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1 Can someone tell me where the mistake is? With regards, Swogat Pradhan

4 4

[kolla] [openeuler] CI jobs status
by Michał Nasiadka 26 Nov '24

26 Nov '24

Hello Koalas, OpenEuler jobs in master (to be Antelope) are failing for a long time. If no one is interested in maintaining OpenEuler support in Kolla-Ansible - I will propose dropping it’s support on Wednesday Kolla meeting. Best regards, Michal

4 3

Kolla Ansible on Ubuntu 20.04 - cloud-init & other network issues
by Tobias McNulty 10 Oct '24

10 Oct '24

Hi, I'm attempting to use Kolla Ansible 14.6.0 to deploy OpenStack Yoga on a small 3-node Ubuntu 20.04 cluster. The nodes have 128 GB RAM each, dual Xeon processors, and dual 10G Intel NICs. The NICs are connected to access ports on a 10G switch with separate VLANs for the local and external networks. All the playbooks run cleanly, but cloud-init is failing in the Ubuntu 20.04 and 22.04 VMs I attempt to boot. The VM images are unmodified from https://cloud-images.ubuntu.com/, and cloud-init works fine if I mount a second volume with user-data. The error is a timeout attempting to reach 169.254.169.254. This occurs both when booting a VM in an internal routed network and directly in an external network. I tried various neutron plugin agents (ovn, linuxbridge, and openvswitch both with and without firewall_driver = openvswitch <https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro…>) first with a clean install of the entire OS each time, all with the same result. Running tcpdump looking for 169.254.169.254 shows nothing. As a possible clue, the virtual NICs are unable to pass any traffic (e.g., to reach an external DHCP server) unless I completely disable port security on the interface (even if the associated security group is wide open). But disabling port security does not fix cloud-init (not to mention I don't really want to disable port security). Are there any additional requirements related to deploying OpenStack with Kolla on Ubuntu 20.04? This is a fairly vanilla configuration using the multinode inventory as a starting point. I tried to follow the Quick Start <https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html> as closely as possible; the only material difference I see is that I'm using the same 3 nodes for control + compute. I am using MAAS so it's easy to get a clean OS install on all three nodes ahead of each attempt. I plan to try again with the standard (non-HWE) kernel just in case, but otherwise I am running out of ideas. In case of any additional clues, here are my globals.yml and inventory file, along with the playbook I'm using to configure the network, images, VMs, etc., after bootstrapping the cluster: https://gist.github.com/tobiasmcnulty/7dbbdbc67abc08cbb013bf5983852ed6 Thank you in advance for any advice! Cheers, Tobias

5 9

Live migration fails
by Szabo, Istvan (Agoda) 07 Aug '24

07 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[ptl][tc] OpenStack packages PyPi additional external maintainers audit & cleanup
by Ghanshyam Mann 17 May '24

17 May '24

Hi PTLs, As you might know or have seen for your project package on PyPi, OpenStack deliverables on PyPi have additional maintainers, For example, https://pypi.org/project/murano/, https://pypi.org/project/glance/ We should keep only 'openstackci' as a maintainer in PyPi so that releases of OpenStack deliverables can be managed in a single place. Otherwise, we might face the two sets of maintainers' places and packages might get released in PyPi by additional maintainers without the OpenStack project team knowing about it. One such case is in Horizon repo 'xstatic-font-awesome' where a new maintainer is added by an existing additional maintainer and this package was released without the Horizon team knowing about the changes and release. - https://github.com/openstack/xstatic-font-awesome/pull/2 To avoid the 'xstatic-font-awesome' case for other packages, TC discussed it in their weekly meetings[1] and agreed to audit all the OpenStack packages and then clean up the additional maintainers in PyPi (keep only 'openstackci' as maintainers). To help in this task, TC requests project PTL to perform the audit for their project's repo and add comments in the below etherpad. - https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup Thanks to knikolla to automate the listing of the OpenStack packages with additional maintainers in PyPi which you can find the result in output.txt at the bottom of this link. I have added the project list of who needs to check their repo in etherpad. - https://gist.github.com/knikolla/7303a65a5ddaa2be553fc6e54619a7a1 Please complete the audit for your project before March 15 so that TC can discuss the next step in vPTG. [1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html#… -gmann

18 27

Accessing virsh in openstack wallaby | tripleo
by Swogat Pradhan 24 Mar '24

24 Mar '24

Hi, Can someone please tell me how can i access the virsh utility on the compute node on openstack wallaby? Previously we used nova_libvirt but in wallaby there are multiple containers and i am unable to use virsh utility to edit my domain.xml file. List of containers: [root@dcn01-hci-2 ~]# podman ps | grep nova 10d981158842 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtlogd_wrapper e91667516afc 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtsecretd a4b07fe0e833 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtnodedevd d7e1db393e9c 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtstoraged 5308a171793e 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtqemud f490a6249ba1 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 6 weeks ago nova_virtproxyd ab0441e56957 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 2 months ago (healthy) nova_migration_target f35fbba5b690 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 6 weeks ago (unhealthy) nova_compute 82bc01993106 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo /usr/sbin/virtlog... 2 months ago Up 2 months ago Can someone please suggest how I can i edit an instance xml file in this setup? With regards, Swogat Pradhan

2 5

[Watcher] How use Watcher to scheduler Openstack resource without cpu_usage
by Nguyễn Hữu Khôi 06 Mar '24

06 Mar '24

Hello guys. I want to use watcher to scheduler openstack resources but some openstack versions are missing cpu_usage metric. How do we use Watcher without it? Thank you. Nguyen Huu Khoi

3 5

[neutron][vpnaas][ovn] Pushing VPNaaS support through OVN
by Mohammed Naser 12 Feb '24

12 Feb '24

Hi all! One of the biggest show stoppers for us for OVN is VPNaaS but I think it’s time that we’d like to be involved in getting it over the line, I want to thank Bodo who has shown a lot of patience in getting the code necessary, and it seems that the code works for them in production as well. I’d like to ask if possible for folks to review these two outstanding changes: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/847007 https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 I know Slawek had some concerns, so hoping that raising via the email list if Bodo can address those and over the next bit of time we can get this landed in, since it even has actual proper testing both in CI and with user feedback. Thanks! Mohammed

6 8

[designate] Proposal to deprecate the agent framework and agent based backends
by Michael Johnson 09 Jan '24

09 Jan '24

TLDR: The Designate team would like to deprecate the backend agent framework and the agent based backends due to lack of development and design issues with the current implementation. The following backends would be deprecated: Bind9 (Agent), Denominator, Microsoft DNS (Agent), Djbdns (Agent), Gdnsd (Agent), and Knot2 (Agent). Designate includes many backend DNS server drivers[1], many of which are "native" (also known as xfr type backends) backend implementations. In addition to the "native" backends, Designate has an agent backend[2] that supports other backends via an agent process. To quote the agent backend documentation[2]: This backend uses an extension[3] of the DNS protocol itself to send management requests to the remote agent processes, where the requests will be actioned. The rpc traffic between designate and the agent is both unauthenticated and unencrypted. Do not run this traffic over unsecured networks. Here are the reasons we are proposing to deprecate the agent framework now: 1. The agent protocol used by Designate is using an "unassigned"[4][5] DNS opcode (14) that is causing problems with the dnspython library >= 2.3.0 which is now validating the opcode when building DNS messages. It is a bad practice to use "unassigned" values as they may be officially assigned at any time, likely with an incompatible message format. 2. The agent backends are not tested in the OpenStack jobs[1]. 3. Many of the agent backends have been marked as "Experimental" since 2016 with no additional contributions beyond general repository code maintenance. 4. The protocol between the Designate worker process and the agent process is unauthenticated and unencrypted. 5. We do not know of a development resource to rewrite the agent framework protocol to address issue #1 and #4 above. 6. The introduction of catalog zones[6] may eliminate the need for some of the agent based backend drivers. By marking the agent framework and agent based backends "deprecated" in the Antelope cycle, we would remove the code no earlier than the "C" release of OpenStack (per the OpenStack deprecation policy[7]). In the meantime, issue #1 has been worked around by overriding the dnspython opcode validation[7] as needed in the Designate code (similar to a monkey patch). This is not a sustainable long term solution. The following backend agent based drivers would be marked "deprecated" in addition to the agent framework itself: Bind9 (Agent) Denominator Microsoft DNS (Agent) Djbdns (Agent) Gdnsd (Agent) Knot2 (Agent) We plan to propose patches for the deprecation over the next week, but will not merge them until at least January 24th to allow time for comment from the community. If you have concerns about this deprecation plan or are interested in rewriting the agent framework protocol to address the above issues, please reply to this announcement. Michael [1] https://docs.openstack.org/designate/latest/admin/support-matrix.html [2] https://docs.openstack.org/designate/latest/admin/backends/agent.html [3] https://github.com/openstack/designate/blob/master/designate/backend/privat… [4] https://www.rfc-editor.org/rfc/rfc6895.html#section-2.2 [5] https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-pa… [6] https://www.ietf.org/archive/id/draft-ietf-dnsop-dns-catalog-zones-08.txt [7] https://docs.openstack.org/project-team-guide/deprecation.html [8] https://review.opendev.org/c/openstack/designate/+/870678

3 13

[swift][OpenStackSDK][keystone] Warnings about (my) swift endpoint URL by keystoneauth1 discovery
by Christian Rohmann 13 Nov '23

13 Nov '23

Hey openstack-discuss, we use Ceph RadosGW (Quincy release) to provide Swift as part of an OpenStack cloud. The endpoints are configured as such: > # openstack endpoint list > +----------------------------------+--------+--------------+----------------+---------+-----------+----------------------------------------------------------------------+ > | ID | Region | Service Name | Service > Type | Enabled | Interface | URL | > +----------------------------------+--------+--------------+----------------+---------+-----------+----------------------------------------------------------------------+ > | 1234567890 | region | swift | object-store | True | > public | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > | 2345678901 | region | swift | object-store | True | > internal | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > | 3456789012 | region | swift | object-store | True | > admin | > https://object-store.region.cloud.example.com/swift/v1/AUTH_%(tenant_id)s > | > so according to https://docs.ceph.com/en/latest/radosgw/keystone/#cross-project-tenant-acce…, if I am not mistaken. I can also use the openstack client to access containers: > # openstack container list > +---------------+ > | Name | > +---------------+ > | containera | > | containerb | > +---------------+ and there is no warnings or other apparent issues. But when using "project cleanup" via e.g. "openstack project cleanup --dry-run --project $PROJECT" I see multiple warnings like > Failed to contact the endpoint at > https://object-store.region.cloud.example.com/swift/v1/AUTH_f2bc4bd34567ddc… > for discovery. Fallback to using that endpoint as the base url. > but only mentioning the swift endpoint. Following the warning string this originates from the discovery method of keystoneauth1, see https://github.com/openstack/keystoneauth/blob/28048af9593740315df8d9027c3b…. Could anybody help me understand what is issue might be? Why does this warning not appear for every use of object storage / swift via openstackclient? Is there any way for me to "fix" this? Could this even be a bug? Thanks and with kind regards Christian

4 10

[kolla] [train] [cinder] Cinder issues during controller replacement
by Albert Braden 20 Oct '23

20 Oct '23

We’re replacing controllers, and it takes a few hours to build the new controller. We’re following this procedure to remove the old controller: https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hos… After that the cluster seems to run fine on 2 controllers, but approximately 1/3 of our volumes can’t be attached to a VM. When we look at those volumes, we see this: | os-vol-host-attr:host | qde4-ctrl1.cloud.ourdomain.com@rbd-1#rbd-1 | Ctrl1 is the controller that is being replaced. Is it possible to change the os-vol-host-attr on a volume? How can we work around this issue while we are replacing controllers? Do we need to disable the API for the duration of the replacement process, or is there a better way?

6 9

[OPENSTACK][rabbitmq] using quorum queues
by Nguyễn Hữu Khôi 17 Oct '23

17 Oct '23

Hello guys. IS there any guy who uses the quorum queue for openstack? Could you give some feedback to compare with classic queue? Thank you. Nguyen Huu Khoi

9 19

[all][tc] python 3.11 testing plan
by Ghanshyam Mann 27 Sep '23

27 Sep '23

Hi All, Some of you are part of discussion for python 3.11 testing but If you are not aware of it, below is the plan for python 3.11 testing in OpenStack. Non voting in 2023.2 ------------------------- You might have seen that python 3.11 job is now running as non voting in all projects[1]. Idea is to run it as non voting for this (2023.2) cycle which will give projects to fix the issue and make it green. As it is running on debian (frickler mentioned the reason of running it in debian in gerrit[2]), it need some changes in bindep.txt file to pass. Here is the example of fix[3] which you can do in your project also. Voting in 2024.1 -------------------- In next cycle (2024.1), I am proposing to make py3.11 testing mandatory [4] and voting (automatically via common python job template). You need to fix the failure in this cycle otherwise it will block the gate once the next cycle development start (basically once 891238 is merged). [1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/891227/5 [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/891146/1 [3] https://review.opendev.org/c/openstack/nova/+/891256 [4] https://review.opendev.org/c/openstack/governance/+/891225 [5] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/891238 -gmann

12 27

[ironic] Mass retirement of old branches due to config errs
by Jay Faulkner 18 Sep '23

18 Sep '23

Hi all, Ironic is one of the major offenders remaining in the work to cleanup Zuul config errors. To resolve these issues, it's my plan to retire any impacted branches unless a contributor volunteers to clean them up. I will give folks until at least September 1, 2023, to object before I begin to take action. These branches have been broken for at least one year, and have gotten no patches or releases in that time. It's clear they have little need to continue existing. Please look at https://zuul.opendev.org/t/openstack/config-errors for the full list of potentially impacted branches; I will list here as best I can: openstack/ironic-prometheus-exporter - bugfix/2.1 - stable/train openstack/networking-generic-switch - stable/pike - stable/train - stable/ussuri - stable/victoria - stable/wallaby - stable/xena openstack/python-ironicclient - stable/train - stable/ussuri - stable/victoria - stable/wallaby - stable/xena - Note: stable/yoga is also in the config errors list, but is considered maintained and cannot be retired at this time. I will work to remove failing jobs and get this zuul config fixed manuallt. As an additional note, the following branches were retired months ago, but due to a bug were recreated. They have been fully deleted (again): openstack/ironic-python-agent - bugfix/8.0 openstack/ironic - bugfix/18.0

3 4

[cinder][kolla-ansible] cinder-volume active/active usage
by 韩光宇 15 Sep '23

15 Sep '23

Hello, I saw that kolla-ansible had allow cinder coordination backend to be configured. And it can be set to "redis" or "etcd" in /etc/kolla/gloabls.yml [1]. Based on my current understanding, this option enables cinder-volume active/active. 1. I would like to ask, between Redis and Etcd, which one is more recommended or what are their pros and cons? 2. And I have saw the spec of cinder-volume a/a[2]. Is it sufficient to configure [coordination]backend_url and [DEFAULT]cluster to use Cinder volume active/active, or are there any other considerations? Could any reference for Cinder volume active/active configuration and usage documentation be recommended ? I would appreciate for any help. Best wishes. Han Guangyu [1] https://github.com/openstack/kolla-ansible/blob/master/etc/kolla/globals.ym… [2] https://specs.openstack.org/openstack/cinder-specs/specs/ocata/ha-aa-job-di…

3 2

[ptl][tc][winstackers] Final call for Winstackers PTL and maintainers
by James Page 11 Sep '23

11 Sep '23

Hi All As announced by Lucian last November (see [0]) Cloudbase Solutions are no longer in a position to maintain support for running OpenStack on Windows and have also ceased operation of their 3rd party CI for the windows support across a number of OpenStack projects. This situation has resulted in the Winstackers project becoming PTL-less for the 2023.2 cycle with no volunteers responding to the TC's call to fill this role and take this feature in OpenStack forward (see [1]). This is the final call for any maintainers to step forward if this feature is important to them in OpenStack. The last user survey in 2022 indicated that 2% of respondents were running on Hyper-V so this might be important enough to warrant a commitment from someone operating OpenStack on Windows to maintain these features going forward. Here is a reminder from Lucian's original email on the full list of projects which are impacted in some way: * nova hyper-v driver - in-tree plus out-of-tree compute-hyperv driver * os-win - common Windows library for Openstack * neutron hyperv ml2 plugin and agent * ovs on Windows and neutron ovs agent support * cinder drivers - SMB and Windows iSCSI * os-brick Windows connectors - iSCSI, FC, SMB, RBD * ceilometer Windows poller * manila Windows driver * glance Windows support * freerdp gateway The lack of 3rd party CI for testing all of this really needs to be addressed as well. If no maintainers are forthcoming between now and the next PTG in June the TC will need to officially retire the project and start the process of removing support for Windows across the various projects that support this operating system in some way - either directly or through the use of os-win. For clarity this call refers to the use of the Hyper-V virtualisation driver and associated Windows server components to provide WIndows based OpenStack Hypervisors and does not relate to the ability to run Windows images as guests on OpenStack. Regards James [0] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03104… [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032888.h…

5 9

[Skyline] error username or password incorrect
by Satish Patel 11 Sep '23

11 Sep '23

Folks, Try to install skyline UI to replace horizon using doc: https://docs.openstack.org/skyline-apiserver/latest/install/docker-install-… Everything went well and I got a login page on http://x.x.x.x:9999 also it pulled Region/Domains. When I am trying to login with my account, I get an error: Username or Password is incorrect. I am using sqlite DB for skyline as per documents. No errors in logs command $ docker logs skyline When I use Chrome Developer Tools then it was indicating an error in these URLs. http://openstack.example.com:9999/api/openstack/skyline/api/v1/profile http://openstack.example.com:9999/api/openstack/skyline/api/v1/policies 401 Unauthorized ( {"detail":"no such table: revoked_token"} )

2 16

[openstack-ansible] Recommended branch for a production environment?
by Roger Rivera 05 Sep '23

05 Sep '23

Hello, We have deployed Openstack-Ansible in a test environment and we were wondering what the recommended repository branch is to deploy in a production environment that will be integrated with a separate Ceph cluster. 1. We are thinking about pinning to the stable/zed. Is that recommended over the master branch? 2. Are bugs ironed out on both master and stable/zed with the same cadence? 3. Additionally, is Debian 11 a better alternative than Ubuntu 22 for target hosts? We noticed Ubuntu 22.04 support was added recently, whereas Debian 11 has been supported for quite some time now which leads us to believe its stability/integration could be more mature at this point? Any suggestions will be appreciated. Thank you, -- *Roger *

3 7

[SDK][CLI][API][OpenAPI] Machine readable OpenStack API spec - time to do a next step?
by Artem Goncharov 01 Sep '23

01 Sep '23

Hey, Some of you may know that for certain time I was doing experiments on the sdk/cli/ansible_mod side with regards to the code generation. Reason for that is simple: huge codebases and too few resources. While not being the primary goal of this initiative, but still a pointer into the same direction is that most of the tools we need to maintain do the same stuff with some adaptations necessary for the framework in question. I did a lot of diverse attempts trying to take current OpenStackSDK codebase as a “source of truth” regarding what exists in which service and use it to generate code (OSC, AnsibleModule, etc). Pretty quickly it became clear that we do not have enough information to cover all the different needs: - when query parameter has been added into or dropped from the API - what is the type of the query parameter and whether in the case it is list it should be rendered as "?tags=a,b" or "?tags=a&tags=b” - which fields are necessary to be send in the request, which are optional and how to deal when you send name but get back UUID in the same field - what are the parameter/resource fields types in detail with respect to strongly typed programming languages (“int” is not good to differentiate between u8 and f64) - how to determine list of supported “actions” on the resource which are above the plain CRUD Firstly I tried to extend our current model of things in SDK, but even that was not so helpful. And then I decided to give another look at OpenAPI and our desires since multiple years to move into that direction. First of all it provides all the required information to do what is necessary. And so I tried to gather all the things we said about OpenAPI at OpenStack and which challenges we have and compare it against the OpenAPI 3.1. Problems: 1) OpenAPI does not support model of microversions. To be more precise on that you can’t describe different request/response body based on the header differentiator 2) URL + Method are representing unique combination making it impossible to represent different actions based on the content 3) All relevant Headers are supposed to be described in the spec. For example Swift is using X-Object-Meta-* prefix to allow user customisations what is not currently supported by the spec Actually that’s it, everything else was doable. Have I missed something? So what can we do about it: 1) OpenAPI 3.1 is now based upon jsonschema, what allows huge flexibility in describing object schema including inheritance and polymorphism (with composition, discriminator, etc). So we can describe the necessary Microversion Header and schema using “oneOf” whenever necessary. Moreover it is possible to extend type schema with “x-“ prefixed custom properties. So I went and started adding “x-openstack-“ prefixed properties where necessary 2) I personally agree with OpenAPI that URL+method should be enough to uniquely identify what is expected (while not a big deal for the API consumer, it would have been easier on the server side to have URL uniquely tied with the data and operation instead of dynamically looking at the request to figure out what to do. This is actually a most complex thing to deal with and the only solution that comes to my mind would be not to try to put everything into single spec, but rather have a dedicated specs for different operations. It makes it anyway easier to maintain such spec. Maybe at some next OpenAPI iteration this gets resolved and we can adopt changes. 3) A tricky thing, but there is nothing preventing us specifying headers as “x-object-meta-*” and defining custom processors for things like that to for example compose/decompose this into dictionary on the client side OpenAPI now even allows defining spec extensions if necessary, but I think at the moment we can cover all issues without that. Demo time: - server live migration (in my eyes one of the trickiest things I have seen so far from the OpenStack APIs). Here you have an action requiring a dedicated spec, multiple revisions with micro versions and even parameter type bool which can be a string as well: [2] https://paste.opendev.org/show/bcxFi2CrNX1YNEuTzoEh/ More real-life examples in [4] - image create and upload: [3] https://paste.opendev.org/show/bNN1t0qVmHEdVHu0Mtrn/ Here it is possible to put few methods into the single spec. You can also see here samples of different media-types, capture headers, readOnly/writeOnly properties (You can actually take those specs and paste them into https://editor-next.swagger.io/ and see how it looks like) Closing notes: I have implemented a WIP change [1] in SDK that consumes list of specs and performs requested operation. Series of SDK commands are converted to the new way dealing with APIs. This is backwards compatible, but opens a road to heavily reduce amount of code in SDK (precisely by dropping all those customisations that are necessary now). Honestly speaking my drafts even show performance improvement on SDK side in the area of 100-300ms for diverse API operations, but I am still not really able to explain why. Maybe because of avoiding most black magic of SDK. I assume after completion we could get another performance boost by dropping other unnecessary logic and abstractions. The work is not completed as the change title states. Once we have specs for the commands code generators can be updated to consume this data and produce much better code. BTW, I have now also a prototype of the new CLI written with Rust and this is a hypersonic bullet compared to the current OSC. But please do not push me more on that, it is still in a very early stages and depends heavily on the available specs. I can only say that it is now designed in the way that every API call can have a thin CLI coverage just by providing a spec, when additional logic is desired - surely will require human implementation. Code generators in the pipe: OSC, AnsibleModules, RustSDK (sync/async), RustCLI. Next thing that are on the radar: gopher cloud, terraform modules, async python sdk, JS SDK(?) If all of that gets executed properly and with some community traction we can all have following things covered: - improve standardisation of OpenStack internals and externals: glance and nova (at least those 2) are already using jsonschema internally in different areas to describe requests/responses. Why not to make this standard reaching the service consumers? - getting rid of api-ref work by updating our sphinx machinery to consume our customised specs and produce nice docs matching the reality - sharing specs between teams to improve interface (not like currently we need to read the api-ref with tons of bugs plus source code to understand how to cover new feature in service X). Maybe even a central repo with the specs per release. - there are plenty of code generators and server bindings for OpenAPI specs so that we can potentially align frameworks used by different teams to maintain less - less work for all of us who needs services talking to each other (not immediately right now, but once the code is switched on consuming specs) - request verification already on the client side not waiting for the response - finally show something to customers often annoying asking “where are your openapi specs” (no offence here ;-))? I know it is a long message. But I am pretty excited with the progress and would like to hear community opinions. For the more detailed discussion consider this as a pre-announcement of the topic for PTG in sdk/cli slots. Huge invest but huge outcome P.S. it can result in a good chunk of relatively easy work for students Regards, Artem [1] https://review.opendev.org/c/openstack/openstacksdk/+/892161 [2] https://paste.opendev.org/show/bcxFi2CrNX1YNEuTzoEh/ [3] https://paste.opendev.org/show/bNN1t0qVmHEdVHu0Mtrn/ [4] https://review.opendev.org/c/openstack/openstacksdk/+/893365

4 5

[all] osprofiler requirements on opentelemetry: is this reasonable?
by Thomas Goirand 01 Sep '23

01 Sep '23

Hi, I just saw that the last version of osprofiler requires opentelemetry-exporter-otlp and opentelemetry-sdk. Since osprofiler is used in almost all projects, and that opentelemetry is really HUGE, I wonder if this is all reasonable. This forces downstream distros to do a lot of packaging only for that. Is this avoidable? I started doing the packaging, and then stopped to write this message, seeing how much work that would represent. Your thoughts? Cheers, Thomas Goirand (zigo)

3 3

[Rally]
by Aayushi Gautam 31 Aug '23

31 Aug '23

Hello, I am Aayushi , an intern with Redhat working on ESI ( Elastic secure Infracstructure) group. We were trying to use Rally to test the performance of our codebase. I have created a Plugin and task . And getting an error. The same bug is also asked on the bug page of Rally, but it was not answered. I have attached the code of the plugin and task and the error message. Looking forward to hearing from you.

2 5

Issue with Live Migration
by Chris DiLorenzo 31 Aug '23

31 Aug '23

We are running zed deployed with kolla-ansible. We are running into an issue with Live Migration. These are the steps to reproduce the issue: - Create a VM - Attach a Cinder Volume. This will create a new Storage Controller. - Start writing data to the new disk. We used FIO. Let FIO run until it starts reporting IOPS data. - Live migrate the VM - The VM will migrate and FIO will continue to run. FIO will show 0 or no IOPS - lspci output will show that the new storage device is in error. - The VM will remain in this state until the user issues a hard reset command - Once the VM is rebooted, the issue can not be reproduced until another device is attached This also happens if we attach a new VNIC. Prior to migration, this is what we see: root@test-vm-cd:~# cat before_migration_lspci.txt | grep block 05:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev 01) Subsystem: Red Hat, Inc. Virtio block device 08:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev 01) Subsystem: Red Hat, Inc. Virtio block device Post migration we see this: 08:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: virtio-pci The original SCSI controller is fine. Outside of the above error, we don't see any other errors. From Openstack's perspective, the migration went fine. Any suggestions on where to look? Has anyone else seen this? Thanks, Chris

1 0

[elections][sahara] PTL Candidacy for 2024.1
by Jerry Zhou (周鑫勇) 31 Aug '23

31 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Sahara PTL during the 2024.1 cycle. I have been in this role for the last cycle, and I would like to continue serving as PTL. During the past cycles, there was a lot of effort put into promoting contributor collaboration through various activities. We also revised unstable unit/functional tests to improve the quality of development, and created documents for users to demonstrate use cases with practical examples. In the next cycle, I'd like to continue improving unit testing and documentation quality.

1 0

TripleO centos9 wallaby IPA job is failing
by Bhagyashri Shewale 31 Aug '23

31 Aug '23

Hi folks, All the centos9 wallaby IPA jobs are failing due to [1] and blocking gate. We are currently working on it. [1]: https://bugs.launchpad.net/tripleo/+bug/2033357 Thanks and regards Bhagyashri Shewale

2 1

Openstack Horizon Login Issues
by Asma Naz Shariq 31 Aug '23

31 Aug '23

Hi Team, Can anyone help me to resolve this issue of openstack dashboard-Yoga release? You do not have permission to access the resource: /horizon/ Login as different user or go back to home page. How to resolve this issue in openstack while accessing web interface. Can anyone guide me how to resolve this issue? when i entered the credentials to access to openstack dashboard, it display mesasge: Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator. Regards, Asma

2 1

migration error
by Karera Tony 31 Aug '23

31 Aug '23

Hello Team, I am migrating an instance from one Cpmpute to another but I am getting this error *Error: *Failed to live migrate instance to host "compute1". Details <http://10.10.13.31/admin/instances/#message_details> Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. 0 Refer to http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult (HTTP 400) (Request-ID: req-6bc103a8-f1f1-489c-a620-ec535b651280) Please advise Regards Tony Karera

1 0

Re: openstack-discuss Digest, Vol 58, Issue 108
by Karera Tony 31 Aug '23

31 Aug '23

My issue was resolved after upgrading kolla-ansible. Regards Tony Karera On Wed, Aug 30, 2023 at 3:53 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. [keystone][election] Self-nomination for Keystone PTL for > 2024.1 cycle (Dave Wilde) > 2. Re: openstack-discuss Digest, Vol 58, Issue 107 (Karera Tony) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Aug 2023 08:35:00 -0500 > From: Dave Wilde <dwilde(a)redhat.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: [keystone][election] Self-nomination for Keystone PTL for > 2024.1 cycle > Message-ID: <54d82977-aee0-4df2-a7c3-2be3b8c2788c@Spark> > Content-Type: text/plain; charset="utf-8" > > Hey folks, > > It's Dave here, your current OpenStack Keystone PTL. I'd like to submit my > candidacy to again act as the PTL for the 2024.1 cycle.??We're making great > progress with Keystone, and I would like to continue with that excellent > work. > > As PTL in this cycle here are some of the things I'd like to focus on: > > ??- Finish the manager role and ensure that the SRBAC implied roles are > correct > ?? ?for manager and member > ??- Continue the OAuth 2.0 Implementation > ??- Start a known issues section in the Keystone documentation > ??- Start a documentation audit to ensure that our documentation is of the > ?? ?highest quality > > Of course we will continue the weekly meetings and the reviewathons.??I > think > the reviewathons have been very successful and I'm keen on keeping them > going. > > I'm looking forward to another successful cycle and working with everyone > again! > > Thank you! > > /Dave >

1 0

[elections][venus] PTL Candidacy for 2024.1
by Eric Zhang (张连法)-浪潮信息 31 Aug '23

31 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Venus PTL during the Caracal/2024.1 cycle. I have been in this role for the last 2 cycles and I would like to continue serving as PTL. In the upcoming cycle, I would like to focus on the following: * Continuous improvement in documents, unit tests, clients and dashboard. * Enhance log anomaly detection, such as more matching rules, improving performance. Thank you for your consideration! Lianfa Zhang

1 0

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 31 Aug '23

31 Aug '23

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2024.1/…

1 0

[elections][cyborg] PTL Candidacy for 2024.1
by Alex Song (宋文平) 31 Aug '23

31 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Cyborg PTL during the Caracal/2024.1 cycle. I have been in this role for the last 3 cycles and I would like to continue serving as PTL. During the past cycles, there was a lot of effort on promoting contributor collaboration through different activities and it helped us to make progress on closing gaps between the Cyborg APIs and other clients consuming them, as well as tackling tech debt and getting new features and drivers merged. I feel energized to continue pushing on these areas, but also put some focus on: * Complete the new features such as vgpu and mig management, disable and enable devices, update the device attribute and so on. * Working on the stability of our upstream CI first party jobs and also checking with third party CI maintainers to ensure their CI is healthy and reporting valid results. * Enhancing the review bandwidth and doing more actions to encourage more reviews from people submitting code to the Cyborg code base. * Work on documentation to help new contributors understand what are the requirements when proposing new features, and also continue the effort to cover the lack of documentation we have on third party CI setups for Cyborg, helping potential new vendors to quickly set up their CI systems. Thank you for your consideration! Wenping Song IRC: wenping1

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations End
by Ian Y. Choi 31 Aug '23

31 Aug '23

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 12 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Cyborg, Ec2_Api, Mistral, Monasca, Openstack_Chef, Rally, Sahara, Senlin, Skyline, Sunbeam, Trove, Venus There are 1 projects that will have elections: OpenStack_Helm. The details for those will be posted around polling start date after we setup the CIVS system. -- TC Election Details -- Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Sep 06, 2023 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#ptl-candidates [1] https://governance.openstack.org/election/#tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

Cinder Bug Report 2023-08-30
by Jon Bernard 30 Aug '23

30 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - [StorPool Storage] Live VM Migration Fails <https://bugs.launchpad.net/cinder/+bug/2033292> - Status: In Progress - Dell PowerMax - Online migration can fail <https://bugs.launchpad.net/cinder/+bug/2033398> - Status: New - Hitachi: send unnecessary request to unlock storage resource group <https://bugs.launchpad.net/cinder/+bug/2033448> - Status: In Progress Thanks -- Jon

1 0

Re: openstack-discuss Digest, Vol 58, Issue 107
by Karera Tony 30 Aug '23

30 Aug '23

Hi Michael, I have realized that the docker version I have on the new compute nodes after running the bootstrap command is 24 while the previous compute and controller nodes have 20. Could that be a problem? Regards Regards Tony Karera On Wed, Aug 30, 2023 at 3:22 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss > > or, via email, send a message with subject or body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > > Today's Topics: > > 1. Re: [elections][Cinder] PTL Candidacy for 2024.1 (Caracal) > (Brian Rosmaita) > 2. Re: [kolla] [train] [cinder] Cinder issues during controller > replacement (Danny Webb) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Aug 2023 08:31:32 -0400 > From: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [elections][Cinder] PTL Candidacy for 2024.1 (Caracal) > Message-ID: <fa39fe25-6651-688a-4bfa-39abbdbb7e04(a)gmail.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 8/29/23 10:17 AM, Rajat Dhasmana wrote: > > Hi All, > > > > I would like to nominate myself to be Cinder?PTL during the 2024.1 > (Caracal) > > cycle. > [snip] > > Here are some work items we are planning for the next cycle (2024.1): > > > > * We still lack review bandwidth since one of our active cores, Sofia, > > couldn't contribute to Cinder anymore > > hence we will be looking out for potential core reviewers. > > * Continue working on migrating from cinderclient to OSC (and SDK) > support. > > * Continue with the current cinder events like festival of XS reviews, > > midcycle, video meeting once a month etc > > that provides regular team interaction and helps tracking and discussion > > of ongoing work throughout the cycle. > > All this sounds great to me! Thanks for stepping up once again to take > on the task of herding the Argonauts and keeping the Cinder project on > track. > > > > > [1] https://review.opendev.org/q/topic:cinderclient-sdk-migration > > <https://review.opendev.org/q/topic:cinderclient-sdk-migration> > > [2] https://review.opendev.org/q/topic:cinder-sdk-gap > > <https://review.opendev.org/q/topic:cinder-sdk-gap> > > [3] > > > https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… > < > https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… > > > > [4] > > > https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… > < > https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… > > > > > > Thanks > > Rajat Dhasmana > > > > > ------------------------------ > > Message: 2 > Date: Wed, 30 Aug 2023 13:19:49 +0000 > From: Danny Webb <Danny.Webb(a)thehutgroup.com> > To: Eugen Block <eblock(a)nde.ag>, > "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [kolla] [train] [cinder] Cinder issues during controller > replacement > Message-ID: > < > LO2P265MB5773FCAFE86B26D1E45E31459AE6A(a)LO2P265MB5773.GBRP265.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="windows-1252" > > Just to add to the cornucopia of configuration methods for cinder > backends. We use a variation of this for active/active controller setup > which seems to work (on pure, ceph rbd and nimble). We use both > backend_host and volume_backend_name so any of our controllers can action a > request for a given volume. We've not had any issues with this setup since > ussuri (we're on Zed / Yoga now). > > eg: > > [rbd] > backend_host = ceph-nvme > volume_backend_name = high-performance > ... > > [pure] > backend_host = pure > volume_backend_name = high-performance > ... > > which leaves us with a set of the following: > > $ openstack volume service list > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > | Binary | Host | Zone | Status | State > | Updated At | > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > | cinder-volume | nimble@nimble-az1 | gb-lon-1 | enabled | up > | 2023-08-30T12:34:18.000000 | > | cinder-volume | nimble@nimble-az2 | gb-lon-2 | enabled | up > | 2023-08-30T12:34:14.000000 | > | cinder-volume | nimble@nimble-az3 | gb-lon-3 | enabled | up > | 2023-08-30T12:34:17.000000 | > | cinder-volume | ceph-nvme@ceph-nvme-az3 | gb-lon-3 | enabled | up > | 2023-08-30T12:34:14.000000 | > | cinder-volume | pure@pure-az1 | gb-lon-1 | enabled | up > | 2023-08-30T12:34:11.000000 | > | cinder-volume | pure@pure-az2 | gb-lon-2 | enabled | up > | 2023-08-30T12:34:11.000000 | > > +------------------+-------------------------+----------+---------+-------+----------------------------+ > > > ________________________________ > From: Eugen Block <eblock(a)nde.ag> > Sent: 30 August 2023 11:36 > To: openstack-discuss(a)lists.openstack.org < > openstack-discuss(a)lists.openstack.org> > Subject: Re: [kolla] [train] [cinder] Cinder issues during controller > replacement > > CAUTION: This email originates from outside THG > > Just to share our config, we don't use "backend_host" but only "host" > on all control nodes. Its value is the hostname (shortname) pointing > to the virtual IP which migrates in case of a failure. We only use > Ceph as storage backend with different volume types. The volume > service list looks like this: > > controller02:~ # openstack volume service list > > +------------------+--------------------+------+---------+-------+----------------------------+ > | Binary | Host | Zone | Status | State | > Updated At | > > +------------------+--------------------+------+---------+-------+----------------------------+ > | cinder-scheduler | controller | nova | enabled | up | > 2023-08-30T10:32:36.000000 | > | cinder-backup | controller | nova | enabled | up | > 2023-08-30T10:32:34.000000 | > | cinder-volume | controller@rbd | nova | enabled | up | > 2023-08-30T10:32:28.000000 | > | cinder-volume | controller@rbd2 | nova | enabled | up | > 2023-08-30T10:32:36.000000 | > | cinder-volume | controller@ceph-ec | nova | enabled | up | > 2023-08-30T10:32:28.000000 | > > +------------------+--------------------+------+---------+-------+----------------------------+ > > We haven't seen any issue with this setup in years during failover. > > Zitat von Gorka Eguileor <geguileo(a)redhat.com>: > > > On 29/08, Albert Braden wrote: > >> What does backend_host look like? Should it match my internal API > >> URL, i.e. api-int.qde4.ourdomain.com? > >> On Tuesday, August 29, 2023 at 10:44:48 AM EDT, Gorka Eguileor > >> <geguileo(a)redhat.com> wrote: > >> > > > > Hi, > > > > If I remember correctly you can set it to anything you want, but for > > convenience I would recommend setting it to the hostname that currently > > has more volumes in your system. > > > > Let's say you have 3 hosts: > > qde4-ctrl1.cloud.ourdomain.com > > qde4-ctrl2.cloud.ourdomain.com > > qde4-ctrl3.cloud.ourdomain.com > > > > And you have 100 volumes on ctrl1, 20 on ctrl2, and 10 on ctrl3. > > > > Then it would be best to set it to ctrl1: > > [rbd-1] > > backend_host = qde4-ctrl1.cloud.ourdomain.com > > > > And then use the cinder-manage command to modify the other 2. > > > > For your information the value you see as "os-vol-host-attr:host" when > > seeing the detailed information of a volume is in the form of: > > <HostName>@<BackendName>#<PoolName> > > > > In your case: > > <HostName> = qde4-ctrl1.cloud.ourdomain.com > > <BackendName> = rbd-1 > > <PoolName> = rbd-1 > > > > In the RBD case the poolname will always be the same as the backendname. > > > > Cheers, > > Gorka. > > > >> On 29/08, Albert Braden wrote: > >> > We?re replacing controllers, and it takes a few hours to build > >> the new controller. We?re following this procedure to remove the > >> old controller: > >> > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hos… > < > https://docs.openstack.org/kolla-ansible/train/user/adding-and-removing-hos… > > > >> > > >> > After that the cluster seems to run fine on 2 controllers, but > >> approximately 1/3 of our volumes can?t be attached to a VM. When we > >> look at those volumes, we see this: > >> > > >> > | os-vol-host-attr:host | > >> qde4-ctrl1.cloud.ourdomain.com@rbd-1#rbd-1 > >> | > >> > > >> > Ctrl1 is the controller that is being replaced. Is it possible to > >> change the os-vol-host-attr on a volume? How can we work around > >> this issue while we are replacing controllers? Do we need to > >> disable the API for the duration of the replacement process, or is > >> there a better way? > >> > > >> > >> Hi, > >> > >> Assuming you are running cinder volume in Active-Passive mode (which I > >> believe was the only way back in Train) then you should be hardcoding > >> the host name in the cinder.conf file to avoid losing access to your > >> volumes when the volume service starts in another host. > >> > >> This is done with the "backend_host" configuration option within the > >> specific driver section in cinder.conf. > >> > >> As for how to change the value of all the volumes to the same host > >> value, you can use the "cinder-manage" command: > >> > >> cinder-manage volume update_host \ > >> --currenthost <current host> \ > >> --newhost <new host> > >> > >> Cheers, > >> Gorka. > >> > >> > >> > > > >

1 0

[keystone][election] Self-nomination for Keystone PTL for 2024.1 cycle
by Dave Wilde 30 Aug '23

30 Aug '23

Hey folks, It's Dave here, your current OpenStack Keystone PTL. I'd like to submit my candidacy to again act as the PTL for the 2024.1 cycle. We're making great progress with Keystone, and I would like to continue with that excellent work. As PTL in this cycle here are some of the things I'd like to focus on: - Finish the manager role and ensure that the SRBAC implied roles are correct for manager and member - Continue the OAuth 2.0 Implementation - Start a known issues section in the Keystone documentation - Start a documentation audit to ensure that our documentation is of the highest quality Of course we will continue the weekly meetings and the reviewathons. I think the reviewathons have been very successful and I'm keen on keeping them going. I'm looking forward to another successful cycle and working with everyone again! Thank you! /Dave

1 0

[elections][Cinder] PTL Candidacy for 2024.1 (Caracal)
by Rajat Dhasmana 30 Aug '23

30 Aug '23

Hi All, I would like to nominate myself to be Cinder PTL during the 2024.1 (Caracal) cycle. I have been the Cinder PTL for the last 3 cycles namely Zed, 2023.1 (Antelope) and 2023.2 (Bobcat). Few of the notable things we achieved in the past cycle are: ** OpenStack Client and SDK work: *We started two efforts in parallel: ** Migrate OSC commands to SDK[1] ** Add support of missing operations in SDK[2] We are making good progress in this area but looking at the work items[3], this effort will span across the next couple of cycles to be completed. ** Security Vulnerabilities:* We were able to address a major security vulnerability CVE-2023-2088 that prevents end users to delete volume attachments directly leaving left over devices on compute hosts resulting in data leaks. ** Transition from EM to Unmaintained: *We noticed the inactive contribution in extended maintenance branches and the need to fix gate issues from time to time. Also the project team is responsible to merge changes into these EM branches. After the recent CVE-2023-2088 wasn't proposed to EM branches, it was clear that the efforts were not worth the outcome so the Cinder team initiated a discussion regarding EOLing the current EM branches. There is a resolution from TC to migrate EM to unmaintained branches[4]. ** Outreachy Mentorship: *We had a successful quarter of outreachy internship from May-August 2023 with 2 interns, Desire and Toheeb. They were able to get a good amount of work done on the project "Automating generation of api-ref samples". ** Review bandwidth and quality:* We have been able to maintain good quantity and quality of reviews from contributors contributing from different organizations. Here are some work items we are planning for the next cycle (2024.1): * We still lack review bandwidth since one of our active cores, Sofia, couldn't contribute to Cinder anymore hence we will be looking out for potential core reviewers. * Continue working on migrating from cinderclient to OSC (and SDK) support. * Continue with the current cinder events like festival of XS reviews, midcycle, video meeting once a month etc that provides regular team interaction and helps tracking and discussion of ongoing work throughout the cycle. [1] https://review.opendev.org/q/topic:cinderclient-sdk-migration [2] https://review.opendev.org/q/topic:cinder-sdk-gap [3] https://docs.google.com/spreadsheets/d/1yetPti2XImRnOXvvJH48yQogdKDzRWDl-NY… [4] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… Thanks Rajat Dhasmana

2 1

Adding compute nodes to openstack cluster running wallaby
by Karera Tony 30 Aug '23

30 Aug '23

Hello Team, I am running openstack wallaby deployed using kolla-ansible and I am trying to add two compute node but I am getting this error. failed: [compute3] (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': 'kolla/ubuntu-source-cron:wallaby', 'environment': {'DUMMY_ENVIRONMENT': 'kolla_useless_env'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => {"ansible_loop_var": "item", "changed": true, "item": {"key": "cron", "value": {"container_name": "cron", "dimensions": {}, "enabled": true, "environment": {"DUMMY_ENVIRONMENT": "kolla_useless_env"}, "group": "cron", "image": "kolla/ubuntu-source-cron:wallaby", "volumes": ["/etc/kolla/cron/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "kolla_logs:/var/log/kolla/"]}}, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1241, in main\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 355, in compare_container\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 376, in check_container_differs\\n File \"/tmp/ansible_kolla_docker_payload_e49mzp45/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 571, in compare_dimensions\\nKeyError: \\'KernelMemory\\'\\n'"} Please advise Tony Regards Tony Karera

2 1

[release][ironic][OpenStackSDK][swift] cycle-with-intermediary deliverables without any release
by Herve Beraud 30 Aug '23

30 Aug '23

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2023.2 Bobcat cycle: The following deliverables have done a bobcat release, but it was not refreshed in the last two months: [ironic] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch [OpenStackSDK] python-openstackclient [swift] swift Those should be released ASAP, and in all cases before September 15, so that we have a release to include in the final 2023.2 Bobcat release. Thanks in advance, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[horizon] Cancelling Today's Weekly meeting
by vishal manchanda 30 Aug '23

30 Aug '23

Hello Team, As it is a holiday for me, I will not be able to host today's horizon weekly meeting. So let's cancel today's weekly meeting. If anything urgent, please reach out to the horizon core team. Thanks & regards, Vishal Manchanda

1 0

[election][ptl][openstack-helm] PTL Candidacy for 2024.1
by Vladimir Kozhukalov 30 Aug '23

30 Aug '23

Hello Everyone, I am pleased to announce my candidacy to continue as the PTL for OpenStack-Helm in the upcoming 2024.1 release cycle. ## Key accomplishments we have collectively achieved during the Bobcat cycle ### New Features: - Integrated a Manila chart, expanding the range of out-of-the-box use-cases. - Introduced OVN chart and support in Neutron, as OVN is emerging as the de facto standard for OpenStack networking. - Launched a Tacker chart to engage telecom sectors as potential users and contributors. - Upgraded the Elasticsearch chart to version 8.9.0. - Initiated the transition to Rook operator for Ceph management, with completion expected by cycle end. ### Pipeline and Compatibility: - Added Compute-kit and Cinder jobs to the check pipeline for Yoga, Zed, and Antelope releases, thereby extending the range of officially supported Openstack releases. ### Platform Support: - We stay Ubuntu-centric due to lack of resources for support of multiple platforms. During this cycle we introduced Ubuntu Jammy images, and initiated extensive testing for Jammy-based deployments. ### Other Improvements: - Enhanced Compute-kit job stability by adopting a multinode test environment for specific releases. - Cleaned up the OpenStack-Helm storyboard. Over 100 stories were reviewed, verified and fixed or closed. as outdated. - Numerous minor fixes and adjustments, including updates for recent Kubernetes releases. A big thank you to everyone for your contributions. ## Looking Ahead ### Documentation: The documentation still needs to be improved and aligned with all the recent changes. Users need clear understanding of how to deploy/upgrade Openstack components and which releases and scenarios are thoroghly tested and expected to work. ### Compatibility: We plan to continue expanding support for recent OpenStack and Kubernetes releases and additional Linux distributions. I am eager to continue in my role as PTL to ensure these initiatives move forward. Thanks. -- Best regards, Kozhukalov Vladimir

1 0

Nominations closing soon
by Amy Marrich 29 Aug '23

29 Aug '23

Hey all, There is less than 24 hours left for nominations to be committed to the election repos for PTL and TC. If you are a diverse member of the community and see a role you would like to try, especially if you’re a member of a leaderless project, step up and put your name in for a leadership role. There are plenty of us in the community who are willing to help mentor you in these roles. Amy(spotz)

1 0

[election][ptl][tacker] PTL Candidacy for 2024.1
by Yasufumi Ogawa 29 Aug '23

29 Aug '23

Hi, I'd like to nominate myself for Tacker PTL for 2024.1 cycle. I've contributed to Tacker as a PTL to provide a generic VNF Manager to industiries. We have implemented or improved several features such as monitoring with Prometheus for containers or policy management for multi domain usecases in addition to introduce the latest ETSI-NVF standard compliant features. We also revised unstable unit/functional tests for which we have been suffered several times for unexpected failures and waste of time as one of the our goals for efficiency of our development, and documents for users to demonstrate usecases in practical examples. In the next cycle, I'd like to continue to improving Tacker for the 5G network includes both a radio-access network and a core network to provide operators as we've focused on. Deploying Tacker as Service Management and Orchestration (SMO) in O-RAN architecture is one of our plans for realizing the scenario. Tacker team has already contributed to ETSI NFV and O-RAN SC communities while getting feedbacks from them and enforced relationship among them gradually. I'd appreciate if we make some more progress for OpenStack and these communities. Regards, Yasufumi (yasufum)

1 0

[scientific-sig] Fwd: Attract Top Talent at UC Berkeley’s Annual World of Data Career Fair for OpenInfra Foundation
by T. Nichole Williams 29 Aug '23

29 Aug '23

Greetings OpenStackers! If you or your organization is on the hunt for new talent, University of California Berkeley is holding an event called World of Data that may be of interest. If you’d like more info, please contact Sarah Son (sarahson(a)berkeley.edu <mailto:sarahson@berkeley.edu>) for more info. Have a lovely week everyone! Cheers, trilliams > Begin forwarded message: > > From: Sarah Son <sarahson(a)berkeley.edu> > Subject: Attract Top Talent at UC Berkeley’s Annual World of Data Career Fair for OpenInfra Foundation > Date: August 3, 2023 at 11:38:56 AM EDT > To: Treva Williams <tribecca(a)tribecc.us> > > Hi Treva! > > My name is Sarah and I am the External Vice President at UC Berkeley’s Student Association for Applied Statistics (SAAS). Nice to meet you! > > I’m reaching out to share some details about World of Data, an annual in-person Data Science Career Fair at UC Berkeley hosted by SAAS <https://saas.berkeley.edu/>, DSS <https://dssberkeley.com/>, and BDAB <https://bd.berkeley.edu/>, Berkeley’s leading student-run organizations for projects and education in data science. We are selective organizations that have helped several hundred Berkeley students cultivate their knowledge in data-related career fields and land positions at outstanding companies. Last September, the first-ever World of Data Career Fair reached an audience of over 400+ with companies such as Micron Technology and Accenture in attendance. We are looking forward to hosting the event again this fall at an even greater scale! > > This year, we would love to have OpenInfra Foundation participate in World of Data on September 20th, 2023. > > Our goal, as always, is to show our talented student body how data science can be applied to solve real-world problems in a diverse range of industries. > > We would love to collaborate with OpenInfra Foundation and learn how you leverage data science techniques to advance your company’s mission. The event will revolve around networking and connecting between students and recruiters at individual company booths, with a focus on data science/machine learning internships and full-time opportunities for summer 2024. > > In the past, our organizations have hosted events such as career fairs with 500+ attendees, annual Data Science Forums with 800+ attendees, annual Datathons for Social Good, and much more. Additionally, with university departmental support and our organization’s existing networks, we once again expect strong participation from promising students in the Statistics, Computer Science, and Data Science communities. > > I’ve attached a brochure below with more details and I'm happy to answer any questions you might have via email or over a call. Looking forward to your response! > > Warm regards, > Sarah > > – > Sarah Son > External Vice President | SAAS > UC Berkeley | Data Science > > >

1 0

[elections][manila] PTL Candidacy for 2024.1
by Carlos Silva 29 Aug '23

29 Aug '23

Hello everyone! I would like to announce my candidacy for the role of Manila PTL during the Caracal/2024.1 cycle. I have been in this role for the last 3 cycles and I would like to continue serving as PTL. During the past cycles, there was a lot of effort on promoting contributor collaboration through different activities and it helped us to make progress on closing gaps between the Manila APIs and other clients consuming them, as well as tackling tech debt and getting new features and drivers merged. I feel energized to continue pushing on these areas, but also put some focus on: * Working on the stability of our upstream CI first party jobs and also checking with third party CI maintainers to ensure their CI is healthy and reporting valid results. * Enhancing the review bandwidth and doing more actions to encourage more reviews from people submitting code to the Manila code base. * Work on documentation to help new contributors understand what are the requirements when proposing new features, and also continue the effort to cover the lack of documentation we have on third party CI setups for Manila, helping potential new vendors to quickly set up their CI systems. Thank you for your consideration! Carlos da Silva IRC: carloss

1 0

Query on Enabling Horizon Support for Creating SR-IOV VMs
by Aditya Sathish 29 Aug '23

29 Aug '23

Hello, We have enabled SR-IOV external interfaces on our server cluster running OpenStack Yoga. Unfortunately, there is a known limitation on the Horizon dashboard where we cannot create virtual machines through the dashboard - forcing us to rely on the OpenStack CLI to create the VMs. I wanted to understand what precisely the limitation was to support this from Horizon and if there were any cherry-picks I could pull from the later releases that would allow me to provide this support through the dashboard (or upgrade my release to 2023.1). I did see that we can now select the VNIC_Type from the dashboard, but that doesn't resolve the issue of VM creation with SR-IOV ports. Any points would be greatly appreciated. Regards, Aditya

1 0

[election][cloudkitty] PTL candidacy for Caracal
by Rafael Weingärtner 29 Aug '23

29 Aug '23

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the Caracal release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/893061 -- Rafael Weingärtner

1 0

[kolla] using local package mirror for image builds
by Jonathan Proulx 29 Aug '23

29 Aug '23

HI All, Using `kolla-build -b ubuntu` to build container images keeps timing out (well hanging for literal days) seemingly on package downloads from remote mirrors. I'm new to kolla and kolla-ansible so I may be misdiagnosing the cause of my current issue but we de have local ubuntu package mirros which would be faster in any case. Is there a way to specify using only a local package mirror? Thanks, -Jon

2 2

[tc] Technical Committee next weekly meeting today, August 29, 2023
by Nikolla, Kristi 29 Aug '23

29 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held today, Tuesday, 29 August 2023 at 1800 UTC on #openstack-tc on OFTC IRC. The agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and attached below: • Roll call • Follow up on past action items • No action items • Gate health check • 2022 user survey analysis • #link https://review.opendev.org/c/openstack/governance/+/892670/ • Documenting implementation processes for Unmaintained • With the resolution being merged, the next step is defining and documenting the processes and implementing the required tooling. • Open Discussion and Reviews • Register for the PTG • #link https://openinfra.dev/ptg/ • #link https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[ptl][election][kuryr] PTL candidacy for 2024.1
by Roman Dobosz 29 Aug '23

29 Aug '23

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next 2024.1 (Caracal) cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. I'm also the PTL since Antelope cycle. In the upcoming 2024.1 cycle, I'd like to focus on Kuryr maintenance, stability and compatibility with upcoming Kubernetes release. Thanks, Roman Dobosz (gryf)

1 0

[publiccloud-sig] Reminder - next meeting August 30th - 0700 UTC
by Felix Kronlage-Dammers 29 Aug '23

29 Aug '23

Hi everyone, this Wednesday the next meeting of the public cloud sig is going to happen. We meet on IRC in #openstack-operators at 0700 UTC. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[Neutron] Default gateway for IPv6 is 0
by Xing Zhang 29 Aug '23

29 Aug '23

Hello everyone, In my test environment, I noticed that the default gateway for IPv6 is changed from 1 to 0, is this correct? Reproduce steps are: * openstack cli: openstack network create test-ipv6-net openstack subnet create --subnet-range 2001:db8::200:0/64 --ip-version 6 --ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful --network test-ipv6-net test-ipv6-subnet # the gateway_ip in the output is 2001:db8::200: but 2001:db8::200:1 is the expected IP * neutron cli: neutron net-create test-v6 neutron subnet-create --name test-v6-subnet --ip-version 6 test-v6 2002:db8::200:0/64 # the gateway_ip in the output is 2001:db8::200: but 2001:db8::200:1 is the expected IP there are 3 versions of OpenStack I've tested, the results are: OpenStack Rocky: 2001:db8::200:1 OpenStack Train: 2001:db8::200:1 OpenStack Wallaby: 2001:db8::200: the virtual router will use the gateway ip for port, and some hardware networking sdn controller for neutron may not work.

2 1

[ptls][tc] OpenStack User Survey Updates
by Allison Price 29 Aug '23

29 Aug '23

Hi Everyone, Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers. If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey. In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can. Cheers, Allison

7 24

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations Last Days
by Tony Breeds 29 Aug '23

29 Aug '23

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 30, 2023 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2023-08-16 23:45:00 UTC Nominations end @ 2023-08-30 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 1 day, 22:20:09 Nominations progress : 86.21% --------------------------------------------------- Projects[1] : 48 Projects with candidates : 18 ( 37.50%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Ec2_Api Glance Heat Horizon Keystone Kuryr Manila Mistral Monasca Octavia OpenStack_Helm Openstack_Chef Puppet_OpenStack Rally Sahara Senlin Skyline Storlets Sunbeam Swift Tacker Telemetry Trove Venus) --------------------------------------------------- TC Candidates : 4 (4 Required) =================================================== Stats gathered @ 2023-08-29 01:24:51 UTC This means that with approximately 2 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… Yours Tony.

1 0

[nova][election] Self-nomination for 2024.1 Nova PTL
by Sylvain Bauza 28 Aug '23

28 Aug '23

Hey Nova and Placement folks, Yet again, I'm asking you to put myself on the Nova and Placement PTL seat. For the exact same reasons than last time (see my previous nomination e-mail), I was convinced to run again for this position, which hopefully will be the last one (despite having already said it once). Challenges are still upfront. Our gate is still coughing every single day and despite the excellent work that a very few awesome people did on stabilizing and which helped improving the situation (kudos to those who will recognize themselves), we are still urging to fix the most common patterns. As a PTL, I'll ensure to keep the energy to chase those issues and identify them so as a team we can fight them. Another concern to me is the reviewing pace. While we're continuing to deliver solid reviews on feature proposals and patches, our team isn't much evolving and we need fresh blood. In order to be able to deliver things, we need to ensure that we properly recognize those who dedicate a portion of their daytime to help others by providing valuable feedback (and I stress on the fact that this feedback *has to* be valuable in order to by worthy). As a PTL, I'll continue to encourage people to express their thoughts and concerns into Gerrit comments so that we are able to count on. The last challenge I have to mention here is the release cadence. Now that more people are getting noticed of the SLURP cadence, we'll be awaited on delivering our next SLURP release, which will be 2024.1 (Caracal). I'll take special attention to that, ensuring that our skip-level-upgrade process we have in Nova will conveniently work with Caracal and that our release notes correctly include the upgrade steps for those who skip 2023.2 (Bobcat). I'll just finish on a last word. While I really appreciated acting as a PTL for the last 4 cycles, I'd be more than happy if someone would like to step up and compete for the seat. I personnally prefer expansion over attrition and one of my favourite tasks is mentoring. Thanks, -Sylvain

1 0

Red Hat Open stack external IP pool change
by Adivya Singh 28 Aug '23

28 Aug '23

Hi Team, Does any body have seen this issue, I am running RHOSP 16 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6.ExternalSubnet]: UPDATE_FAILED NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx.ExternalNetwork]: UPDATE_FAILED NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [Networks]: UPDATE_FAILED NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. I delete the interface from OVS bridge and restart the OVS services and re push the templates Or I change the File manually, Configure any floating ip range , Add the route manually , and restart the Network services Any thought on this Regards Adivya Singh

1 0

[neutron] Bug Deputy Report August 21 - 27
by Nurmatov Mamatisa 28 Aug '23

28 Aug '23

Hi, Below is the week summary of bug deputy report for last week. Undecided bugs needs further triage. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2032738 - [os-ken] [CI] Jobs setting up os-ken from pypi instead of patch in review - Fixed: https://review.opendev.org/c/openstack/os-ken/+/892452 - Assigned to Yatin Karel - https://bugs.launchpad.net/neutron/+bug/2032817 - OVN: Distributed FIP packet drops when provider network MTU exceeds tenant network MTU - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2033090 - Able to change vnic type on a bound port - In progress: https://review.opendev.org/c/openstack/neutron/+/892815 - Assigned to Jakub Libosvar Medium ------ - https://bugs.launchpad.net/neutron/+bug/2032169 - OVN synchronized too many segments - In progress: https://review.opendev.org/c/openstack/neutron/+/891930 - Assigned to Zhou Heng - https://bugs.launchpad.net/neutron/+bug/2032183 - [CI] UT py311 job failing, "libmysqlclient-dev" missing - Fixed: https://review.opendev.org/c/openstack/neutron/+/892142 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2032765 - [L3][DVR]disable ARP response for vlan networks on compute node - Confirmed - Unassigned Low --- - https://bugs.launchpad.net/neutron/+bug/2032770 - [OVN] port creation with --enable-uplink-status-propagation does not work with OVN mechanism driver - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2032929 - OVN security group logging burst limit has an unexpected value for stateless security groups - In progress: https://review.opendev.org/c/openstack/neutron/+/892648 - Assigned to Elvira García Ruiz - https://bugs.launchpad.net/neutron/+bug/2033203 - Quality of Service (QoS) in Neutron - Confirmed - Unassigned Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2032973 - Neutron is not creating DNS records when recreating an instance with the same floating IP - https://bugs.launchpad.net/neutron/+bug/2033179 - Using .local as TLD in dns testing is breaking some scenarios Invalid ------ - https://bugs.launchpad.net/neutron/+bug/2033083 - [OVN] The router GW is "restoring" the NAT rule that disables SNAT - Ironic bug Best regards, Mamatisa Nurmatov Advanced Software Technology Lab / Cloud Technologies Research

1 0

TripleO deployment over IPV6
by Kushagr Gupta 26 Aug '23

26 Aug '23

Hi Team, We were trying to perform IPV6-based deployment of TripleO. We are following the link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… As per our environment, we set the "ipv6_address_mode" to "dhcpv6-stateful" and tried undercloud deployment. It was successful. But when we try node introspection, openstack is not providing an IP that will be used for PXE booting the system. We have enabled PXE booting on the IPV6 network. On Dell machines, we get the following error: "PXE-E16: No offer received." For your reference, the undercloud file which we used is attached. We also tried to find the communication happening on the br-ctlplane interface when the machine tries to boot over IPV6 PXE boot. I am attaching those tcpdump records as well. We are unable to find the MAC address of our machines. *Questions:* 1. Is it even possible to perform tripleO deployment with IPV6? 2. Do we need to do some extra settings, so that our baremetal machines can be PXE booted? Thanks and Regards

3 9

Live migration between centos and ubuntu compute nodes
by Jim Kilborn 25 Aug '23

25 Aug '23

Openstack peers: I am migrating our production openstack environment from centos7 to ubuntu. I am on the train release currently, so I can have that release on both centos7 and ubuntu 18 The issue is that I need to live migrate the vms if it's possible. When I try, I get an error on the source compute node (centos 7). Live Migration failure: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory: libvirtError: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory Any ideas how to get around this until I get my vms migrated? Maybe create a link on the ubuntu 18 host? I'm sure I am not the first to leave centos 7 for ubuntu Thanks for any help on this.

2 1

[keystone] outstanding reviews for federation fix
by Mohammed Naser 25 Aug '23

25 Aug '23

Hi there, Can I please get eyes on https://review.opendev.org/q/I665b7e0234650ba07e0d030a2d442d6599d0888a ? We’ve been carrying this down for too long and it’s a very simple fix. Thanks, Mohammed

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 25 Aug '23

25 Aug '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

[release] Release countdown for week R-5, Aug 28 - Sep 01
by Thierry Carrez 25 Aug '23

25 Aug '23

Development Focus ----------------- We are getting close to the end of the 2023.2 Bobcat cycle! Next week on August 31st is the bobcat-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2024.1 Caracal cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on August 31st. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… August 31st is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Bobcat-3 milestone (feature freeze): August 31st (R-5 week) RC1 deadline: September 14th (R-3 week) Final RC deadline: September 28th (R-1 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0

[ptl][election][neutron] PTL candidacy for 2024.1
by Brian Haley 24 Aug '23

24 Aug '23

Hello Openstack Community, I am writing to submit my candidacy for the Neutron PTL position during the 2024.1 cycle. I have worked on Openstack since Diablo (2011), starting as a cloud operator doing L2 overlay development, along with agent performance and scalability on large-scale deployments. During that time I've become a core contributor (2015) and been part of the team making sure our stable branches continue to receive all the back-ports necessary to make downstream consumption easier. I currently work for Canonical in their Sustaining Engineering group, primarily addressing customer issues, with a focus on processes and tools to help us more quickly solve them. My priorities as PTL would be the following: * Always make sure the stable branches are consumable downstream. Distros and operators are, in my opinion, the lifeblood of Openstack, so we have to make sure they are top of mind when fixing bugs, and that back-ports are done in a timely manner. * Continue pursuing CI stability. During the past 6+ cycles the Neutron community has done a great job keeping its CI healthy, as well as actively updating jobs to make sure we use resources wisely and reduce re-checks. * Keep working on, or complete, ongoing specs. There are a number of larger specs that have a great deal of development in progress, I know we can get some of these completed this cycle: ** Active-active L3 Gateway with Multihoming (LP #2002687) ** Multiple back-end support for L3 routers in ML2/OVN (LP #2020823) ** Configurable Security Group rules added by default to new Security Groups (LP #1983053) ** ML2/OVN IPv6 Distributed routing (LP #1998609) * Continue reducing the bug backlog. Over the past few cycles we were able to fix and/or close about 1/3 of our backlog (~400 bugs), but it will slowly creep back up if we let it. We also have to continue looking forward by: * Keeping the Neutron stadium ecosystem alive and healthy. There are a number of diverse projects, some without a large number of resources. We must make sure those communities receive whatever help they need, whether it's making sure we address bugs affecting them, or helping keep their CIs green. * Address any SQLAlchemy 2.0 migration issues detected. We have done a great job during the last few releases with this work, let's keep that up in 2024.1. * Starting development on newly proposed specs ** OVN interconnection (LP #2027742) * Always welcoming new contributors. Thanks for your support. -Brian Haley (haleyb, haleyb.dev(a)gmail.com)

1 0

Cinder Bug Report 2023-08-23
by Jon Bernard 23 Aug '23

23 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Medium - Cinder-Backup stuck in creating after RBD export-diff existed and turned into zombie / <defunct> <https://bugs.launchpad.net/cinder/+bug/2031897> - Status: No comments or fix proposed Undecided - Cinder allows updating default volume type <https://bugs.launchpad.net/cinder/+bug/2031653> - Status: In Progress - Extending an attached volume leaves multipath device in inconsistent state <https://bugs.launchpad.net/os-brick/+bug/2032177> - Status: In Progress Thanks -- Jon

1 0

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

Cyber Resilience Act: What Now? Aug 24 at 9 AM (CST) / 14:00 UTC
by Kristin Barrientos 23 Aug '23

23 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: On this episode of OpenInfra Live, we will discuss the EU Cyber Resilience Act's impact on open source software. The OpenInfra Foundation and many other open source organizations have expressed concerns about the proposed text, urging the European lawmakers to take into account the specificity of open source open collaboration in the legislation. Join and engage live with our expert panelists as they discuss the current state of the proposal, its potential consequences, what we can still do about it, and what other pieces of upcoming legislation we should watch for. Date and time: Aug 24, 2023 at 9:00 AM CST (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=u6Dh0nXivqM LinkedIn: https://www.linkedin.com/events/7095407763538763776/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Thierry Carrez, Allison Randal, Mike Milinkovich, Ciarán O'Riordan Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[cinder] 2023.2 (Bobcat) R-6 virtual mid cycle on 23 Aug, 2023
by Rajat Dhasmana 23 Aug '23

23 Aug '23

Hello Argonauts, As discussed in last week's cinder upstream meeting[1], we will be conducting our second mid cycle of 2023.2 Bobcat on 23rd August, 2023 (R-6 week). Following are the details: Date: 23rd August, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/qqs-xjzg-ccm Etherpad: https://etherpad.opendev.org/p/cinder-bobcat-midcycles We have almost a week's time so please add your topics! [1] https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-…

1 2

[neutron][tap-as-a-service][release] Deletion old branches of taas
by Rodolfo Alonso Hernandez 23 Aug '23

23 Aug '23

Hello: I would like to revive the mail sent by Lajos about this topic: https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03127…. In a nutshell: we don't have releases from Ocata to Stein of TaaS because it was moved out from the stadium projects. However we still have issues with the zuul configs. Because we can't release an EOL patch, I would ask the release team to remove these 5 branches (Ocata, Pike, Queens, Rocky and Stein) from the git repository. If that is not possible, I'll send patches to these branches to remove the .zuul file. Regards. [1]https://zuul.opendev.org/t/openstack/config-errors

1 0

[ovn] VM in external network unable to arp
by Justin Lamp 23 Aug '23

23 Aug '23

Hey, we are using OVN 22.03 and face an issue where a VM that is directly connected to the provider network won't be accessible, because it cannot arp for the Gateway IP. OVN routers do reply to the arp request though. We know that this exact scenario works as we have it running in our staging environment. Oddly enough if the right MAC-IP Binding is manually defined within the VM and the Gateway, the traffic will begin to flow correctly according to the right SGs. I did an ovn-trace and were able to see that the traffic is supposed to be flooded to the right ports. The ovs-trace on the other hand did not show the same picture. It just did 4k recirculations and then dropped the packet. I already restarted the ovn-controller on the right hv, but that did not do anything. The LSP: $ ovn-nbctl list Logical_Switch_Port cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : c5dfb248-941e-4d4e-af1a-9ccafc22db70 addresses : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] dhcpv4_options : 1922ee38-282f-4f5c-ade8-6cd157ee52e9 dhcpv6_options : [] dynamic_addresses : [] enabled : true external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} ha_chassis_group : [] name : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_name : [] port_security : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] tag : [] tag_request : [] type : "" up : true The PB: $ ovn-sbctl find Port_Binding logical_port=cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : e9e5ce44-698f-4a29-acd1-2f24cc1d1950 chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 datapath : 993b44d5-1629-4e9b-b44e-24096d8b3959 encap : [] external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} gateway_chassis : [] ha_chassis_group : [] logical_port : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" mac : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] nat_addresses : [] options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_port : [] requested_chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 tag : [] tunnel_key : 344 type : "" up : true virtual_parent : [] The LS: $ ovn-nbctl list Logical_Switch public-network _uuid : 56d8be55-462a-4b93-8710-3c79ca386213 acls : [] copp : [] dns_records : [] external_ids : {"neutron:mtu"<neutron:mtu>="1500", "neutron:network_name"<neutron:network_name>=public-network, "neutron:revision_number"<neutron:revision_number>="21"} forwarding_groups : [] load_balancer : [] load_balancer_group : [] name : neutron-210e26d7-942f-4e17-89b2-571eee87d7e4 other_config : {mcast_flood_unregistered="false", mcast_snoop="false"} ports : [00225774-8fbc-473f-ae5e-d486c54212c8, ..., c5dfb248-941e-4d4e-af1a-9ccafc22db70, ... qos_rules : [] The patchport: $ ovn-nbctl list Logical_Switch_Port provnet-aa35051c-6fc0-463a-8807-0cb28903be14 _uuid : f7259aeb-0e63-4d20-8a8e-54ebf454a524 addresses : [unknown] dhcpv4_options : [] dhcpv6_options : [] dynamic_addresses : [] enabled : [] external_ids : {} ha_chassis_group : [] name : provnet-aa35051c-6fc0-463a-8807-0cb28903be14 options : {mcast_flood="false", mcast_flood_reports="true", network_name=physnet1} parent_name : [] port_security : [] tag : [] tag_request : [] type : localnet up : false I hope I provided the needed context! Thanks in advance! Best regards, Justin Lamp -- Justin Lamp Systems Engineer NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk, Sebastian Saemann | AG Nuernberg HRB25207 https://www.netways.de | justin.lamp(a)netways.de ** stackconf 2023 - September - https://stackconf.eu ** ** OSMC 2023 - November - https://osmc.de ** ** NETWAYS Web Services - https://nws.netways.de ** ** NETWAYS Trainings - https://netways.de/trainings **

4 5

Need assistance
by Gk Gk 23 Aug '23

23 Aug '23

Hi All, We have an openstack ansible stein version setup. We had a vm on it which we deleted. The associated neutron port was also deleted and the vm uuid is gone from the nova as well. It had a provider network ip. Even after deleting the vm, we are still finding that ssh port 22 on that IP is responding. So I logged into the hypervisor (compute node) on which that vm was there before deletion and found that the libvirtd service was is error state with the following logs in the nova-compute service: --------- 2023-08-18 10:08:51.463 12587 INFO nova.service [-] Starting compute node (version 19.3.2) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self.force_reraise() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(self.type_, self.value, self.tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 442, in _get_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self._wrapped_conn = self._get_new_connection() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 396, in _get_new_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host wrapped_conn = self._connect(self._uri, self._read_only) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 252, in _connect 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirt.openAuth, uri, auth, flags) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 148, in proxy_call 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = execute(f, *args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 129, in execute 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(c, e, tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = meth(*args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/libvirt.py", line 104, in openAuth 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host if ret is None:raise libvirtError('virConnectOpenAuth() failed') 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service [req-4108e9e2-2afd-472e-a4d9-fcccffc380dc - - - - -] Error starting thread.: HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service Traceback (most recent call last): 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_service/service.py", line 810, in run_service 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service service.start() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/service.py", line 176, in start 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.manager.init_host() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/compute/manager.py", line 1225, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.driver.init_host(host=self.host) 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 503, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self._do_quality_warnings() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 471, in _do_quality_warnings 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service caps = self._host.get_capabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 664, in get_capabilities 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service xmlstr = self.get_connection().getCapabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 482, in get_connection 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service raise exception.HypervisorUnavailable() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service 2023-08-22 14:28:07.678 12587 INFO nova.virt.libvirt.driver [-] Connection event '0' reason 'Failed to connect to libvirt: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused' ----- However that particular neutron port for that vm is also deleted. We cant find it in the neutron db. So how is it possible for that VM IP to be responding on port 22 even after it is deleted. Please help me here. Thanks Kumar

4 3

vPTG October 2023 Teams List
by Kendall Nelson 22 Aug '23

22 Aug '23

Hello Everyone! The October 2023 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - OpenInfra Edge Computing Group - Environmental Sustainability Working Group - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Kolla - Manila - Neutron - Nova - Octavia - OpenStack Charms - OpenStack-Helm - Quality Assurance - OpenStackSDK/CLI - Swift - Tacker - Other OpenStack Teams - - Interoperability Working Group - OpenStack Security SIG - PublicCloud SIG If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — It's FREE! As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg2023.openinfra.dev/

1 0

Collaborating Without Boundaries Working Group - Meeting #2 Tomorrow at 1500 UTC
by Helena Spease 22 Aug '23

22 Aug '23

Hi everyone! Tomorrow at 1500 UTC the OpenInfra Collaborating Without Boundaries Working Group is meeting! If you are a university or organization interested in OpenStack training come learn from Seongsoo Cho, how the Korean User Group is partnering with local universities to provide training opportunities to students. Etherpad : https://meetpad.opendev.org/etherpad/p/cwb <https://meetpad.opendev.org/etherpad/p/cwb> Meetpad: https://meetpad.opendev.org/CWB <https://meetpad.opendev.org/CWB> Cheers, Helena helena(a)openinfra.dev Marketing & Community Coordinator The OpenInfra Foundation

1 0

[tc] Technical Committee Next Weekly Meeting, Today on August 22, 2023
by Nikolla, Kristi 22 Aug '23

22 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held Today, on Tuesday, 22 August 2023 at 1800 UTC on #openstack-tc on OFTC IRC. The agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and attached below. • Roll call • Follow up on past action items • No action items • Gate health check • Documenting implementation processes for Unmaintained • With the resolution being merged, the next step is defining and documenting the processes and implementing the required tooling. • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[dev][glance_storage][s3] improving download speed from s3 backend
by Gökhan Koçak 22 Aug '23

22 Aug '23

Hello everyone, I did not find any option to use something like multipart downloads (only uploads) or concurrency when downloading from s3 storage. So my first question is if this is correct? Second, I see that boto3 is being used: https://opendev.org/openstack/glance_store/src/branch/master/glance_store/_… and I wonder if it is possible to implement using the concurrency settings from boto: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/customiza… ? Best, Gökhan

1 0

[nova] Slow nvme performance for local storage instances
by Jan Wasilewski 22 Aug '23

22 Aug '23

Hi, I am reaching out to inquire about the performance of our local storage setup. Currently, I am conducting tests using NVMe disks; however, the results appear to be underwhelming. In terms of my setup, I have recently incorporated two NVMe disks into my compute node. These disks have been configured as RAID1 under md127 and subsequently mounted at /var/lib/nova/instances [1]. During benchmarking using the fio tool within this directory, I am achieving approximately 160,000 IOPS [2]. This figure serves as a satisfactory baseline and reference point for upcoming VM tests. As the next phase, I have established a flavor that employs a root disk for my virtual machine [3]. Regrettably, the resulting performance yields around 18,000 IOPS, which is nearly ten times poorer than the compute node results [4]. While I expected some degradation, a tenfold decrease seems excessive. Realistically, I anticipated no more than a twofold reduction compared to the compute node's performance. Hence, I am led to ask: what should be configured to enhance performance? I have already experimented with the settings recommended on the Ceph page for image properties [5]; however, these changes did not yield the desired improvements. In addition, I attempted to modify the CPU architecture within the nova.conf file, switching to Cascade Lake architecture, yet this endeavor also proved ineffective. For your convenience, I have included a link to my current dumpxml results [6]. Your insights and guidance would be greatly appreciated. I am confident that there is a solution to this performance disparity that I may have overlooked. Thank you in advance for your help. /Jan Wasilewski *References:* *[1] nvme allocation and raid configuration: https://paste.openstack.org/show/bMMgGqu5I6LWuoQWV7TV/ <https://paste.openstack.org/show/bMMgGqu5I6LWuoQWV7TV/>* *[2] fio performance inside compute node: https://paste.openstack.org/show/bcMi4zG7QZwuJZX8nyct/ <https://paste.openstack.org/show/bcMi4zG7QZwuJZX8nyct/>* *[3] Flavor configuration: https://paste.openstack.org/show/b7o9hCKilmJI3qyXsP5u/ <https://paste.openstack.org/show/b7o9hCKilmJI3qyXsP5u/>* *[4] fio performance inside VM: https://paste.openstack.org/show/bUjqxfU4nEtSFqTlU8oH/ <https://paste.openstack.org/show/bUjqxfU4nEtSFqTlU8oH/>* *[5] image properties: https://docs.ceph.com/en/pacific/rbd/rbd-openstack/#image-properties <https://docs.ceph.com/en/pacific/rbd/rbd-openstack/#image-properties>* *[6] dumpxml of vm: https://paste.openstack.org/show/bRECcaSMqa8TlrPp0xrT/ <https://paste.openstack.org/show/bRECcaSMqa8TlrPp0xrT/>*

5 18

[sunbeam] Juju 3.2 stable release break
by James Page 22 Aug '23

22 Aug '23

Morning The Juju project popped a new stable release of the 3.2 series we currently use for Sunbeam; this has created a problem with the mysql-k8s charm that we rely on for Sunbeam deployment and as such any new deployments will fail. The team is focussed on resolving this ASAP as this is breaking all of our check/gates right now as well. Regards James

1 0

[elections][tc] Self-nominate for Technical Committee
by Dmitriy Rabotyagov 22 Aug '23

22 Aug '23

Hello everyone! I want to nominate myself for the second term on a Technical Committee. During the first term, I actively participated in various TC activities, including a change of the platform for PTI, better defining expectations on projects for removing support for older Python versions, and others. While it took me time to get up to speed and understand better how things are done, I feel being efficient since then as well as bringing value to the table during discussions. Apart from TC activities, I am currently a Core Reviewer and Project Team Leader of OpenStack-Ansible and Vitrage projects. I am a strong advocate for diversity and inclusion, which now is even more important than ever before when corporations are diverting from their commitments to open-source software. I believe that diverse and community-driven projects better represent the real needs of end users and operators. Throughout my career, I have been dealing mostly with Public Clouds, which have a way wider variety of use cases and perspectives than any single corporate solution can have. With that in mind, I want to continue supporting an inclusive environment for all community members as well as connecting operators and developers worlds during the next term of the Technical Committee member. Thanks for your consideration!

3 2

swift_objects are not getting saved in container
by Gaurav Oberai 22 Aug '23

22 Aug '23

Hi Team, We have a setup running with OpenStack Swift setup and a proxy server. We have also used s3api middleware in proxy-server configuration to store objects like AWS s3. Now we are facing issues like objects are not getting stored inside the container instead we are able to store the objects on storage nodes successfully and get a successful response for every request. We have verified the same by listing the objects using the aws-s3 command line utility. However, when tried with OpenStack swift command buckets and objects are not visible inside the container. My concern is how objects are saved if the container is not saving them and how can we fix this issue to store all objects inside the container? Could you please help me with this? Thanks & Regards, Gaurav

2 1

[barbican][cinder][cloudkitty][freezer][heat][ironic][keystone][mistral][monasca][murano][nova][OpenStackSDK][oslo][sahara][Telemetry][zaqar][zun] broken gate on master branch
by Elõd Illés 21 Aug '23

21 Aug '23

Hi $teams_in_subject, I've generated test patches to see gate health (to projects' for cycle-with-intermediary deliverables, that have not merged any patches recently) and the patches show [1] that you have broken CI jobs on your gate. Could the teams please check what the issue / issues are and fix as soon as possible? Thanks in advance! (Note: multiple times I see that the failure in docs job is: Handler <function html_page_context at 0x7f86178f55a0> for event 'html-page-context' threw an exception (exception: object of type 'PosixPath' has no len()) so several gates can be fixed with a fix to this issue) [1] https://review.opendev.org/q/topic:release-health-check-cwi-bobcat+is:open Thanks, Előd Illés irc: elodilles @ #openstack-release

3 3

Re: Kayobe VLAN & bond configuration
by Stefan Pinter 21 Aug '23

21 Aug '23

Hi again! After rebooting the server an cleaning up everything in /etc/systemd/network/ it does work again (kayobe overcloud host configure) but I am afraid to run “kayobe overcloud service deploy”. Can anyone confirm that the configuration might be correct or has an idea about what happened in the network there? Multicast storm? Broadcast storm? Troubles with STP? Thank you and best wishes Stefan ________________________________ BearingPoint GmbH Sitz: Wien Firmenbuchgericht: Handelsgericht Wien Firmenbuchnummer: FN 175524z The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

3 4

[nova-api] Inject public key without create key pair in nova ?
by Pureewat Kaewpoi 21 Aug '23

21 Aug '23

Hi OpenStack Community We have some requirements that need to create instance via API. However nova-api is accept only key_name of key pair created earlier. Can we create instance by passing only public key data without creating a key pair in nova ? Thank you.

4 6

[glance][kolla] importing images on filesystem without copy?
by Rob Jefferson 21 Aug '23

21 Aug '23

Folks, I'm trying to wrap my brain around whether this is possible. Suppose I've configured Glance to use a filesystem backend. Would I be able to point Glance at a directory of existing images, and have it import the images into OpenStack (thus populating the database) without having to copy them? It seems fairly redundant to have the images on the filesystem, and to make copies as part of the creation process. Looking around in the documentation, it seems that this may not be possible, but I'm not sure if there's an alternate path or if what I'm asking is ill-posed. Any advice would be useful. Thanks, Rob

3 2

[charms] Nominate Martin Kalcok for charms-core
by Frode Nordahl 21 Aug '23

21 Aug '23

Hello all, I would like to nominate Martin Kalcok for charms-core. He has been part of the extended charms teams for some time now, and has provided many contributions to OpenStack, Ceph and OVN charms [0]. He is diligent and thorough in his contributions, and has recently become a full time member of the focused OVN team. 0: https://review.opendev.org/q/owner:martin.kalcok%2540canonical.com -- Frode Nordahl

5 4

Unable to Live/Cold migrate instances that have ceph root and secondary netapp storage devices | Wallaby
by Swogat Pradhan 21 Aug '23

21 Aug '23

Hi, I have an instance that has disk /dev/vda present in ceph and the rest of the 6 volumes (10 TB) each on netapp. I am trying to migrate the VM to another host but it is failing to migrate with error volume not found like below: 2023-08-21 09:22:31.852 7 WARNING os_brick.initiator.connectors.iscsi [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] Couldn't find iSCSI nodes because iscsiadm err: iscsiadm: No records found : os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:31.866 7 WARNING os_brick.initiator.connectors.iscsi [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] iscsiadm stderr output when getting sessions: iscsiadm: No active sessions. : os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] Exception during message handling: os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/exception_wrapper.py", line 72, in wrapped 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server context, exc, binary) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/exception_wrapper.py", line 63, in wrapped 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/utils.py", line 1437, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 212, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 200, in decorated_function 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 8288, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server bdm.save() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/manager.py", line 8249, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server migrate_data) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 10343, in pre_live_migration 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self._connect_volume(context, connection_info, instance) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 1808, in _connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server vol_driver.connect_volume(connection_info, instance) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/virt/libvirt/volume/iscsi.py", line 64, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server device_info = self.connector.connect_volume(connection_info['data']) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 154, in trace_logging_wrapper 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 524, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self._cleanup_connection(connection_properties, force=True) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.value 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 518, in connect_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self._connect_single_volume(connection_properties) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 78, in _wrapper 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return r(f, *args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 409, in call 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server do = self.iter(retry_state=retry_state) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 368, in iter 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise retry_exc.reraise() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 186, in reraise 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self.last_attempt.result() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server return self.__get_result() 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise self._exception 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 412, in call 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server result = fn(*args, **kwargs) 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 597, in _connect_single_volume 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server raise exception.VolumeDeviceNotFound(device='') 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server os_brick.exception.VolumeDeviceNotFound: Volume device not found at . 2023-08-21 09:22:34.348 7 ERROR oslo_messaging.rpc.server 2023-08-21 09:22:34.678 7 INFO nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Attempting to driver detach volume a005a015-0bb2-498e-9068-ac14570a5f2e from mountpoint /dev/vda 2023-08-21 09:22:34.680 7 WARNING nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Detaching volume from unknown instance 2023-08-21 09:22:34.682 7 WARNING nova.virt.libvirt.driver [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] During detach_volume, instance disappeared.: nova.exception.InstanceNotFound: Instance 5520dbd7-8f12-4041-bd8c-65b4b55b0452 could not be found. 2023-08-21 09:22:34.707 7 INFO nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Attempting to driver detach volume 01b9b430-9cfd-43b1-b674-b6fb830ee511 from mountpoint /dev/vdb 2023-08-21 09:22:34.708 7 WARNING nova.virt.block_device [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] Detaching volume from unknown instance 2023-08-21 09:22:34.710 7 WARNING nova.virt.libvirt.driver [req-6ed9d181-fa42-4a4a-b55b-2d08352d4e22 9f20ac539d60ff27487ce83f160e3c29bbeea1017d28fb5159b17c9e77454345 265571cce0b54251b17ace88630b5e46 - 64989c3036764834a755ff2bd55b30b3 64989c3036764834a755ff2bd55b30b3] [instance: 5520dbd7-8f12-4041-bd8c-65b4b55b0452] During detach_volume, instance disappeared.: nova.exception.InstanceNotFound: Instance 5520dbd7-8f12-4041-bd8c-65b4b55b0452 could not be found. Server show : +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | AUTO | | OS-EXT-AZ:availability_zone | Watson | | OS-EXT-SRV-ATTR:host | overcloud-novacompute-0.bdxworld.com | | OS-EXT-SRV-ATTR:hostname | hkg2-cctv-archive-server-2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | overcloud-novacompute-0.bdxworld.com | | OS-EXT-SRV-ATTR:instance_name | instance-0000012f | | OS-EXT-SRV-ATTR:kernel_id | | | OS-EXT-SRV-ATTR:launch_index | 0 | | OS-EXT-SRV-ATTR:ramdisk_id | | | OS-EXT-SRV-ATTR:reservation_id | r-mdrfy13i | | OS-EXT-SRV-ATTR:root_device_name | /dev/vda | | OS-EXT-SRV-ATTR:user_data | None | | OS-EXT-STS:power_state | Running | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2023-01-05T09:49:54.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | HKG2-CCTV=192.168.240.14 | | config_drive | True | | created | 2023-01-05T09:49:46Z | | description | HKG2-CCTV-Archive-server-2 | | flavor | disk='150', ephemeral='0', extra_specs.hw:cpu_cores='10', extra_specs.hw:cpu_sockets='2', original_name='CCTV-VM-Flavor', ram='16384', swap='0', | | | vcpus='10' | | hostId | 570b5ef66c44d3f80a1a498c9dbd8b9a2b690a1aee748bc9cb2cf6fb | | host_status | UP | | id | 5520dbd7-8f12-4041-bd8c-65b4b55b0452 | | image | N/A (booted from volume) | | key_name | None | | locked | False | | locked_reason | None | | name | HKG2-CCTV-Archive-server-2 | | progress | 0 | | project_id | 265571cce0b54251b17ace88630b5e46 | | properties | | | security_groups | name='CCTV services Incoming' | | | name='CCTV services Outgoing' | | server_groups | [] | | status | ACTIVE | | tags | | | trusted_image_certificates | None | | updated | 2023-08-21T09:22:35Z | | user_id | ff69985eea81fe6f11e9caa3f242623cbddc7ce21cdd864c9585d793533acb9e | | volumes_attached | delete_on_termination='False', id='a005a015-0bb2-498e-9068-ac14570a5f2e' | | | delete_on_termination='False', id='01b9b430-9cfd-43b1-b674-b6fb830ee511' | | | delete_on_termination='False', id='a385a416-1d37-4111-b7ae-f182a54aeaef' | | | delete_on_termination='False', id='95bafa69-b7cc-4d35-9002-723ca556a570' | | | delete_on_termination='False', id='b5091e83-2afb-457c-abf8-ed855156b59f' | | | delete_on_termination='False', id='0e9762bd-5229-433d-825e-6c7a77c6927c' | | | delete_on_termination='False', id='9a00e144-8755-48d5-8907-7fa499172371' | +-------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ Please suggest how I can migrate the instance. With regards, Swogat Pradhan

1 1

[election][openstack-ansible]
by Dmitriy Rabotyagov 21 Aug '23

21 Aug '23

Hello everyone! I would like to announce my candidacy for the role of PTL of OpenStack-Ansible during the 2024.1 (Caracal) cycle. For the next cycle I want to pay attention on the following topics: * Updating documentation to correspond new defaults * Keep up with latest supported versions of infrastructure software, like MariaDB, RabbitMQ and Ansible * Promote the project on various events and ensure project compatibility with various vendors * Perform clean-up of old functional testing and test repo and finally make progress on re-implementing functional testing of various scenarios for individual repositories. Thank you for your consideration!

1 0

[neutron] Bug deputy report Aug 14 - Aug 20
by Oleg Bondarev 21 Aug '23

21 Aug '23

Hello Neutron Team, Here's the bug report for the week of Aug 14 - Aug 20: Critical: - https://bugs.launchpad.net/neutron/+bug/2031415 - neutron-tempest-plugin-openvswitch* jobs are failing or timing-out Edit - Fixed by haleyb: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/891550 - https://bugs.launchpad.net/neutron/+bug/2031526 - [ndr] "neutron-tempest-plugin-dynamic-routing" failing - Fixed on os-ken side by j-harbott: https://review.opendev.org/c/openstack/os-ken/+/891658 - waits for os-ken release - https://bugs.launchpad.net/neutron/+bug/2031971 - Rally jobs failing in neutron gate - Invalid - fixed on Rally side by haleyb: https://review.opendev.org/c/openstack/rally-openstack/+/892052 High: - Medium: - https://bugs.launchpad.net/neutron/+bug/2031646 - [sqlalchemy-20] "test_has_alive_neutron_server" failing with SQLAlchemy 2.0 - In progress: https://review.opendev.org/c/openstack/neutron/+/891691 - assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2031656 - Shared networks can be returned as "shared=False" in the API request - Confirmed - assigned to ralonsoh Low: - https://bugs.launchpad.net/neutron/+bug/2031520 - [OVN] Document the router port location (dvr, centralized) depending on network type, load balancing, port forwarding, etc - Triaged - unassigned Thanks, Oleg

1 0

[OSA][NEUTRON]
by Murilo Morais 19 Aug '23

19 Aug '23

Good evening everyone! When using Tenant Network I can't make the instances communicate when they are on different hosts, I believe I'm forgetting to configure something related to network_hosts, but I'm not sure what. It wasn't clear to me exactly the difference between "network_hosts", "network-infra_hosts" and "network-agent_hosts". I'm using the following configuration: openstack_user_config.yml: cidr_networks: container: ... storage: ... used_ips: [...] global_overrides: internal_lb_vip_address: ... external_lb_vip_address: ... management_bridge: br-mgmt no_containers: false provider_networks: - network: container_bridge: br-mgmt container_interface: eth1 container_type: veth ip_from_q: container is_container_address: true type: raw group_binds: - all_containers - hosts - network: container_bridge: br-provider container_type: veth type: vlan range: "100:200" network_interface: "eno2" net_name: vlan group_binds: - neutron_openvswitch_agent - network: container_bridge: "br-flat" container_type: "veth" type: "flat" network_interface: "trunk.103" net_name: "router" group_binds: - neutron_openvswitch_agent - network: container_bridge: br-storage container_interface: eth2 container_type: veth ip_from_q: storage type: raw group_binds: - glance_api - cinder_api - cinder_volume - nova_compute - ceph-mon - ceph-osd shared-infra_hosts: dcn2: ip: ...2 coordination_hosts: dcn2: ip: ...2 repo-infra_hosts: dcn2: ip: ...2 haproxy_hosts: dcn2: ip: ...2 identity_hosts: dcn2: ip: ...2 storage-infra_hosts: dcn2: ip: ...2 storage_hosts: dcn2: ip: ...2 image_hosts: dcn2: ip: ...2 placement-infra_hosts: dcn2: ip: ...2 compute-infra_hosts: dcn2: ip: ...2 dashboard_hosts: dcn2: ip: ...2 network_hosts: dcn2: ip: ...2 compute_hosts: dcn2: ip: ...2 dcn3: ip: ...3 dcn8: ip: ...14 dcn10: ip: ...19 Example to upload the instances: network create network_test subnet create --network network_test --subnet-range 192.168.0.0/24 subnet_test server create --flavor m1.large --image debian-11-genericcloud-amd64-20230601-1398 --network network_test --key-name my_key --use-config-drive debian_test1 server create --flavor m1.large --image debian-11-genericcloud-amd64-20230601-1398 --network network_test --key-name my_key --use-config-drive debian_test2 If for some reason any of them go up on different hosts, even configuring the IP manually, they don't communicate, but the instant they are on the same host the ping starts to work.

2 1

Re: [OpenInfra Foundation Support] Re: Ajuda - Help me! Info.
by Suporte 19 Aug '23

19 Aug '23

Desprezada comunidade!! Poderiam me ajudar? Estou tentando apresentar meu TCC sobre o OpenStak mas estou tendo dificuldades em entender como funciona a ferramenta em relação a múltiplos servidores físicos (cluester). Basicamente queria uma orientação se é possível subir 3 servidores físicos e acessar os recursos unificados em uma aba apenas do Horizon? Amaria um retorno. Atenciosamente | Kind Regards, Mateus Dias Cel.: (11) 96872-8478 E-mail: mateus.dias(a)tektel.com.br Tektel Informática ________________________________ De: Open Infrastructure Foundation <support(a)openstack.zendesk.com> Enviado: segunda-feira, agosto 14, 2023 12:49 PM Para: Suporte <suporte(a)tektel.com.br> Assunto: [OpenInfra Foundation Support] Re: Ajuda - Help me! Info. ##- Please type your reply above this line -## Your request (#46153<https://support.openstack.org/hc/requests/46153>) has been solved. To reopen this request, reply to this email or click the link below: https://support.openstack.org/hc/requests/46153 Allison (OpenInfra Foundation Support) Aug 14, 2023, 10:49 CDT Hi Mateus, Por favor compartilhe esta pergunta na lista de discussão do OpenStack para que a comunidade possa ajudá-lo. https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss Allison This email is a service from OpenInfra Foundation Support. [K20VPL-4E7XM]

2 2

[release] Release countdown for week R-6, Aug 21 - 25
by Thierry Carrez 18 Aug '23

18 Aug '23

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 24th. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (August 31st) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, August 31st. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2023.2 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2023.2 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2023.2 "Bobcat" final release will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 24th, 2023 (R-6 week) Client library freeze: August 31st, 2023 (R-5 week) Bobcat-3 milestone: August 31st, 2023 (R-5 week) Cycle Highlights Due: August 31st, 2023 (R-5 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 18 Aug '23

18 Aug '23

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

1 0

Need assistance
by Gk Gk 18 Aug '23

18 Aug '23

Hi All, We have an openstack ansible setup. We are trying to collect statistics for mysql galera cluster. I am trying to use the following mysql prometheus exporter at https://github.com/prometheus/mysqld_exporter/releases . But when I install the exporter into each of the three mysql galera nodes, I am not finding any mysql client statistics on the metrics url. Also when I checked the mysql databases 'information_schema' and 'performance_schema' , they were empty. How to get the relevant galera stats for the mysql cluster in openstack ? Thanks Kumar

1 0

vPTG October 2023 Team Signup Deadline Approaching!
by Kendall Nelson 17 Aug '23

17 Aug '23

Hello Everyone, Sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 23 to Friday, October 27 2023! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by August 20, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [2] PTG Registration: http://ptg2023.openinfra.dev/

1 1

Call for Mentors & Projects - Boston University Students
by Kendall Nelson 17 Aug '23

17 Aug '23

Hello Everyone! As some of you might know, we have had a working relationship with Boston University once a year where students actively participate in our OpenInfra project communities. The semester in which the Fundamentals of Cloud Computing (the course where we collaborate with them)( is approaching. September 5 is when the course begins and it runs until December 21. The course is a senior/graduate-level class that includes a semester-long capstone-like project, with the projects being proposed and supervised by an industry mentor. The projects are completed in teams of 5-7 students, who are expected to spend 5-8 hours per week on the project over the 13-week term, with presentations to the class every two weeks to evaluate their progress. *So! If you know of a project you would like to propose, please let me know ASAP! The professor would like to have the finalized list of projects to offer students by the first week in September. * Let me know if you have any other questions! -Kendall Nelson

3 3

[kolla] openvswitch-netcontrold image removal
by Michał Nasiadka 17 Aug '23

17 Aug '23

Hello Koalas, The openvswitch-netcontrold image is being dropped, that means in Bobcat release Kolla will not build and publish this image. This image is not supported within kolla-ansible, so it’s not tested and it installs netcontrold outside of the regular kolla venv. It has been used in the past by TripleO - but TripleO will not support Bobcat and beyond. If there is anybody interested in maintaining this image - please come forward posting your comment in the patch [1], otherwise it will be dropped. [1]: https://review.opendev.org/c/openstack/kolla/+/891655 Michal

1 0

[openstack][nova] how check if exist instances were create with AZ or without AZ
by Nguyễn Hữu Khôi 17 Aug '23

17 Aug '23

Hello guys. I need to verify whether an existing instance was created with AZ or without AZ. How can we check on an existing instance? I did not setup default AZ scheduler before. At this time I plan to expand the system by a new AZ. as document If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I am worried about when I migrate instances and they will be free to be moved to other zones. Nguyen Huu Khoi

2 3

VM state wont update on power failure
by Shrey Chauhan 17 Aug '23

17 Aug '23

Hi, Currently I am running xena version of openstack. I am confused about one thing. Running a 3 node cluster. In case of a power failure my vm still shows as active (vm_state = active, power_state = running), even though in KVM they are in shutoff state. When I bring back the node and restart nova the state changes to 'shutoff'. What I am not understanding, is nova managing only local vms power states. Its a 3 node cluster, so nova compute running on other node should change the state in the database, isnt it? Am I missing any nova or linvirt configuration here? Thanks in advance for any kind of help here Thanks and regards, Shrey

2 1

[olso.messaging] RabbitMQ and streams
by Arnaud Morin 16 Aug '23

16 Aug '23

Hey all, Is there any chance that someone already worked on integrating RabbitMQ streams (see [1]) to replace fanouts in oslo rabbitmq driver? We are wondering if this would help lowering the rabbit usage, and maybe increase the rabbit stability? Our deployment is relying a lot on fanouts to delivers messages to computes (mostly neutron, e.g. secgroup update / remote cache population), this is leading to a massive number of messages beeing delivered by seconds. Cheers, Arnaud [1] https://www.rabbitmq.com/streams.html

2 2

[tripleo] [deployment] heat stack error
by Kamil Madac 16 Aug '23

16 Aug '23

Hi Brendan, thanks for the reply. Existing deployment has been done on different set of servers and on centos stream 8, wallaby, so on centos 9 we deployed a different tripleo repos (python3-tripleo-repos-0.1.1-0.20220214194341.cbbdde6.el8.noarch.rpm vs python3-tripleo-repos-0.1.1-0.20230111082402.c73cb0f.el9.noarch.rpm ) for undercloud deployment. Environment yamls were taken from that working deployment. We will try to remove environment yaml from deploy arguments one by one and will try to identify yaml which causes the issue. On Tue, Aug 15, 2023, 22:49 Brendan Shephard <bshephar(a)redhat.com> wrote: > Hey Kamil, > > There will be an error in one of the environment files that you’re > including in your overcloud deploy command. > > You said it’s your first deployment that was already prepared for you. > Does this mean that the environment has already been deployed and you are > trying to make a change now? If that’s the case, then I would check any of > the files that have changed between the initial deployment and what you’re > trying to do now. > > Regards, > Brendan Shephard > Senior Software Engineer > > > > On 15 Aug 2023, at 23:48, Kamil Madac <kamil.madac(a)gmail.com> wrote: > > > > > > Hello, > > I'm trying to deploy openstack wallaby on centos9. Undercloud is > running, but when I run "openstack overcloud deploy" it ends up with error: > > > > 2023-08-14 14:45:51.426 5 ERROR heat.engine.worker > > 2023-08-14 14:45:52.346 5 DEBUG heat.engine.scheduler > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Task create > from TemplateResource "ControllerServiceChain" Stack "keos9" > [18515e00-1d85-4 > > f16-91f7-a88c7553c1ed] running step > /usr/lib/python3.6/site-packages/heat/engine/scheduler.py:207 > > 2023-08-14 14:45:52.352 5 INFO heat.engine.resource > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] CREATE: > TemplateResource "ControllerServiceChain" > [44cce696-f0ef-4975-88e5-5b4e2b69149c] St > > ack "keos9" [18515e00-1d85-4f16-91f7-a88c7553c1ed] > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource Traceback (most > recent call last): > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 916, in > _action_recorder > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 1028, in > _do_action > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield from > self.action_handler_task(action, args=handler_args) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 978, in > action_handler_task > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource done = > check(handler_data) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", > line 408, in check_create_complete > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource return > self._check_status_complete(self.CREATE) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", > line 451, in _check_status_complete > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource action=action) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource > heat.common.exception.ResourceFailure: resources.ControllerServiceChain: > Error in 24 output role_data: The values of the "for_each" argument to > "repeat > > " must be lists or maps > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource > > 2023-08-14 14:45:52.366 5 INFO heat.engine.stack > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Stack CREATE > FAILED (keos9): Resource CREATE failed: resources.ControllerServiceChain: > Error i > > n 24 output role_data: The values of the "for_each" argument to "repeat" > must be lists or maps > > > > > > It is my first tripleo deployment which was already prepared by the > customer, but is not working currently. It is wallaby deployment on centos > stream 9. > > > > Can somebody give me advice on what is the best way to troubleshoot such > issues in heat stacks in tripleo? > > > > Role data has been successfully generated by command: > > > > $ openstack overcloud roles generate -o > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml > Controller Compute > > > > and then used to generate heat templates: > > > > > /var/workdir/tripleo-heat-templates-upstream-wallaby/tools/process-templates.py > \ > > -p /var/workdir/tripleo-heat-templates-upstream-wallaby \ > > -r > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml > \ > > -n > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_network_data.yaml > \ > > -o /var/workdir/generated-tripleo-heat-templates \ > > --safe > > > > > > > > Kamil Madac > > > >

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations Kickoff
by Ian Y. Choi 16 Aug '23

16 Aug '23

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Aug 30, 2023 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2024.1/<Project_Name or "TC">/<email_address> (for example, "candidates/2024.1/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Sep 06, 2023 23:45 UTC through to Sep 20, 2023 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Aug 16, 2023 23:45 UTC PTL + TC nomination ends @ Aug 30, 2023 23:45 UTC TC campaigning starts @ Aug 30, 2023 23:45 UTC TC campaigning ends @ Sep 06, 2023 23:45 UTC PTL + TC elections start @ Sep 06, 2023 23:45 UTC PTL + TC elections end @ Sep 20, 2023 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2023-08-30 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 1

[tripleo] [deployment] heat stack error
by Kamil Madac 15 Aug '23

15 Aug '23

Hello, I'm trying to deploy openstack wallaby on centos9. Undercloud is running, but when I run "openstack overcloud deploy" it ends up with error: 2023-08-14 14:45:51.426 5 ERROR heat.engine.worker 2023-08-14 14:45:52.346 5 DEBUG heat.engine.scheduler [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Task create from TemplateResource "ControllerServiceChain" Stack "keos9" [18515e00-1d85-4 f16-91f7-a88c7553c1ed] running step /usr/lib/python3.6/site-packages/heat/engine/scheduler.py:207 2023-08-14 14:45:52.352 5 INFO heat.engine.resource [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] CREATE: TemplateResource "ControllerServiceChain" [44cce696-f0ef-4975-88e5-5b4e2b69149c] St ack "keos9" [18515e00-1d85-4f16-91f7-a88c7553c1ed] 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource Traceback (most recent call last): 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 916, in _action_recorder 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 1028, in _do_action 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield from self.action_handler_task(action, args=handler_args) 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 978, in action_handler_task 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource done = check(handler_data) 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", line 408, in check_create_complete 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource return self._check_status_complete(self.CREATE) 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", line 451, in _check_status_complete 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource action=action) 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource heat.common.exception.ResourceFailure: resources.ControllerServiceChain: Error in 24 output role_data: The values of the "for_each" argument to "repeat " must be lists or maps 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource 2023-08-14 14:45:52.366 5 INFO heat.engine.stack [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Stack CREATE FAILED (keos9): Resource CREATE failed: resources.ControllerServiceChain: Error i n 24 output role_data: The values of the "for_each" argument to "repeat" must be lists or maps It is my first tripleo deployment which was already prepared by the customer, but is not working currently. It is wallaby deployment on centos stream 9. Can somebody give me advice on what is the best way to troubleshoot such issues in heat stacks in tripleo? Role data has been successfully generated by command: $ openstack overcloud roles generate -o /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml Controller Compute and then used to generate heat templates: /var/workdir/tripleo-heat-templates-upstream-wallaby/tools/process-templates.py \ -p /var/workdir/tripleo-heat-templates-upstream-wallaby \ -r /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml \ -n /var/workdir/tripleo-environment/tripleo-heat-templates/custom_network_data.yaml \ -o /var/workdir/generated-tripleo-heat-templates \ --safe Kamil Madac

2 1

[puppet] Planning deprecation of puppet-qdr
by Takashi Kajinami 15 Aug '23

15 Aug '23

Hello, In Puppet OpenStack projects, we maintain the puppet-qdr module, which manages the QPID Dispatcher Router (aka. qdr). We've been using this module to deploy the qdr service in one of our CentOS jobs so that we can test deployment with the amqp1 messaging driver. However, the amqp1 driver was recently deprecated[1] because of lack of packages built for Ubuntu and Debian. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/861070 While I'm now deprecating support for amqp1 driver in our module and removing usage of the deprecated driver in our CI, I'm also planning to deprecate the puppet-qdr module because we no longer have requirements to manage the qdr service within OpenStack deployments. I'm sending this email to hear any feedback about the module deprecation before we decide its actual timeline. In case you have any thought/concern/etc then please let me know. NOTE: Because the puppet-qdr module has been used by TripleO, my current plan is to deprecate the project instead of retiring it, which keeps its stable branches open. Thank you, Takashi Kajinami

1 0

[magnum] Correct labels / versions to use Kubernetes v1.24 or later versions of v1.23 with Magnum
by Jay Rhine 15 Aug '23

15 Aug '23

Hello! With the latest Antelope release of OpenStack, the release states that it is now compatible with v1.24. I do see there are changes in the underlying templates, etc. that now allow a later v1.24 tag to successfully install. However, just changing the “kube_tag” label is not really enough to fully run a good v1.24. The the tags for the other images (etcd, cinder csi related, etc.) are still at the same versions of the v1.23.3 release that has been around for a while. I see discussions in the comments on https://storyboard.openstack.org/#!/story/2010028 about various labels that were used to get v1.24 to work well in one case. Is there a document anywhere or table, etc. that would have a documented set of labels that would be recommended? Or any other information on running different Kubernetes releases via label updates with Magnum? Thanks for any advice, Jay -- Jay Rhine Rumble Cloud Architect jay.rhine(a)rumble.com

2 4

[neutron] Bug deputy Aug 7 - Aug 13
by Rodolfo Alonso Hernandez 15 Aug '23

15 Aug '23

Hello Neutrinos: This is the bug report from the week Aug 7 - Aug 13. High: * https://bugs.launchpad.net/neutron/+bug/2030718. "Trunk port can not be deleted after removing trunk network". Unassigned. * https://bugs.launchpad.net/neutron/+bug/2030903. "Test failure with SQLAlchemy master branch using TableClause.insert()". Assigned to Miro. * https://bugs.launchpad.net/neutron/+bug/2031184. "OVN Metadata agent tearsdown all namespaces on restart". Assigned to Miro. Medium: * https://bugs.launchpad.net/neutron/+bug/2030747. "Port creation on shared network fails with port_security defined". Unassigned. * https://bugs.launchpad.net/neutron/+bug/2030773. "OVN DB Sync always logs warning messages about updating all router ports". Assigned to Lucas. * https://bugs.launchpad.net/neutron/+bug/2030804. " Missing ip rule causes FIP removal to fail". Assigned to Brian. * https://bugs.launchpad.net/neutron/+bug/2031087. "ICMPv6 Neighbor Advertisement packets from VM's link-local address dropped by OVS". Unassigned. * https://bugs.launchpad.net/neutron/+bug/2031097. "Router causes temporary ARP poisioning/hijack of DVR FIP when migrating/resizing VM". Unassigned. Low: * https://bugs.launchpad.net/neutron/+bug/2030520. "Add support for iPXE over IPv6 in the ML2/OVN DHCP implementation". Assigned to Slawek. * https://bugs.launchpad.net/neutron/+bug/2030735. "HA router state may be set incorrectly in the Neutron DB in some cases". Unassigned. * https://bugs.launchpad.net/neutron/+bug/2030753. "Network components in Neutron". Assigned to Brian. Untriagged: * https://bugs.launchpad.net/neutron/+bug/2030741. "[OVN] Lack of AZs awareness in L3 port scheduler". Unassigned. * https://bugs.launchpad.net/neutron/+bug/2031085. "error in callback mechanism". Unassigned. Regards.

1 0

[kolla-ansible][tooz][devstack] Upgrade path to etcd v3.4
by Jan Gutter 15 Aug '23

15 Aug '23

Hi folks, etcd maintains two stable branches [1], at the moment these appear to be the v3.4 and v3.5 series. etcd does not support skip-version updates without dataloss[2] out of the box, operators are encouraged to do online updates. I took a quick sample of some etcd versions: * devstack currently uses etcd v3.3.12 (at time of writing) [3] * kolla uses etcd v3.3.27 [4] * tripleo uses rdo etcd: it appears they're already on 3.4.14 [5] * upstream etcd is at 3.4.27 and 3.5.9 [6] Now, the bad news: The client side endpoints of etcd is changing from `v3alpha` to `v3`, with a `v3beta` step added to ensure maximum confusion [7] tooz, for example, currently defaults to `v3alpha` for the recommended etcd3gw backend [8], but it's configurable in the client side by passing an extra option to the backend url. So just updating etcd from 3.3 to 3.4 usually breaks things until a couple of orchestration updates are made. It seems providing a smooth upgrade path would require coordination between orchestration, services that depend on etcd as a backend, and a couple of middleware libraries. The lack of a skip-version upgrade support means it's probably also better to do this sooner rather than later. 3.4 is already late in its release cycle and due to go out of maintenance soon. Options: * upgrade to 3.4 and use `v3` endpoint everywhere - fix forward? * try to detect endpoints in middleware (etcd3gw) somehow? * ask ChatGPT how to farm goats Links (not permalinks!): [1]: https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/b… [2]: https://etcd.io/docs/v3.3/upgrades/upgrade_3_4/ [3]: https://opendev.org/openstack/devstack/src/branch/master/stackrc#L723 [4]: https://opendev.org/openstack/kolla/src/branch/master/docker/etcd/Dockerfil… [5]: https://review.rdoproject.org/r/plugins/gitiles/rdoinfo/+/master/buildsys-t… [6]: https://github.com/etcd-io/etcd/releases/ [7]: https://etcd.io/docs/v3.5/dev-guide/api_grpc_gateway/ [8]: https://opendev.org/openstack/tooz/src/branch/master/tooz/drivers/etcd3gw.p…

2 2

[tc] Technical Committee next weekly meeting Tomorrow on August 15, 2023
by Nikolla, Kristi 14 Aug '23

14 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, Aug 15, 2023 at 1800 UTC on #openstack-tc on OFTC IRC. Please propose items to the agenda by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting As of now, the agenda for tomorrow's meeting is • Roll call • Follow up on past action items • rosmaita to review guidelines patch and poke at automating it • Gate health check • Testing runtime for 2024.1 release • https://review.opendev.org/c/openstack/governance/+/891225 • User survey question updates by Aug 18 • https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034589.ht… • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open • https://review.opendev.org/c/openstack/project-team-guide/+/843457 • https://review.opendev.org/c/openstack/governance/+/888771 Thank you, Kristi Nikolla

1 0

LDAP failover fails
by Albert Braden 14 Aug '23

14 Aug '23

We are experiencing the LDAP failover issue described in [1]. Redhat’s solution is to not bother fixing the bug, and to tell customers to put the LDAP server behind a load-balancer. According to Redhat, that is not a good solution for FreeIPA, as explained in [2] and further elucidated in the blog post [3] that it references. I see that the community has a bug open for this [4] and the bug is being worked on here [5] but there has been no activity since 10/22. What is the status of this bugfix? Does it just need someone to review and merge it, or is there more work to be done? How are other FreeIPA users working around this problem? [1] https://bugzilla.redhat.com/show_bug.cgi?id=2024602#c3 [2] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… [3] http://ssimo.org/blog/id_019.html [4] https://bugs.launchpad.net/keystone/+bug/1953622 [5] https://review.opendev.org/c/openstack/keystone/+/821086

2 4

[openstack][neutron] it is good if we set fixed ip and set ip in instance netplan also
by Nguyễn Hữu Khôi 14 Aug '23

14 Aug '23

Hello guys. Sometimes I see that my instances won't get IP from Neutron DHCP Agent. Is it good if we set a fixed port for instance and set a static ip in the instance's netplan configuration also? Nguyen Huu Khoi

5 10

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Season
by Ian Y. Choi 12 Aug '23

12 Aug '23

Election details: https://governance.openstack.org/election/ The nomination period officially begins Aug 16, 2023 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 4 candidates stepping forward the available TC positionss. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[release] Release countdown for week R-7, Aug 14-18
by Elõd Illés 11 Aug '23

11 Aug '23

Development Focus ----------------- We are entering the last weeks of the 2023.2 Bobcat development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 17th, 2023. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 24th, 2023). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (August 31st, 2023) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, August 31st, 2023. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 14th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 28th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (August 31st, 2023). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: August 17th, 2023 (R-7 week) Non-client library freeze: August 24th, 2023 (R-6 week) Client library freeze: August 31st, 2023 (R-5 week) Bobcat-3 milestone: August 31st, 2023 (R-5 week) Final 2023.2 Bobcat release: October 4th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[OSA] CEPH libvirt secrets
by Murilo Morais 11 Aug '23

11 Aug '23

Good evening everyone! Guys, I'm having trouble adding a second CEPH cluster for Nova/Cincer to consume. I'm using the following configuration: cinder_backends: ceph1: volume_driver: cinder.volume.drivers.rbd.RBDDriver rbd_pool: ceph1_vol rbd_ceph_conf: /etc/ceph/ceph1.conf rbd_store_chunk_size: 8 volume_backend_name: ceph1 rbd_user: ceph1_vol rbd_secret_uuid: "{{ cinder_ceph_client_uuid }}" report_discard_supported: true ceph2: volume_driver: cinder.volume.drivers.rbd.RBDDriver rbd_pool: ceph2_vol rbd_ceph_conf: /etc/ceph/ceph2.conf rbd_store_chunk_size: 8 volume_backend_name: ceph2 rbd_user: ceph2_vol rbd_secret_uuid: "{{ cinder_ceph_client_uuid2 }}" report_discard_supported: true ceph_extra_confs: - src: /etc/openstack_deploy/ceph/ceph1.conf dest: /etc/ceph/ceph1.conf client_name: ceph1_vol keyring_src: /etc/openstack_deploy/ceph/ceph1_vol.keyring keyring_dest: /etc/ceph/ceph1.client.ceph1_vol.keyring secret_uuid: '{{ cinder_ceph_client_uuid }}' - src: /etc/openstack_deploy/ceph/ceph2.conf dest: /etc/ceph/ceph2.conf client_name: ceph2_vol keyring_src: /etc/openstack_deploy/ceph/ceph2_vol.keyring keyring_dest: /etc/ceph/ceph2.client.ceph2_vol.keyring secret_uuid: '{{ cinder_ceph_client_uuid2 }}' But when executing the `virsh secret-list` command it only shows the UUID of "cinder_ceph_client_uuid". Both "cinder_ceph_client_uuid" and "cinder_ceph_client_uuid2" are defined in "user_secrets.yml". I have a slight impression that I didn't configure something, but I don't know what, because I didn't find anything else to be done, according to the documentation [1], or it went unnoticed by me. [1] https://docs.openstack.org/openstack-ansible-ceph_client/latest/configure-c… Thanks in advance!

2 5

[nova] VM gets stuck in BUILD status after SQL DBConnectionError error in nova-conductor
by Pavlo Bychikhin 10 Aug '23

10 Aug '23

Hi all, Sometimes when I create a bunch of VMs (40) at once, one of them gets stuck in BUILD status. From logs I found that this happens due to SQL error in nova-conductor: DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query'). There is an attempt to schedule the VM: .... nova-scheduler"sending reply msg_id: 593a990393d5439580870d8412ab49f3 reply queue: reply_a0992fe3f9924cb1b45bfa8b27057580 time elapsed: 1.49198414385s" And right after that the SQL error happens: nova-conductor "Exception during message handling" "DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT instance_id_mappings.created_at AS instance_id_mappings_created ......" And after that the VM stays in BUILD status forever. My setup is Galera cluster behind Haproxy load balancer. I checked various DB server timeouts - they are totally fine. Ones in MySQL correspond ones in nova.conf and haproxy.cfg. In the MySQL logs there are messages like: [Warning] Aborted connection 17798924 to db: 'nova' user: 'nova' host: 'xxx.xxx.xxx.xxx' (Got an error reading communication packets) In the Haproxy logs there are messages like: <134>2023-08-05T08:44:34.325338+00:00 dbs01 haproxy[1275]: xxx.xxx.xxx.xxx:44880 [05/Aug/2023:08:42:44.441] mysql_cluster_nova_conn mysql_cluster_nova_conn/dbs02 1/0/109884 11438 CD 4125/1884/1884/1884/0 0/0 "CD" means "The client unexpectedly aborted during data transfer" So the Haproxy believes the connection is closed at client side. I checked the network interface counters - they are also fine (no errors, drops etc). I found some discussions in the Internet. People say, when the DB is behind load balancer - such 'Lost connection' events are pretty normal and not harmful to the Openstack components. I would agree with them. I think, Nova should be able to recover from accidental DB connection lost. Or to set the ERROR status to the VM if that's impossible. My Nova version is 17.0.13 (Queens). May be someone encountered such issue and knows how to fix? Or that's a bug in Nova and I need to upgrade it to a more recent version? Thanks in advance ---- Best regards, Pavlo Bychikhin

1 0

Kayobe VLAN & bond configuration
by Stefan Pinter 10 Aug '23

10 Aug '23

Hi! I am trying to set up Openstack with Kayobe and right now I’m very stuck at VLAN configuration with LACP bonds on my two network nodes. Last Friday the network even came to a hold when activating Openvswitch because it started a broadcast storm or something in the whole company even though I have 2 VLANs just for this project. So I am trying to do it like this: #bond configuration dummy_net_interface: bond0 dummy_net_bootproto: static dummy_net_bond_slaves: - eno12399np0 - eno12409np1 dummy_net_bond_mode: 802.3ad dummy_net_bond_miimon: 100 dummy_net_bond_lacp_rate: fast #configure mgmt interface mgmt_net_interface: brmgmt mgmt_net_bridge_ports: - bond0 #external net work interface and bridge configuration #ext_net_bridge_ports: ext_net_interface: "brbond{{ ext_net_vlan }}" ext_net_bridge_ports: - "bond0.{{ ext_net_vlan }}" Part of my networks.yml … external_net_names: - ext_net … ext_net_cidr: 172.31.246.0/24 ext_net_no_ip: true ext_net_vlan: 705 Last time this worked, when I ran a “kayobe overcloud host configure” (the node had network connection) but then “kayobe overcloud service deploy” killed the network when it started the Openvswitch. Now (today) this configuration doesn’t even allow to reach the network/(to be)neutron nodes (they lose network connection) when the playbook restarts system-networkd. It already creates OVS PHY bridges and lots of stuff even though I ran “overcloud service destroy” before that. Should it do that at this stage? Are there any examples to set up a network node with bonds and vlans and external neutron networks out there? Any suggestions? Thank you 😊 Kind regards Stefan ________________________________ BearingPoint GmbH Sitz: Wien Firmenbuchgericht: Handelsgericht Wien Firmenbuchnummer: FN 175524z The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

1 0

Kayobe VLAN & bond configuration
by BPt-FM BBS IaaS 10 Aug '23

10 Aug '23

Hi! I am trying to set up Openstack with Kayobe and right now I’m very stuck at VLAN configuration with LACP bonds on my two network nodes. Last Friday the network even came to a hold when activating Openvswitch because it started a broadcast storm or something in the whole company even though I have 2 VLANs just for this project. So I am trying to do it like this: #bond configuration dummy_net_interface: bond0 dummy_net_bootproto: static dummy_net_bond_slaves: - eno12399np0 - eno12409np1 dummy_net_bond_mode: 802.3ad dummy_net_bond_miimon: 100 dummy_net_bond_lacp_rate: fast #configure mgmt interface mgmt_net_interface: brmgmt mgmt_net_bridge_ports: - bond0 #external net work interface and bridge configuration #ext_net_bridge_ports: ext_net_interface: "brbond{{ ext_net_vlan }}" ext_net_bridge_ports: - "bond0.{{ ext_net_vlan }}" Part of my networks.yml … external_net_names: - ext_net … ext_net_cidr: 172.31.246.0/24 ext_net_no_ip: true ext_net_vlan: 705 Last time this worked, when I ran a “kayobe overcloud host configure” (the node had network connection) but then “kayobe overcloud service deploy” killed the network when it started the Openvswitch. Now (today) this configuration doesn’t even allow to reach the network/(to be)neutron nodes (they lose network connection) when the playbook restarts system-networkd. It already creates OVS PHY bridges and lots of stuff even though I ran “overcloud service destroy” before that. Should it do that at this stage? Are there any examples to set up a network node with bonds and vlans and external neutron networks out there? Any suggestions? Thank you 😊 The information in this email is confidential and may be legally privileged. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.

1 0

Exploring the Intersection of AI and Open Source: Aug. 10 at 15 UTC
by Kristin Barrientos 09 Aug '23

09 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: If you stand at the intersection of AI and open source you’ll find a very active discussion around how each concept can apply to the other but you’ll find few definitive answers. This panel of open source community leaders will discuss the current state of AI & open source, the collaborative efforts underway to improve global understanding of this emerging use case and how open source community members can participate in solving today’s unanswered questions. Date and time: Aug 10, 2023 at 10:00 CST (15:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=LLujjvEIbPk LinkedIn: https://www.linkedin.com/events/7094342351971598337/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Mark Collier, Pamela Chestek, Stefano Maffulli, Armstrong Foundjem, Stephen O'Grady Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[operators][swift][s3][ceph] interoperability s3/swift protocol using radosgw
by Benedikt Trefzer 09 Aug '23

09 Aug '23

Hi Openstack list I'm stuck with a problem: We implemented object storage using ceph radosgw, using keystone authentication and rgw multi-tenancy. So far so good. If I create a container named 'test-swift' using swift protocol, radosgw-admin shows me a bucket created as: "*\/test-swift" (* is the uuid of the opensstack project) which seems to be the correct behaviour. If I create a bucket with s3cmd named 'test-s3', radosgw-admin shows the bucket as: "test-s3" which is not the expected behaviour since this is not multi tenancy ! Can anyone point me to the right direction to solve this ? Could the use of v2 signatures for S3 be a problem ? Further information: Ceph version: Jewel Openstack keystone: train Access to rgw through Apache fcgi (sitting behind haproxy nodes) Thanks for all the hints Benedikt PS: - I know that Jewel and train are old versions, but ... - I know that S3/Swift protocols are not fully supported using rgw

1 0

Cinder Bug Report 2023-08-09 - No new Bugs This Week!
by Rajat Dhasmana 09 Aug '23

09 Aug '23

1 0

[skyline] Username or password is incorrect
by Satish Patel 09 Aug '23

09 Aug '23

Folks, Try to install skyline UI to replace horizon using doc: https://docs.openstack.org/skyline-apiserver/latest/install/docker-install-… Everything went well and I got a login page on http://x.x.x.x:9999 also it pulled Region/Domains. When I am trying to login with my account, I get an error: Username or Password is incorrect. I am using sqlite DB for skyline as per documents. No errors in logs command $ docker logs skyline When I use Chrome Developer Tools then it was indicating an error in these URLs. http://openstack.example.com:9999/api/openstack/skyline/api/v1/profile http://openstack.example.com:9999/api/openstack/skyline/api/v1/policies 401 Unauthorized ( {"detail":"no such table: revoked_token"} ) Find attached screenshot

2 2

[cinder] prevent change volume type from different AZ
by Nguyễn Hữu Khôi 09 Aug '23

09 Aug '23

Hello guys. I have 2 AZ and 1 volume backend on each AZ. My goal is when 1 volume was created from the AZ then user cannot change it to another volume type on a different AZ. Thank you. Nguyen Huu Khoi

2 2

[neutron] User survey Neutron related questions
by Slawek Kaplonski 09 Aug '23

09 Aug '23

Hi, As we talked on the Neutron team meeting yesterday [1] I prepared etherpad with Neutron related questions and possible answers from the User Survey [2]. I already added there some of my comments. Please check it and comment on it too. We can then discuss it during next week's Neutron team meeting and finally maybe send some proposals to change something there. [1] https://meetings.opendev.org/meetings/networking/2023/networking.2023-08-08… [2] https://etherpad.opendev.org/p/neutron-user-survey-questions-2023 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[glance][ops] Problems snapshotting a VM: image gets deleted
by Massimo Sgaravatto 09 Aug '23

09 Aug '23

I have problems snapshotting a particular VM. This is what happens: [root@cld-ctrl-01 ~]# nova image-create --show --poll 8cfd9323-f9d8-41f8-b607-41597d9c79e9 ns3-new-snap-2023-08-09-2 Server snapshotting... 0% completeERROR (NotFound): No image found with ID 133d4978-1de3-4cef-8804-8b0f07b12e4e<br /><br /> (HTTP 404) [root@cld-ctrl-01 ~]# According to the logs [*], it looks like the snapshot is for some reason deleted, but I don't understand what the problem is Any hints ? Thanks, Massimo [*] 2023-08-09 08:35:05.683 5507 INFO eventlet.wsgi.server [req-b0908999-5e95-4520-ae5a-614c503e91e9 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 192.168.60.105\ ,192.168.60.232 - - [09/Aug/2023 08:35:05] "POST /v2/images/133d4978-1de3-4cef-8804-8b0f07b12e4e/members HTTP/1.1" 200 424 0.037093 2023-08-09 08:35:05.689 5506 INFO eventlet.wsgi.server [-] 192.168.60.234 - - [09/Aug/2023 08:35:05] "OPTIONS /versions HTTP/1.0" 200 1781 0.001015 2023-08-09 08:35:05.690 5507 INFO eventlet.wsgi.server [req-b0908999-5e95-4520-ae5a-614c503e91e9 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 192.168.60.105\ ,192.168.60.232 - - [09/Aug/2023 08:35:05] "GET /v2/schemas/member HTTP/1.1" 200 872 0.003611 2023-08-09 08:35:05.690 5501 INFO eventlet.wsgi.server [-] 192.168.60.234 - - [09/Aug/2023 08:35:05] "OPTIONS /versions HTTP/1.0" 200 1781 0.000932 2023-08-09 08:35:05.770 5500 INFO eventlet.wsgi.server [req-4146429a-27a6-4ac9-a3f7-4534c32c6dd0 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 193.206.210.24\ 0,192.168.60.232 - - [09/Aug/2023 08:35:05] "GET /v2/images/133d4978-1de3-4cef-8804-8b0f07b12e4e HTTP/1.1" 200 1456 0.012723 2023-08-09 08:35:05.812 5500 INFO eventlet.wsgi.server [-] 192.168.60.234 - - [09/Aug/2023 08:35:05] "OPTIONS /versions HTTP/1.0" 200 1781 0.000906 2023-08-09 08:35:05.812 5506 INFO eventlet.wsgi.server [-] 192.168.60.234 - - [09/Aug/2023 08:35:05] "OPTIONS /versions HTTP/1.0" 200 1781 0.001003 2023-08-09 08:35:05.862 5503 INFO eventlet.wsgi.server [req-b0908999-5e95-4520-ae5a-614c503e91e9 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 192.168.60.159\ ,192.168.60.232 - - [09/Aug/2023 08:35:05] "GET /v2/images/133d4978-1de3-4cef-8804-8b0f07b12e4e HTTP/1.1" 200 1456 0.012832 2023-08-09 08:35:05.868 5506 INFO eventlet.wsgi.server [req-b0908999-5e95-4520-ae5a-614c503e91e9 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 192.168.60.159\ ,192.168.60.232 - - [09/Aug/2023 08:35:05] "GET /v2/schemas/image HTTP/1.1" 200 6278 0.002641 2023-08-09 08:35:06.014 5500 INFO eventlet.wsgi.server [req-b0908999-5e95-4520-ae5a-614c503e91e9 a1f915a7a36c471d87d6702255016df4 beaeede3841b47efb6b665a1a667e5b1 - default default] 192.168.60.159\ ,192.168.60.232 - - [09/Aug/2023 08:35:06] "DELETE /v2/images/133d4978-1de3-4cef-8804-8b0f07b12e4e HTTP/1.1" 204 208 0.140910

2 2

[openstack][neutron] set a fixed ip for router gateway
by Nguyễn Hữu Khôi 09 Aug '23

09 Aug '23

Hello guys. I am curious why we can not set a fixed ip for router gateway. [image: image.png] Although I see these codes were merged many years ago. https://review.opendev.org/c/openstack/neutron/+/83664 Nguyen Huu Khoi

2 2

Why service use UTC in db and log use local timezone
by kaqiu pi 08 Aug '23

08 Aug '23

Hello, I have a openstack cluster. And the local time of server is different from UTC. I saw that the log date of openstack service is local time. But when I use the command line to query the openstack service status, time zone is UTC. Such as `opentack compute service list`, "Update At" is UTC. In the email archive[1], I saw that there was a discussion earlier: > i would guess it a deliberate design descisn to only store data information in utc format and leave it to the clinets to convert to local timezones if desired But at that time it was just a guess, I would like to ask if this is the meaning of the original design, why the service use UTC instead of local time? I would appreciate any kind of guidance or help. Best wishes. [1] https://lists.openstack.org/pipermail/openstack-discuss/2021-June/022857.ht…

2 1

[RALLY] Running Rally tasks and Tempest tests in multi-user context
by Taltavull Jean-François 08 Aug '23

08 Aug '23

Hi openstack-discuss, I'm currently using Rally v3.4.0 to test our OpenStack Zed platform. Rally has been deployed on a dedicated virtual machine and Rally tasks and Tempest tests, launched on this machine by Rundeck, run pretty well. Now, I wish every OpenStack team member could launch whatever scenario or test he wants, when he wants, for example after having applied a service configuration change on the staging platform. And a question is arising: can several users launch different Rally scenarios or Tempest tests at the same time, from their own Linux account/environment, using the same Rally, the one which is deployed on the dedicated machine ? Thanks and best regards, Jean-Francois

2 2

[neutron] Bug Deputy Report July 31 - August 06
by Lucas Alvares Gomes 08 Aug '23

08 Aug '23

Hi, This is the Neutron bug report from July 31st to August 6th. *High:* * https://bugs.launchpad.net/neutron/+bug/2029722 - Routed subnets cannot use sna -Assigned to: Alban PRATS *Medium:* * https://bugs.launchpad.net/neutron/+bug/2029335 - [centos-9-stream] jobs fails as nova-compute stuck at libvirt connect since systemd-252-16.el9 - Assigned to: Yatin * https://bugs.launchpad.net/neutron/+bug/2029419 - Add Tempest scenario to validate NIC teaming - Unassigned *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2029420 - ovdb connections fail. out-of-sync with ovs library - Unassigned * https://bugs.launchpad.net/neutron/+bug/2030294 - OVN: garbled DNS responses when edns is being used - Unassigned * https://bugs.launchpad.net/neutron/+bug/2030295 - OVN: no DNS responses are generated for TCP queries - Unassigned Cheers, Lucas

1 0

[tc] Technical Committee next weekly meeting Today on August 8, 2023
by Nikolla, Kristi 08 Aug '23

08 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held Today, Tuesday, August 8, 2023 at 1800 UTC on #openstack-tc on OFTC IRC. Please find the agenda below: • Roll call • Follow up on past action items • rosmaita to review guidelines patch and poke at automating it • Gate health check • Unmaintained status replaces Extended Maintenance • https://review.opendev.org/c/openstack/governance/+/888771 • User survey question updates by Aug 18 • https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034589.ht… • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[openstack][nova] Slow provision 1 instance .
by Ha Noi 08 Aug '23

08 Aug '23

Hi everyone, We have a openstack with one region and more than 100 compute nodes. We are using ceph for block storage. I don't know why my instance was provisioned too slow: more than 1 minutes. Nova compute log: Took 56.47 seconds to build instance. So I would like to optimize and speed up instance build time. Thanks and Best Regards

2 7

[tacker] Cancelling IRC meetings
by Yasufumi Ogawa 07 Aug '23

07 Aug '23

Hi team, I'd like to skip the next two weekly meetings becaseu I'm not available today, nothing new issues from the last week and next week is a week holiday for many of us. Thanks, Yasufumi

1 0

instance memory save and restore
by Tony Liu 07 Aug '23

07 Aug '23

Hi, VMWare vCenter has such feature to snapshot/save instance memory along with disk. Then instance can be reverted to that snapshot later when needed. OpenStack doesn't seem to support it. Any plan to work on that? Actually, I'm looking for the motivation/requirement to for that feature. Typically, we snapshot/backup storage, then restore the storage and restart/reboot the host/instance. Would that be sufficient? I think there will be a chance of inconsistence between memory and storage. That's why we may need to save the state of both memory and storage. Does that make sense? Any opinions is welcome. Thanks! Tony

2 1

[horizon][yoga][kolla-ansible][domain] list project created by a specific user
by James Leong 07 Aug '23

07 Aug '23

Hi all, Is it possible to list only projects that are created by the respective user. For example, user A created project 1, and project 2. I do not want user B to be able to view project 1, and project 2 other than the project created by user B. Apart from that, is there a way to allow users to switch between default domain to another domain via openstack dashboard (horizon)? Best, James

1 0

[horizon][keystone][kolla-ansible][domain][policies][yoga] Allow user to access different domain
by James Leong 06 Aug '23

06 Aug '23

Hi everyone, I am curious if a user from the default domain can access a different domain. For instance, the cloud admin created multiple domains and used the below command to add a user to a new domain other than the default one. "openstack role add --user test --domain test member" As a user with a member role, I am not able to see the list of the domains associated with the user account. I will only be able to see it on the admin side. Can member roles be allowed to view domains they are in? Best, James

1 0

[openstack][nova] Slow provision 1 instance . (Ha Noi)
by Karl Kloppenborg 05 Aug '23

05 Aug '23

Hi Han, Can you give us some more information? Where is the delay? Is it in volume building, allocation selection? Spawning? Etc. The VM instantiation process has a number of us processes that can all slow down at scale for different reasons. I doubt it is the actual spawning or allocation stage, likely a ceph/cinder building stage, especially if it’s copying data via glance to a volume. Thanks, Karl.

1 0

How to add Audit middleware in placement-api
by Pureewat Kaewpoi 04 Aug '23

04 Aug '23

Dear Community ! According to this document (https://docs.openstack.org/keystonemiddleware/yoga/audit.html) It say, I have to add "audit" middleware into api-paste.ini file. But placement api It not have api-paste.ini and It looks like placement calling middleware in this file (https://opendev.org/openstack/placement/src/branch/master/placement/deploy.…) As I understand I have to change some code to use audit middleware ? Or Just create api-paste.ini for placement-api and config wsgi to use this paste ? Best Regards, Pureewat

1 0

[openvswitch][neutron] firewall_driver openvswitch in production
by Satish Patel 04 Aug '23

04 Aug '23

Folks, Who is running the OVS firewall driver (firewall_driver = openvswitch) in production and are there any issues with running it which I may not be aware of? We are not yet ready for OVN deployments so have to stick with OVS. LinuxBridge is at the end of its life trying to get rid of any dependency. [securitygroup] firewall_driver = openvswitch

2 2

[placement][sdk] How to debug HTTP 502 errors with placement in DevStack?
by Stephen Finucane 03 Aug '23

03 Aug '23

We recently merged support for placement traits in openstacksdk. Since then, we've seen an uptick in failures of various functional jobs [1]. The failure is always the same test: openstack.tests.functional.placement.v1.test_trait.TestTrait.test_resource_pr ovider_inventory That test simply creates a new, custom trait and then attempts to list all traits, show an individual trait, and finally delete the trait. The failure occurs during the first step, creation of the custom trait: openstack.exceptions.HttpException: HttpException: 502: Server Error for url: https://10.209.100.9/placement/traits/CUSTOM_A982E0BA1C2B4D08BFD6D2594C6783… , Bad Gateway: response from an upstream server.: The proxy server received an invalid: Apache/2.4.52 (Ubuntu) Server at 10.209.100.9 Port 80: Additionally, a 201 Created: 502 Bad Gateway: error was encountered while trying to use an ErrorDocument to handle the request. I've looked through the various job artefacts and haven't found any smoking guns. I can see placement receive and reply to the request so it would seem something is happening in between. *Fortunately*, this is also reproducible locally against a standard devstack deployment by running the following in the openstacksdk repo: OS_TEST_TIMEOUT=60 tox -e functional-py310 -- \ -n openstack/tests/functional/placement/v1/test_trait.py \ --until-failure Does anyone have any insight into what could be causing this issue and have suggestions for how we might go about debugging it? As things I haven't a clue 😔 Cheers, Stephen [1] https://zuul.opendev.org/t/openstack/builds?job_name=openstacksdk-functiona…

2 2

[magnum][openstack-ansible][k8s] kube_masters CREATE_FAILED
by Satish Patel 03 Aug '23

03 Aug '23

Folks, I am running the Xena release and fedora-coreos-31.X image. My cluster is always throwing an error kube_masters CREATE_FAILED. This is my template: openstack coe cluster template create --coe kubernetes --image "fedora-coreos-35.20220116" --flavor gen.medium --master-flavor gen.medium --docker-storage-driver overlay2 --keypair jmp1-key --external-network net_eng_vlan_39 --network-driver flannel --dns-nameserver 8.8.8.8 --labels="container_runtime=containerd,cinder_csi_enabled=false" --labels kube_tag=v1.21.11-rancher1,hyperkube_prefix=docker.io/rancher/ k8s-new-template-31 Command to create cluster: openstack coe cluster create --cluster-template k8s-new-template-31 --master-count 1 --node-count 2 --keypair jmp1-key mycluster31 Here is the output of heat stack [root@ostack-eng-osa images]# heat resource-list mycluster31-bw5yi3lzkw45 WARNING (shell) "heat resource-list" is deprecated, please use "openstack stack resource list" instead +-------------------------------+--------------------------------------+----------------------------------------------------------------------------------------------------------------+-----------------+----------------------+ | resource_name | physical_resource_id | resource_type | resource_status | updated_time | +-------------------------------+--------------------------------------+----------------------------------------------------------------------------------------------------------------+-----------------+----------------------+ | api_address_floating_switch | | Magnum::FloatingIPAddressSwitcher | INIT_COMPLETE | 2023-08-01T20:55:49Z | | api_address_lb_switch | | Magnum::ApiGatewaySwitcher | INIT_COMPLETE | 2023-08-01T20:55:49Z | | api_lb | 99e0f887-fbe2-4b2f-b3a1-b1834c9a21c2 | file:///openstack/venvs/magnum-24.5.1/lib/python3.8/site-packages/magnum/drivers/common/templates/lb_api.yaml | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | etcd_address_lb_switch | | Magnum::ApiGatewaySwitcher | INIT_COMPLETE | 2023-08-01T20:55:49Z | | etcd_lb | d4ba15f3-8862-4f2b-a2cf-53eafd36d286 | file:///openstack/venvs/magnum-24.5.1/lib/python3.8/site-packages/magnum/drivers/common/templates/lb_etcd.yaml | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | kube_cluster_config | | OS::Heat::SoftwareConfig | INIT_COMPLETE | 2023-08-01T20:55:49Z | | kube_cluster_deploy | | OS::Heat::SoftwareDeployment | INIT_COMPLETE | 2023-08-01T20:55:49Z | | kube_masters | 9ac8fc3e-a7d8-4eca-90c6-f66a8e0c43f0 | OS::Heat::ResourceGroup | CREATE_FAILED | 2023-08-01T20:55:49Z | | kube_minions | | OS::Heat::ResourceGroup | INIT_COMPLETE | 2023-08-01T20:55:49Z | | master_nodes_server_group | 19c9b300-f655-4db4-b03e-ea1479c541db | OS::Nova::ServerGroup | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | network | a908f229-fe8f-4ab8-b245-e8cf90c1b233 | file:///openstack/venvs/magnum-24.5.1/lib/python3.8/site-packages/magnum/drivers/common/templates/network.yaml | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | secgroup_kube_master | 79e6b233-1a18-48c4-8a4f-766819eb945f | OS::Neutron::SecurityGroup | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | secgroup_kube_minion | 2a908ffb-15bf-45c5-adad-6930b0313e94 | OS::Neutron::SecurityGroup | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | secgroup_rule_tcp_kube_minion | 95779e79-a8bc-4ed4-b035-fc21758bd241 | OS::Neutron::SecurityGroupRule | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | secgroup_rule_udp_kube_minion | 2a630b3e-51ca-4504-9013-353cbe7c581b | OS::Neutron::SecurityGroupRule | CREATE_COMPLETE | 2023-08-01T20:55:49Z | | worker_nodes_server_group | d14b0630-95fa-46dc-81e3-2f90e62c7943 | OS::Nova::ServerGroup | CREATE_COMPLETE | 2023-08-01T20:55:49Z | +-------------------------------+--------------------------------------+----------------------------------------------------------------------------------------------------------------+-----------------+----------------------+ I can ssh into an instance but am not sure what logs I should be chasing to find the proper issue. Any kind of help appreciated

3 5

[cloudkitty] InfluxDB version 1.8.10
by Kaster, Jörn 03 Aug '23

03 Aug '23

Hello together, we have deployed OpenStack with the standard kolla-ansible toolset. Within is included the rating component cloudkitty with prometheus and InfluxDB. The InfluxDB version that is deployed with kolla-ansible is 1.8.10 [2021-10-11]. The actual newest InfluxDB version is 2.7.1 [2023-04-28]. Are there any plans to migrate in the near future to the newest version? I couldn't find any informations on InfluxDB Sites if the 1.8 branch is supported anymore. It seems not like described in Point 2.4 of [1]. [1] https://www.influxdata.com/legal/support-policy/ [https://images.ctfassets.net/o7xu9whrs0u9/fn7Q8NJ8ctkA2FOf8DPjW/e2c782d7edb…]<https://www.influxdata.com/legal/support-policy/> Support Policy | InfluxData<https://www.influxdata.com/legal/support-policy/> InfluxData Support Program describes InfluxData’s current support offerings and support policies for the Software and Subscription Services. www.influxdata.com

2 3

[ptl][osc][sdk] openstackclient/sdk "service cores"
by Brian Rosmaita 02 Aug '23

02 Aug '23

Hello Stackers, At the Vancouver 2023 Forum, Artem and Stephen proposed adding individual OpenStack project cores as "service cores" for the python-openstackclient and openstacksdk projects.[0] This will give -2..+2 review powers to subject matter experts for osc/sdk changes affecting particular openstack components, and hopefully speed up the reviewing process. The idea is that service-cores will verify that the cli/sdk code is correct for their particular openstack component, and the "regular" osc/sdk core team (which will have sole +W power) will ensure that changes preserve consistency across the entire osc/sdk. You can give your core team permissions to act as osc/sdk "service cores" by proposing a patch to project-config. You can use the following patch as an example: https://review.opendev.org/c/openstack/project-config/+/890346 cheers, brian [0] https://etherpad.opendev.org/p/oscsdk-vancouver-forum-2023

1 0

[SDK][OSC] Core team cleanup
by Stephen Finucane 02 Aug '23

02 Aug '23

👋️ The openstacksdk-core Gerrit team contains a number of individuals who have not contributed to SDK in at over a year. * Adrian Turjak * Dean Troyer * Doug Hellmann * Monty Taylor * Paul Belanger In addition, the python-openstackclient-core Gerrit group contains the following individuals who have not contributed to OSC in the same time period. * Dean Troyer * Doug Hellmann * Matt Riedemann * Monty Taylor So that I don't have to remember to follow-up on this in a week's time, I have gone ahead and preemptively removed these individuals from the respective groups. If you are on either list and wish to remain in the groups, please reach out to me and I'll re-add you promptly :) Alternatively, assuming these folks are indeed no longer working on SDK or OpenStack at large, thank you all for your historical contributions. As is customary with emeritus reviewers, if at a future date you wish to resume OpenStack contributions we'd be happy to re-add you to the openstacksdk-core group. Thanks, Stephen

2 1

Cinder Bug Report 2023-08-02
by Rajat Dhasmana 02 Aug '23

02 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Low - RBD migrate_volume code optimization <https://bugs.launchpad.net/cinder/+bug/2028793> - Status: Recently reported, no comments or fix proposed - NetApp ONTAP - Error on failover-host with REST API <https://bugs.launchpad.net/cinder/+bug/2028857> - Status: Fix proposed <https://review.opendev.org/c/openstack/cinder/+/889826> - [Pure Storage] failure to disconnect remote hosts in uniform sync rep cluster <https://bugs.launchpad.net/cinder/+bug/2029005> - Status: No comments or fix proposed Thanks Rajat Dhasmana

1 0

[openstack][neutron[nova][kolla-ansible]instance cannot ping after live migrate
by Nguyễn Hữu Khôi 02 Aug '23

02 Aug '23

Hello guys. I am using openstack yoga with kolla ansible. When I migrate: instance1 from host A to host B after that I cannot ping this instance(telnet also). I must restart neutron_openvswitch_agent or move this instance back to host B then this problem has gone. this is my settings: ----------------- neutron.conf ----------------- [nova] live_migration_events = True ------------------------------------------------ ----------------- nova.conf ----------------- [DEFAULT] vif_plugging_timeout = 600 vif_plugging_is_fatal = False debug = True [compute] live_migration_wait_for_vif_plug = True [workarounds] enable_qemu_monitor_announce_self = True ----------------- openvswitch_agent.ini----------------- [securitygroup] firewall_driver = openvswitch [ovs] openflow_processed_per_port = true I check nova, neutron, ops logs but they are ok. Thank you. Nguyen Huu Khoi

4 12

[tc] Technical Committee next weekly meeting today on August 1, 2023
by Nikolla, Kristi 01 Aug '23

01 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held today (Tuesday, Aug 1, 2023) at 1800 UTC on Zoom. Use the following link to connect https://us06web.zoom.us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 The agenda for the meeting is: • Roll call • Follow up on past action items • tc-members to review https://review.opendev.org/c/openstack/project-team-guide/+/843457 • Unmaintained status replaces Extended Maintenance • https://review.opendev.org/c/openstack/governance/+/888771 • Release notes guidelines for SLURP/NON-SLURP cadence • Gate health check • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

2 2