[Yahoo-eng-team] [Bug 2045888] [NEW] Availability zone is not shown when aggregate does not contain any host

Public bug reported: I'm using openstack yoga. The API responce for get availability zones is not consistent. When host aggregate with availability zone is present but does not contain any hosts the availability zone will not be shown at API. heat@keystone-client-558fdf8468-7m9ml:/$ openstack agg

[Yahoo-eng-team] [Bug 2045889] [NEW] [OVN] ML2/OVN mech driver does not set the OVS bridge name in the port VIF details

Public bug reported: The ML2/OVN mech driver does not set the OVS bridge name nor the datapath type in the Neutron DB port VIF details. Example of an ML2/OVS port: """ binding_vif_details: bound_drivers.0='openvswitch', bridge_name='br-int', connectivity='l2', datapath_type='system', ovs_hybrid_

[Yahoo-eng-team] [Bug 2045921] [NEW] scheduler.utils.set_vm_state_and_notify() race between ERROR state save() and compute_utils.add_instance_fault_from_ex()

Public bug reported: Maybe "race" isn't the right word, but the ordering of the Instance.save() of ERROR state and the creation of the instance.fault record can result in the instance.fault not having been created yet after the instance is visibly showing ERROR state. Seen in the gate: test_qos_

[Yahoo-eng-team] [Bug 2029335] Re: [centos-9-stream] jobs fails as nova-compute stuck at libvirt connect since systemd-252-16.el9

Marking invalid, impacted Ironic but fix was in devstack. ** Changed in: ironic Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2029335 Title: [centos-9-str

[Yahoo-eng-team] [Bug 2045950] [NEW] Security group performance issue for iptables driver due to "stateless feature"

Public bug reported: There is a huge performance issue with the security groups when using the iptables implementation: If you have a security group with say 500 rules it will take minutes for the RPC server to create the the port configuration. You will see this when you restart the neutron-lin