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

[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 13 Aug '23

13 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 11 Aug '23

11 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 08 Aug '23

08 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 07 Aug '23

07 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 06 Aug '23

06 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 05 Aug '23

05 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 03 Aug '23

03 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 03 Aug '23

03 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