March 2023 - openstack-discuss - lists.openstack.org

[neutron][ovn] stateless SG behavior for metadata / slaac / dhcpv6
by Ihar Hrachyshka 30 Mar '23

30 Mar '23

Hi all, (I've tagged the thread with [ovn] because this question was raised in the context of OVN, but it really is about the intent of neutron stateless SG API.) Neutron API supports 'stateless' field for security groups: https://docs.openstack.org/api-ref/network/v2/index.html#stateful-security-… The API reference doesn't explain the intent of the API, merely walking through the field mechanics, as in "The stateful security group extension (stateful-security-group) adds the stateful field to security groups, allowing users to configure stateful or stateless security groups for ports. The existing security groups will all be considered as stateful. Update of the stateful attribute is allowed when there is no port associated with the security group." The meaning of the API is left for users to deduce. It's customary understood as something like "allowing to bypass connection tracking in the firewall, potentially providing performance and simplicity benefits" (while imposing additional complexity onto rule definitions - the user now has to explicitly define rules for both directions of a duplex connection.) [This is not an official definition, nor it's quoted from a respected source, please don't criticize it. I don't think this is an important point here.] Either way, the definition doesn't explain what should happen with basic network services that a user of Neutron SG API is used to rely on. Specifically, what happens for a port related to a stateless SG when it trying to fetch metadata from 169.254.169.254 (or its IPv6 equivalent), or what happens when it attempts to use SLAAC / DHCPv6 procedure to configure its IPv6 stack. As part of our testing of stateless SG implementation for OVN backend, we've noticed that VMs fail to configure via metadata, or use SLAAC to configure IPv6. metadata: https://bugs.launchpad.net/neutron/+bug/2009053 slaac: https://bugs.launchpad.net/neutron/+bug/2006949 We've noticed that adding explicit SG rules to allow 'returning' communication for 169.254.169.254:80 and RA / NA fixes the problem. I figured that these services are "base" / "basic" and should be provided to ports regardless of the stateful-ness of SG. I proposed patches for this here: metadata series: https://review.opendev.org/q/topic:bug%252F2009053 RA / NA: https://review.opendev.org/c/openstack/neutron/+/877049 Discussion in the patch that adjusts the existing stateless SG test scenarios to not create explicit SG rules for metadata and ICMP replies suggests that it's not a given / common understanding that these "base" services should work by default for stateless SGs. See discussion in comments here: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/876692 While this discussion is happening in the context of OVN, I think it should be resolved in a broader context. Specifically, a decision should be made about what Neutron API "means" by stateless SGs, and how "base" services are supposed to behave. Then backends can act accordingly. There's also an open question of how this should be implemented. Whether Neutron would like to create explicit SG rules visible in API that would allow for the returning traffic and that could be deleted as needed, or whether backends should do it implicitly. We already have "default" egress rules, so there's a precedent here. On the other hand, the egress rules are broad (allowing everything) and there's more rationale to delete them and replace them with tighter filters. In my OVN series, I implement ACLs directly in OVN database, without creating SG rules in Neutron API. So, questions for the community to clarify: - whether Neutron API should define behavior of stateless SGs in general, - if so, whether Neutron API should also define behavior of stateless SGs in terms of "base" services like metadata and DHCP, - if so, whether backends should implement the necessary filters themselves, or Neutron will create default SG rules itself. I hope I laid the problem out clearly, let me know if anything needs clarification or explanation. Yours, Ihar

3 6

[Magnum] vPTG
by Jake Yip 29 Mar '23

29 Mar '23

Dear all, Magnum vPTG will be held at Wed 0900 UTC in the Havana Room. Please see etherpad https://etherpad.opendev.org/p/march2023-ptg-magnum for updates Regards, Jake (sorry for duplicates)

1 1

OpenStack 2023.1 Antelope for Ubuntu 22.04 LTS
by Corey Bryant 29 Mar '23

29 Mar '23

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack 2023.1 Antelope on Ubuntu 22.04 LTS (Jammy Jellyfish). Details of the Antelope release can be found at: https://www.openstack.org/software/antelope The Ubuntu Cloud Archive for OpenStack 2023.1 Antelope can be enabled on Ubuntu 22.04 by running the following command: sudo add-apt-repository cloud-archive:antelope The Ubuntu Cloud Archive for 2023.1 Antelope includes updates for: aodh, barbican, ceilometer, cinder, designate, designate-dashboard, dpdk (22.11.1), glance, gnocchi, heat, heat-dashboard, horizon, ironic, ironic-ui, keystone, magnum, magnum-ui, manila, manila-ui, masakari, mistral, murano, murano-dashboard, networking-arista, networking-bagpipe, networking-baremetal, networking-bgpvpn, networking-hyperv, networking-l2gw, networking-mlnx, networking-odl, networking-sfc, neutron, neutron-dynamic-routing, neutron-fwaas, neutron-taas, neutron-vpnaas, nova, octavia, octavia-dashboard, openstack-trove, openvswitch (3.1.0), ovn (23.03.0), ovn-octavia-provider, placement, sahara, sahara-dashboard, senlin, swift, trove-dashboard, vitrage, watcher, watcher-dashboard, zaqar, and zaqar-ui. For a full list of packages and versions, please refer to: https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/antelope_vers… == Reporting bugs == If you have any issues please report bugs using the ‘ubuntu-bug’ tool to ensure that bugs get logged in the right place in Launchpad: sudo ubuntu-bug nova-conductor Thank you to everyone who contributed to OpenStack 2023.1 Antelope! Corey (on behalf of the Ubuntu OpenStack Engineering team)

1 0

(Openstack-Designate) rndc key not getting generated in /etc/designate
by Adivya Singh 29 Mar '23

29 Mar '23

Hi Team, My DNS Server located outside the Open Stack, and i am using below variables in my user_variables.yaml File. But When i ' m running os-desigante-install.yml Playbook, rndc key are not generating in /etc/designate Folder and the playbook fail at the below Task {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'file'\n\nThe error appears to be in '/etc/ansible/roles/os_designate/tasks/designate_post_install.yml': line 89, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Create Designate rndc key file\n ^ here\n"} - name: Create Designate rndc key file template: src: rndc.key.j2 dest: "{{ item.file }}" owner: "{{ item.owner | default('root') }}" group: "{{ item.group | default('root') }}" mode: "{{ item.mode | default('0600') }}" with_items: "{{ designate_rndc_keys }}" when: designate_rndc_keys is defined and the post-install.yml File looks like this Any idea on this, Where i am missing ## rndc keys for authenticating with bind9 # define this to create as many key files as are required # designate_rndc_keys # - name: "rndc-key" # file: /etc/designate/rndc.key # algorithm: "hmac-md5" # secret: "<key>"

2 1

[ironic] bug tracking move to launchpad
by Julia Kreger 29 Mar '23

29 Mar '23

Greetings Ironic! During the PTG yesterday, we discussed the fact we had not moved back to Launchpad for bug tracking. Mainly because we are all very busy. The point was raised, why don't we just re-enable launchpad bug tracking, and move our primary usage back to that. Consensus on the call resulted with this proposal, and the consensus to send this email to the mailing list. As such, if nobody objects, I'm going to go turn the bug tracker for Ironic in launchpad back on next Monday. If you object, scream now and/or write a migration script and/or propose another solution. Thanks! -Julia

1 0

(Openstack-Nova)
by Adivya Singh 29 Mar '23

29 Mar '23

Hi Team I see these error in my syslog related to my nova compute service getting hung while communicating to rabbit-mq service "A recoverable connection/channel error occurred, trying to reconnect: [Errno 24] Too many open files" Is this a OS related error, or some thing i can change to get rid of this error Regards Adivya Singh

3 2

[neutron] BGP for self-service network
by Deniz AYDIN 29 Mar '23

29 Mar '23

Hi, I am looking for options for removing Layer-2 in the underlay as much as possible. The features explained in the document, BGP floating IPs over L2 segmented network <https://docs.openstack.org/neutron/zed/admin/config-bgp-floating-ip-over-l2…>, solve the problem for floating IPS where layer 2 is only needed between servers and rack switches. Is there any specific reason that this feature is limited to floating IPS? As long as we have unique BGP next-hops defined for every DVR, it can also be used for advertising self-service networks /32 routes. Thanks for the help Deniz

1 0

[nova] openstack-tox-pep8 job broken, hold your rechecks
by melanie witt 29 Mar '23

29 Mar '23

Hey all, Sending this to the ML to try to help others who may not have heard about it yet. I didn't know about myself until I saw the job fail on a random nova patch and I looked around to figure out why. It looks like openstack-tox-pep8 is failing 100% in nova due to a newer version of the mypy library being pulled in since a recent upper-constraints bump: https://review.opendev.org/c/openstack/requirements/+/872065 And the job isn't going to pass until the following fix merges: https://review.opendev.org/c/openstack/nova/+/878693 Finally, to help prevent a breakage for this in the future, a cross-nova-pep8 job has been approved: https://review.opendev.org/c/openstack/requirements/+/878748 and will be on its way to the gate once the aforementioned fix merges. I'll post a reply to this email when it's OK to do rechecks again. Cheers, -melwitt

2 3

[nova] Hold your rechecks
by Sylvain Bauza 29 Mar '23

29 Mar '23

Hey, Due to the recent merge of https://review.opendev.org/c/openstack/requirements/+/872065/10/upper-const… we now use mypy==1.1.1 which includes a breaking behavioural change against our code : https://07de6a0c9e6ec0c6835f-ccccbfab26b1456f69293167016566bc.ssl.cf2.rackc… Thanks to Eric (kudos to him, he was quickier than me), we have a fix https://review.opendev.org/c/openstack/nova/+/878693 Please accordingly hold your rechecks until that fix is merged. -Sylvain

1 1

[PTL][release][stable][EM] Extended Maintenance - Xena
by Elõd Illés 29 Mar '23

29 Mar '23

Hi teams, As 2023.1 Antelope was released last week and we are in a less busy period, now is the good time to call your attention to the following: In less than a month Xena is planned to transition to Extended Maintenance phase [1] (planned date: 2023-04-20). I have generated the list of the current *open* and *unreleased* changes in stable/xena for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Xena before moving stable/xena branches to Extended Maintenance. Feel free to edit and extend these lists to track your team's progress! Note that the *latest* Xena *release* tagging patches ('xena-em' tag) have been generated too in advance [3], please mark with a -1 if your team plans to do a final release, or +1 if the team is ready for the transition. The schedule from now on is as follows: * patches with +1 from PTL / release liaison will be merged, thus those repositories will transition to Extended Maintenance * at the planned deadline (April 20th) the Release Team will merge all of the transition patches (even the ones without any response!) * after the transition, stable/xena will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases! [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/xena-final-release-before-em [3] https://review.opendev.org/q/topic:xena-em Thanks, Előd irc: elodilles @ #openstack-release

1 0

[nova][ptg] Today's agenda
by Sylvain Bauza 29 Mar '23

29 Mar '23

(just shamelessly stealing the idea from Neutron's team) Hey foks, Yesterday was a packed day but we didn't really progressed on a lot of topics. Today I'm gonna propose a list of topics in order to improve our sessions's visibility and in order to provide some timeboxing. 13:00 UTC - 14:45 UTC : * How to make sure people can help to review ? * Should we ask for some implementation before accepting a spec ? * CI stability is a nightmare, let's fight over this * Bobcat is a non-SLURP release * Let's clean up our upgrade documentation * Nova community outreach * Clean-up our bug list by abandoning very old LP bug reports ? * Summit/PTG : what could we be doing for the physical PTG ? (Will be 4 weeks before milestone-2) 15:00 UTC - 15:45 UTC : * Nova/Manila cross-project session : Prevent share deletion while it's attached to an instance 16:00 UTC - 17:00 UTC : * When your instance is stuck due to hard affinity policies, what could we do ? * Users reported exhaustion of primary keys ('id') in some large tables like system_metadata. How could we achieve a data migration from sa.Integer to sa.BigInteger ? Details can be found in https://etherpad.opendev.org/p/nova-bobcat-ptg#L192 I assume the packed agenda, particularly the first two hours. As a reminder, people are welcome to add their IRC nicks in each of the courtesy ping list of the related topic. Hope this gives you a taste of joining the Nova PTG today. -Sylvain

1 0

[neutron][ptg] Today's agenda
by Rodolfo Alonso Hernandez 29 Mar '23

29 Mar '23

Hello all: This is a quick summary of the agenda for today's meeting (starting at 13UTC): * Status and questions about https://review.opendev.org/q/topic:port-hints * IPv6 Prefix Delegation in OVN * Neutron agents status (https://bugs.launchpad.net/neutron/+bug/2011422) * DHCP IPv6 issues with metadata service ( https://bugs.launchpad.net/neutron/+bug/1953165) * Operator hour Please check the full agenda, topics and past logs in https://etherpad.opendev.org/p/neutron-bobcat-ptg. Regards.

1 0

[Horizon][policies][keystone] allow _member_ role to add user
by James Leong 28 Mar '23

28 Mar '23

Hi all, I am using kolla-ansible for OpenStack deployment in the yoga version. Would it be possible to allow a user with a "_member_" role to add a user to the respective project? In OpenStack, an admin role allows users to add, delete, and edit a user profile. I would like to have the same privilege added to the "_member_" role. I have tried to modify the file "user.py" in the keystone container at "keystone/common/policies" and restarted the container. However, the button on my horizon dashboard did not appear. How could I integrate the code in order to allow the create button to appear on my dashboard with the "_member_" role? Is there a way to do that? THanks for your help James

1 0

[scientific-sig] PTG sessions for Scientific SIG
by Stig Telfer 28 Mar '23

28 Mar '23

Hi all - The Scientific SIG has two sessions on Wednesday (tomorrow) at the PTG, at 1400 UTC and 2100 UTC. Everyone is welcome. There is an etherpad for the sessions here: https://etherpad.opendev.org/p/march2023-ptg-scientific-sig <https://etherpad.opendev.org/p/march2023-ptg-scientific-sig>. We'll begin with an introduction to the SIG and some discussion of problems, challenges and new features specific to research computing use cases. We'd also like participants to contribute lightning talks about anything relevant that is of interest to them. Cheers, Stig

1 0

[Magnum] vPTG
by Jake Yip 28 Mar '23

28 Mar '23

Dear all, Magnum vPTG will be held at Wed 0900 UTC in the Havana Room. Please see etherpad https://etherpad.opendev.org/p/march2023-ptg-magnum for updates Regards, Jake -- Jake Yip DevOps Engineer, ARDC Nectar Research Cloud

2 1

[networking-mlnx] release job failure - missing openstackci as maintainer in pypi
by Elõd Illés 28 Mar '23

28 Mar '23

Hi networking-mlnx maintainers, latest networking-mlnx releases caused release job failures [1][2][3], with the following error: The user 'openstackci' isn't allowed to upload to project 'networking-mlnx'. (note, that networking-mlnx is not under openstack namespace (x/networking-mlnx)) [1] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… [2] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… [3] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… Thanks, Előd irc: elodilles @ #openstack-release

1 0

[Freezer] Restore action report ERROR can't delete temporary Image
by Annie Liu(BJ-RD) 28 Mar '23

28 Mar '23

Hi All My Cinder Backend is Ceph, and so is Glance. For backup and restore, I choose Cinder for mode and local for storage . When I restore a Cinder volume with Freezer, an ERROR reported related to deleting temporary Image failure, which makes the whole restore flow can't be completed. 2023-03-23 16:53:50.555 361 ERROR freezer.main [-] HTTP 409 Conflict: Image 8af4be3f-2e7a-4965-8b34-74e610a89a3e could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance.: HTTPConflict: HTTP 409 Conflict: Image 8af4be3f-2e7a-4965-8b34-74e610a89a3e could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance. According to Cinder source code, the volume created from Image is a child of the Image, since it is made by clone which means it doesn't copy volume data at first. In other words, the Image is its parent holding the real data, and that's why deleting is failed. My question is, is this a general issue for other storage solution? Is there any opportunity to fix it? For example, do a flatten immediately after create volume from Image? Thanks. Beat Regards, Annie Liu ????? ????????????????????????????????????????????????????? CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

1 0

[neutron] Bug deputy report (week of Mar 20)
by Akihiro Motoki 28 Mar '23

28 Mar '23

Hi, Here is the bug deputy report last week. Hopefully, someone familiar with DNS integration can check the first bug. # Needs assignee * FQDN inside guest VM is not the same as dns_assignment on network port https://bugs.launchpad.net/neutron/+bug/2012391 It would be nice if someone familiar with DNS integration can look into it. * [CI] "neutron-ovs-grenade-multinode-skip-level" and "neutron-ovn-grenade-multinode-skip-level" failing always https://bugs.launchpad.net/neutron/+bug/2012731 # New but assigned * [OVN] Define the OVS port in the LSP to allow OVN to set the QoS rules https://bugs.launchpad.net/neutron/+bug/2012613 Assigned to ralonsoh # In Progress * [ovn] N/S traffic for VMs without FIPs not working https://bugs.launchpad.net/neutron/+bug/2012712 Assigned to ltomasbo [1] was proposed as a fix of bug 2012712 which is caused by [2]. In parallel, [3] was proposed to revert [2]. Reverting [2] first sounds reasonable to avoid the regression but it is better to clarify the priority and the relationship in the review comments. ltomasbo is involved in both, so I think there is no confusion though. [1] https://review.opendev.org/c/openstack/neutron/+/878450 [2] https://review.opendev.org/c/openstack/neutron/+/875644 [3] https://review.opendev.org/c/openstack/neutron/+/878441 * neutron-ovn-agent fails on do_commit aborted due to error: 'Chassis_Private' https://bugs.launchpad.net/neutron/+bug/2012385 * Intermittent failures of test_agent_metadata_port_ip_update_event https://bugs.launchpad.net/neutron/+bug/2012754 * [sqlalchemy-20] sqlalchemy.exc.InvalidRequestError: No 'on clause' argument may be passed when joining to a relationship path as a target https://bugs.launchpad.net/neutron/+bug/2012643 * [sqlalchemy-20] Strings are not accepted for attribute names in loader options https://bugs.launchpad.net/neutron/+bug/2012662 * [sqlalchemy-20] Unexpected keyword argument "when" in "sqlalchemy.case" method https://bugs.launchpad.net/neutron/+bug/2012705 # RFE * [rfe] Add one api support CRUD allowed_address_pairs https://bugs.launchpad.net/neutron/+bug/2012332 Thanks, Akihiro Motoki (amotoki)

1 0

(Open Stack )Image Upload in Open Stack in a Bulk
by Adivya Singh 28 Mar '23

28 Mar '23

Hi Team, Any hints, if i want to upload images in a bulk in a Open Stack , because it takes some time for the image to copy if we go one by one, or even of we go with script Also if there is a scenario where glance mount point fails and we can create the same Share path and Copy the Image from the source , Will the OpenStack glance Service will start detecting those images upload in a share Regards Adivya Singh

2 3

[swift][ptg] Ops Feedback Session - 29th March at 13:00 UTC
by Matthew Oliver 28 Mar '23

28 Mar '23

As we've done in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting in Ocata (https://www.openstack.org/ptg/rooms/ocata) at 13:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, We'd appreciate it if you can offer some feedback on the feedback etherpad (https://etherpad.opendev.org/p/swift-bobcat-ops-feedback ). This has always been a highlight at every PTG for us swift devs. Have your say and help make Swift even better! Matt

1 0

DCN compute service goes down when a instance is scheduled to launch | wallaby | tripleo
by Swogat Pradhan 28 Mar '23

28 Mar '23

Hi, I currently have 3 compute nodes on edge site1 where i am trying to launch vm's. When the VM is in spawning state the node goes down (openstack compute service list), the node comes backup when i restart the nova compute service but then the launch of the vm fails. nova-compute.log 2023-02-26 08:15:51.808 7 INFO nova.compute.manager [req-bc0f5f2e-53fc-4dae-b1da-82f1f972d617 - - - - -] Running instance usage audit for host dcn01-hci-0.bdxworld.com from 2023-02-26 07:00:00 to 2023-02-26 08:00:00. 0 instances. 2023-02-26 08:49:52.813 7 INFO nova.compute.claims [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Claim successful on node dcn01-hci-0.bdxworld.com 2023-02-26 08:49:54.225 7 INFO nova.virt.libvirt.driver [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Ignoring supplied device name: /dev/vda. Libvirt can't honour user-supplied dev names 2023-02-26 08:49:54.398 7 INFO nova.virt.block_device [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Booting with volume c4bd7885-5973-4860-bbe6-7a2f726baeee at /dev/vda 2023-02-26 08:49:55.216 7 WARNING nova.cache_utils [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Cache enabled with backend dogpile.cache.null. 2023-02-26 08:49:55.283 7 INFO oslo.privsep.daemon [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Running privsep helper: ['sudo', 'nova-rootwrap', '/etc/nova/rootwrap.conf', 'privsep-helper', '--config-file', '/etc/nova/nova.conf', '--config-file', '/etc/nova/nova-compute.conf', '--privsep_context', 'os_brick.privileged.default', '--privsep_sock_path', '/tmp/tmpin40tah6/privsep.sock'] 2023-02-26 08:49:55.791 7 INFO oslo.privsep.daemon [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Spawned new privsep daemon via rootwrap 2023-02-26 08:49:55.717 2647 INFO oslo.privsep.daemon [-] privsep daemon starting 2023-02-26 08:49:55.722 2647 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2023-02-26 08:49:55.726 2647 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_SYS_ADMIN/CAP_SYS_ADMIN/none 2023-02-26 08:49:55.726 2647 INFO oslo.privsep.daemon [-] privsep daemon running as pid 2647 2023-02-26 08:49:55.956 7 WARNING os_brick.initiator.connectors.nvmeof [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] Process execution error in _get_host_uuid: Unexpected error while running command. Command: blkid overlay -s UUID -o value Exit code: 2 Stdout: '' Stderr: '': oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2023-02-26 08:49:58.247 7 INFO nova.virt.libvirt.driver [req-3a1547ea-326f-4dd0-9127-7f4a4bdf1e45 b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - default default] [instance: 0c62c1ef-9010-417d-a05f-4db77e901600] Creating image Is there a way to solve this issue? With regards, Swogat Pradhan

5 40

[ironic] Slight PTG Schedule change
by Jay Faulkner 27 Mar '23

27 Mar '23

Take notice: tomorrow's topic schedule has been changed slightly. We have moved Service Steps and DPU Orchestration conversations up 30 minutes. As mentioned in the other thread ( https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032983.h…) I accidentally booked Firmware Upgrades to two times. This was fortuitous because we needed to add a cross-team item with Keystone. As always, the up to date schedule and notes are here: https://etherpad.opendev.org/p/ironic-bobcat-ptg Thanks, Jay Faulkner Ironic PTL

1 0

[all][ptg] Pre-PTG discussion: New Keystone Middleware Feature Supporting OAuth2.0 with External Authorization Service
by Hiromu Asahina 27 Mar '23

27 Mar '23

Hello Everyone, Recently, Tacker and Keystone have been working together on a new Keystone Middleware that can work with external authentication services, such as Keycloak. The code has already been submitted [1], but we want to make this middleware a generic plugin that works with as many OpenStack services as possible. To that end, we would like to hear from other projects with similar use cases (especially Ironic and Barbican, which run as standalone services). We will make a time slot to discuss this topic at the next vPTG. Please contact me if you are interested and available to participate. [1] https://review.opendev.org/c/openstack/keystonemiddleware/+/868734 -- Hiromu Asahina

4 11

[nova] Can OpenStack support snapshot rollback (not creating a new instance)?
by 韩光宇 27 Mar '23

27 Mar '23

Hello, I use Ceph as the storage backend for Nova, Glance, and Cinder. If I create a snapshot for a instance, It create a new image in glance. And I can use the image to create a new instance. This feels to me more like creating an image based on the current state of the VM rather than creating a VM snapshot. I want to ask: 1、Can I create and revert a VM snapshot like I would in virtual machine software? 2、When a VM uses multiple disks/volumes, does OpenStack support taking a snapshot of all disks/volumes of the VM as a whole? 3、Can OpenStack snapshot and save the memory state of a VM? If it is not currently supported, are there any simple customization implementation ideas that can be recommended? Thank you for any help and suggestions. Best wishes. Han

3 2

[neutron][release] Proposing transition to EOL Train (all Neutron related projects)
by Rodolfo Alonso Hernandez 27 Mar '23

27 Mar '23

Hello: I'm sending this mail in advance to propose transitioning Neutron and all related projects to EOL. I'll propose this topic too during the next Neutron meeting. The announcement is the first step [1] to transition a stable branch to EOL. The patch to mark these branches as EOL will be pushed in two weeks. If you have any inconvenience, please let me know in this mail chain or in IRC (ralonsoh, #openstack-neutron channel). You can also contact any Neutron core reviewer in the IRC channel. Regards. [1] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l…

3 3

[ptg][sdk][cli][ansible] PTG Slot for SDK, CLI, Ansible collection OpenStack is now booked
by Artem Goncharov 27 Mar '23

27 Mar '23

Hi all, A bit late, but still - I have booked a 3 hours slot during PTG on Friday 14:00-17:00 UTC. This will follow publiccloud room discussion so I think some people and outcomes will follow directly into our room. Etherpad is there: https://etherpad.opendev.org/p/march2023-ptg-sdk-cli Feel free to feel in topics you want to discuss Cheers, Artem

3 6

[Diversity] Diversity and Inclusion at the PTG
by Amy Marrich 24 Mar '23

24 Mar '23

I have blocked off three hours on Monday for the D&I WG to discuss the upcoming Diversity Survey(14:00 UTC) and then ongoing changes to the Code of Conduct(15:00- 16:00 UTC) and then the Summit if there is time. The agenda can be found here[0]. All projects are encouraged to attend these sessions as the WG is at the Foundation level. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/march2023-ptg-diversity

1 0

[openstack-helm] PTG March 27-31 2023
by Vladimir Kozhukalov 24 Mar '23

24 Mar '23

Dear openstack-helmers, As you know PTG is going to happen next week and I booked slots at the end of the week on Thursday 03/30 and on Friday 03/31 from 14:00 UTC till 17:00 UTC [1] I believe this should be enough. If you feel other time slots are gonna work better for any reason there are still some free slots that can be booked. Please also pay some attention to the etherpad where I listed some of the points for our discussions. [2] Please feel free to add other points that you think worth it to be discussed. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/march2023-ptg-openstack-helm -- Best regards, Kozhukalov Vladimir

1 0

[i18n][PTG] I18n SIG 2023.2 (Bobcat) PTG Planning
by Ian Y. Choi 24 Mar '23

24 Mar '23

Hi, PTG is coming next week. I have blocked the following schedule - anyone can check via https://ptg.opendev.org/ptg.html and please let me know if more discussion is needed during PTG. Those are topics what I am thinking currently but it is open - feel free to suggest any topic to be discussed: - Weblate migration - Translation artifacts release management - Review of i18n statistics & ATC/AC - Discussion on translation target - Overall OpenStack/OpenInfra I18n process/progress review - Check-in on each language team Discussions will be shared via Etherpad: https://etherpad.opendev.org/p/march2023-ptg-i18n . Lastly, please don't forget to register if you have forgotten: https://openinfra-ptg.eventbrite.com :) Looking forward to a productive PTG with I18n. Thank you, /Ian

1 0

[cinder][PTG] Cinder 2023.2 (Bobcat) Virtual PTG
by Rajat Dhasmana 24 Mar '23

24 Mar '23

Hello Argonauts, We will be conducting cinder virtual PTG for 2023.2 (Bobcat) cycle from 28th March to 31st March, 2023. I've prepared the PTG etherpad[1] with topics day wise. I haven't kept the schedule time bound since some discussions take less and some take more time and in both cases reaching a conclusion is important. There are some events that need to be done on their respective time are as follows: *1) Operator Hour: *We encourage operators to join and tell us about the pain points of cinder so we can improve upon it. Date: Wednesday, 29 March, 2023 Time: 1400-1500 UTC Link: https://bluejeans.com/556681290 *2) Glance Cross Project* Date: Thursday, 30 March, 2023 Time: 1430-1500 UTC Link: https://bluejeans.com/556681290 *3) Nova Cross Project* Date: Thursday, 30 March, 2023 Time: 1600-1700 UTC Link: https://zoom.us/j/96494117185?pwd=NGhya0NpeWppMEc1OUNKdlFPbDNYdz09 (Diablo room) The general information about the PTG is as follows: Date: 28th March to 31st March, 2023 Time: 1300-1700 UTC everyday Link to PTG: https://bluejeans.com/556681290 You can also follow the schedule at https://ptg.opendev.org/ptg.html Note that we have allocated 4 hours each day but it also depends on the number and duration of topics as to how long the PTG will run. If you want to be reminded about a particular topic, please add your IRC nick in the *Courtesy ping list *mentioned after every topic. If you still have topics, please add them to the Planning etherpad[2] and I will see if we can accommodate that into our current schedule. Lastly, we will be cancelling our cinder upstream meeting (Wednesday, 29 March, 1400-1500 UTC) since it overlaps with the PTG. If you still have topics please bring it to the PTG. See you all at the PTG! [1] https://etherpad.opendev.org/p/bobcat-ptg-cinder [2] https://etherpad.opendev.org/p/bobcat-ptg-cinder-planning Thanks Rajat Dhasmana

1 0

[TripleO] Last maintained release of TripleO is Wallaby
by James Slagle 24 Mar '23

24 Mar '23

The team of TripleO developers, reviewers, and community have no plans to do another release of TripleO, or to continue maintaining the Zed release. This means the last maintained release of TripleO is Wallaby. The plan is to continue to maintain the train and wallaby branches of TripleO repositories under the openstack namespace. We plan to continue to run existing CI on those branches, although we anticipate reducing to a minimal set of jobs in the future. Going forward, the TripleO team expects to continue involvement in other OpenStack projects, and focus on different approaches to OpenStack deployment. The team is not aware of enough other community interest to continue to maintain the zed, master, and future branches of TripleO. Eventually, we will empty commit these branches with a pointer to Wallaby being the last release. If other interests do exist to maintain TripleO going forward, then those plans can adjust. TripleO does not plan on nominating a PTL in the current Bobcat election cycle. If a PTL-like contact is needed for train and wallaby maintenance, then someone will be nominated. I am also not sure how to reflect this project structure change within openstack/governance, and am looking for guidance on how to do so. This type of change did not seem to exactly fit within the concepts of inactive or retired projects. I can work on the patches for governance with some direction, if anyone can provide it. Thanks, and please let us know any questions or feedback about this plan. -- -- James Slagle --

6 21

[security-sig] vPTG sessions 16:00 UTC Tuesday and Wednesday
by Jeremy Stanley 24 Mar '23

24 Mar '23

I've booked two hours on the vPTG schedule, Tuesday and Wednesday 16:00-17:00 UTC, in the hopes that interested parties will be able to make at least one of those if not both. We'll use OpenDev's Meetpad service: https://meetpad.opendev.org/march2023-ptg-os-security I tried to avoid booking conflicts with Barbican and Keystone since those are the two projects our participants traditionally have obligatory conflicts from (also worked around the TC, Release and Diversity WG sessions). I know folks from Ironic wanted to talk about VMT topics, but our times overlap with some of theirs so we can either try to talk about that in one of the non-overlapping Ironic sessions or they can join us during ours, whichever works better. I've started adding some proposed discussion topics to the corresponding pad, but anyone can feel free to throw ideas in there, or just bring them up once we're on the call... I'm not one to stand on ceremony: https://etherpad.opendev.org/p/march2023-ptg-os-security Hopefully some people will be able to make it, but if you want other times on the schedule too then let me know and I'll try to work something out. -- Jeremy Stanley

1 0

[blazar][ptg] Bobcat PTG scheduling
by Pierre Riteau 24 Mar '23

24 Mar '23

Hello, The Bobcat PTG will happen online during the week starting March 27. As the Blazar project has done in the past, I suggest we meet on Thursday, but starting 1400 UTC rather than the usual 1500 of our biweekly meeting. I have booked two hours in the Bexar room. If you want to join, please let me know if this works for you. To summarise, the Blazar project will meet on Thursday March 30 from 1400 UTC to 1600 UTC. We will prepare discussion topics on Etherpad. Cheers, Pierre Riteau (priteau)

1 1

OUTREACHY INITIAL APPLICANT
by Anointing Adetoye 24 Mar '23

24 Mar '23

Good day I have been unable to make relevant contributions because I don't know how to start contributing or converse on the channel. Also, I am a golang developer that is just picking C and I would really like to use this opportunity to build my knowledge in C. I will appreciate it if i get pointed to how to make contribution and also utilize the few weeks remaining to make relevant contribution to the project.

2 1

[neutron] Neutron driver's meeting cancelled
by Rodolfo Alonso Hernandez 24 Mar '23

24 Mar '23

Hello Neutrinos: Today's drivers meeting is cancelled. The only topic in the agenda [1] was agreed to be discussed during the PTG. Join us next week in the PTG sessions! Here is the Neutron agenda [2] and the PTG website [3]. We'll be on the Juno channel. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers [2]https://etherpad.opendev.org/p/neutron-bobcat-ptg [3]https://ptg.opendev.org/ptg.html

1 0

[nova]host cpu reserve
by Nguyễn Hữu Khôi 24 Mar '23

24 Mar '23

Hello guys. I am trying google for nova host cpu reserve to prevent host overload but I cannot find any resource about it. Could you give me some information? Thanks. Nguyen Huu Khoi

3 12

回复： [ironic]Questions about the use of the build image tool
by 任亮 24 Mar '23

24 Mar '23

I have found the cause of the problem, which is because tar does not exist in the working directory. I wonder if there are requirements on the base image when building from the base image.  Thank you. 发自我的企业微信 ----------回复的邮件信息---------- 任亮<renliang(a)uniontech.xn--com> 2023-03-23-jw84b 周四 15:01写道： Hi We are using diskimage-builder to make a custom image, There is a problem in extract_image, The question is chroot: failed to run command 'bin/tar': No such file or directory, I found the /bin/tar file in the working directory /tmp/ tmp.00yldwe1xt. But errors are still being reported. It's not clear if this is a custom image problem, There are also requirements for custom images. 发自我的企业微信

2 1

[manila] Cancelling March 30th IRC weekly meeting
by Carlos Silva 24 Mar '23

24 Mar '23

Hello Zorillas! As mentioned in today's IRC meeting, we will be having several meetings at the PTG next week, so we will not have our usual IRC meeting on Thursday March 30th 15 UTC. See you at the PTG! Regards, carloss

1 0

[manila] Bobcat vPTG slots and topics
by Carlos Silva 24 Mar '23

24 Mar '23

Hello, Zorillas! PTG is right around the corner and I would like to remind you to please add the topics you would like to bring up during our sessions to the planning etherpad [1] until next Tuesday (Mar 21st). I have already allocated some slots for our sessions: - Monday: 16:00 to 17:00 UTC - Wednesday: 14:00 to 16:00 UTC - Thursday: 14:00 to 16:00 UTC - Friday: 14:00 to 17:00 UTC We will be meeting in the Austin room, you can access the meeting room through the PTG page [2]. If you have a preference of date/time for your topic to be discussed, please let me know and I will try to accommodate it. Looking forward to meeting you! [1] https://etherpad.opendev.org/p/manila-bobcat-ptg-planning [2] https://ptg.opendev.org/ptg.html Thanks, carloss

1 1

[tc] No TC weekly meeting next week + meeting time change
by Nikolla, Kristi 23 Mar '23

23 Mar '23

Hi all, Due to the vPTG being held next week, the TC will not hold its regular weekly meeting that was scheduled for Wednesday, March 29, 2023. Please note, that after the PTG, the new meeting time will be Tuesdays 18.00 UTC. More information and an ICS file can be found here https://meetings.opendev.org/#Technical_Committee_Meeting Thank you, Kristi Nikolla

1 0

[tc][ptl][ptg] TC + Community Leaders Interaction for 2023.2 vPTG
by Nikolla, Kristi 23 Mar '23

23 Mar '23

Hello everyone, On Monday, March 27, 2023 16.00UTC to 18.00UTC, the TC is organizing the Technical Committee & Community Leaders Interaction. While this meeting is open to all, we would like to invite participation especially from PTL, TC, and SIG Chairs with the goal of gathering feedback and promoting collaboration. This meeting has been quite successful in the last 2 PTG and I'm hoping we can continue this tradition. If you have an item you'd like to propose for discussion please add it to the purposefully quite empty etherpad[0], where you can also find information and details on how to join. 0. https://etherpad.opendev.org/p/tc-leaders-interaction-2023-2 Hope to see you there, Kristi Nikolla

1 0

[all][tc][goal][policy] RBAC goal discussion in 2023.2 PTG
by Ghanshyam Mann 23 Mar '23

23 Mar '23

Hello Everyone, I have booked the Tuesday 17-18 UTC slot bexar room for the RBAC goal discussion. You can add the topics/queries to be discussed in vPTG in the below etherpad. - https://etherpad.opendev.org/p/rbac-2023.2-ptg -gmann

1 0

Fwd: [PTG] Environmental Sustainability WG goes to the vPTG next week!
by Kendall Nelson 23 Mar '23

23 Mar '23

[Cross posting from the foundation ML] Hello Everyone! I have finally begun setting up the etherpad for our time during the PTG. I have the Austin room reserved on Tuesday from 16-18 UTC. I hope to see you all there and please add to the etherpad if there is a related topic you think we should discuss! Here is the etherpad: https://etherpad.opendev.org/p/march2023-ptg-env-sus -Kendall Nelson

1 0

[nova][ptg][ops] Nova at the vPTG (+ skipping next weekly meeting)
by Sylvain Bauza 23 Mar '23

23 Mar '23

Hey folks, As a reminder, the Nova community will discuss at the vPTG. You can see the topics we'll talk in https://etherpad.opendev.org/p/nova-bobcat-ptg Our agenda will be from Tuesday to Friday, everyday between 1300UTC and 1700UTC. Connection details are in the etherpad above, but you can also use PTGbot website : https://ptg.opendev.org/ptg.html (we'll use the diablo room for all the discussions) You can't stick around for 4 hours x 4 days ? Heh, no worries ! If you (as an operator or a developer) want to engage with us (and we'd love this honestly), you have two possibilities : - either you prefer to listen (and talk) to some topics you've seen in the agenda, and then add your IRC nick (details how to use IRC are explained by [1]) on the topics you want. Once we start to discuss about those topics, I'll ping the courtesy ping list of each topic on #openstack-nova. Just make sure you're around in the IRC channel. - or you prefer to engage with us about some pain points or some feature requests, and then the right time is the Nova Operator Hour that will be on *Tuesday 1500UTC*. We have a specific etherpad for this session : https://etherpad.opendev.org/p/march2023-ptg-operator-hour-nova where you can preemptively add your thoughts or concerns. Anyway, we are eager to meet you all ! Oh, last point, given we will be at the vPTG, next week's weekly meeting on Tuesday is CANCELLED. But I guess you'll see it either way if you lurk the #openstack-nova channel ;-) See you next week ! -Sylvain [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032853.h…

3 4

[qa][ptg] Virtual Bobcat vPTG Planning
by Martin Kopec 23 Mar '23

23 Mar '23

Hello everyone, here is [1] our etherpad for the 2023.2 Bobcat PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots for our sessions so that they fit your schedule at [2]. We will go most likely with 1-hour slot per day, as they usually fit easier into everyone's schedule. The number of slots will depend on the number of topics proposed in [1]. [1] https://etherpad.opendev.org/p/qa-bobcat-ptg [2] https://framadate.org/sLZppMVkFw2FcEhO Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 1

[tacker][ptg] Bobcat vPTG Planning
by Yasufumi Ogawa 23 Mar '23

23 Mar '23

Hi team, We are going to have the Bobcat vPTG through three days, 28-30 Mar 6am-8am UTC as agreed at the IRC meeting last week. I've booked rooms for the sessions and uploaded etherpad [1]. Please feel free to add your proposal on the etherpad. [1] https://etherpad.opendev.org/p/tacker-bobcat-ptg Thanks, Yasufumi

1 1

[heat][PTG] 2023.2 (Bobcat) PTG Planning
by Takashi Kajinami 23 Mar '23

23 Mar '23

Hello, I've signed up for the upcoming virtual PTG so that we can have some slots for Heat discussion. In case you are interested in attending the sessions or have any topics you want to discuss, please put your name and the proposed topics in the etherpad. https://etherpad.opendev.org/p/march2023-ptg-heat-planning It'd be nice if we can update the planning etherpad this week so that I'll fix our slots and topics early next week. Thank you, Takashi Kajinami

1 1

[ironic]Questions about the use of the build image tool
by 任亮 23 Mar '23

23 Mar '23

Hi We are using diskimage-builder to make a custom image, There is a problem in extract_image, The question is chroot: failed to run command 'bin/tar': No such file or directory, I found the /bin/tar file in the working directory /tmp/ tmp.00yldwe1xt. But errors are still being reported. It's not clear if this is a custom image problem, There are also requirements for custom images. 发自我的企业微信

1 0

Unable to create volume with image in edge site | Glance-Cinder | Openstack DCN | Wallaby
by Swogat Pradhan 22 Mar '23

22 Mar '23

Hi, I am creating a fresh thread for this glance issue. I have setup glance multistore for my infra. glance.yaml for dcn site: (overcloud) [stack@hkg2director ~]$ cat dcn02/glance_dcn02.yaml parameter_defaults: #GlanceShowMultipleLocations: true GlanceEnabledImportMethods: web-download,copy-image GlanceBackend: rbd GlanceStoreDescription: 'dcn02 rbd glance store' GlanceBackendID: dcn02 CephClusterName: dcn02 GlanceMultistoreConfig: ceph: GlanceBackend: rbd GlanceStoreDescription: 'Default glance store backend.' CephClusterName: ceph Now i have created a cirros image and have imported it to dcn store using copy-image method. When I create an empty volume in the DCN site the volume gets created without any issues. But when I create a volume with image (volume source) the volume gets stuck in the creating state forever. I get logs in cinder-volume 3-4 mins after I have hit the create volume button. Cinder logs: 2023-03-22 20:34:59.166 108 INFO cinder.volume.flows.manager.create_volume [req-0d2093a0-efbd-45a5-bd7d-cce25ddc200e b240e3e89d99489284cd731e75f2a5db 4160ce999a31485fa643aed0936dfef0 - - -] Volume 5743a879-090d-46db-bc7c-1c0b0669a112: being created as image with specification: {'status': 'creating', 'volume_name': 'volume-5743a879-090d-46db-bc7c-1c0b0669a112', 'volume_size': 2, 'image_id': 'acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b', 'image_location': ('rbd://a5ae877c-bcba-53fe-8336-450e63014757/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', [{'url': 'rbd://a5ae877c-bcba-53fe-8336-450e63014757/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', 'metadata': {'store': 'ceph'}}, {'url': 'rbd://a8d5f1f5-48e7-5ede-89ab-8aca59b6397b/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', 'metadata': {'store': 'dcn02'}}]), 'image_meta': {'name': 'cirros', 'disk_format': 'qcow2', 'container_format': 'bare', 'visibility': 'public', 'size': 16338944, 'virtual_size': 117440512, 'status': 'active', 'checksum': '1d3062cd89af34e419f7100277f38b2b', 'protected': False, 'min_ram': 0, 'min_disk': 0, 'owner': '4160ce999a31485fa643aed0936dfef0', 'os_hidden': False, 'os_hash_algo': 'sha512', 'os_hash_value': '553d220ed58cfee7dafe003c446a9f197ab5edf8ffc09396c74187cf83873c877e7ae041cb80f3b91489acf687183adcd689b53b38e3ddd22e627e7f98a09c46', 'id': 'acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b', 'created_at': datetime.datetime(2023, 3, 22, 18, 50, 5, tzinfo=datetime.timezone.utc), 'updated_at': datetime.datetime(2023, 3, 22, 20, 3, 54, tzinfo=datetime.timezone.utc), 'locations': [{'url': 'rbd://a5ae877c-bcba-53fe-8336-450e63014757/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', 'metadata': {'store': 'ceph'}}, {'url': 'rbd://a8d5f1f5-48e7-5ede-89ab-8aca59b6397b/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', 'metadata': {'store': 'dcn02'}}], 'direct_url': 'rbd://a5ae877c-bcba-53fe-8336-450e63014757/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/snap', 'tags': [], 'file': '/v2/images/acfd0a14-69e0-44d6-a6a1-aa9dc83e9d5b/file', 'stores': 'ceph,dcn02', 'properties': {'os_glance_failed_import': '', 'os_glance_importing_to_stores': '', 'owner_specified.openstack.md5': '', 'owner_specified.openstack.object': 'images/cirros', 'owner_specified.openstack.sha256': ''}}, 'image_service': <cinder.image.glance.GlanceImageService object at 0x7f8147973438>} I checked both glance and cinder containers are running in a healthy state. I see no errors or whatsoever. I am not sure how to fix the cinder volume stuck in the creating state in the DCN edge site. With regards, Swogat Pradhan

1 1

[neutron] detecting l3-agent readiness
by Mohammed Naser 22 Mar '23

22 Mar '23

Hi folks, I'm working on improving the stability of rollouts when using Kubernetes as a control plane, specifically around the L3 agent, it seems that I have not found a clear way to detect in the code path where the L3 agent has finished it's initial sync.. Am I missing it somewhere or is the architecture built in a way that doesn't really answer that question? Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

7 11