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

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

15 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 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