f0o | After adding a bunch of more hypervisors I ran into some "fun" situation; I now have Two "nova" availability zones and it seems that at least Neutron is entirely confused by this telling me that it cannot find Nova AZ (likely because it finds 2!) | 11:10 |
---|---|---|
f0o | Is there a better way to rectify this than grep'ing through the SQL to determine what needs to be merged into what AZ? | 11:11 |
f0o | or am I barking at the wrong tree? | 11:11 |
f0o | "openstack availability zone list --network" is deffo empty... | 11:36 |
f0o | did something change from 2024.1 to 2024.2 in that regard? | 11:36 |
f0o | https://paste.opendev.org/show/bFNbzc0iI542ugQCvxno/ << from release notes - it deffo affects single-az setups | 11:37 |
f0o | https://github.com/openstack/openstack-ansible-os_neutron/blob/70bb847605b3002c58802511eeec99193d0f9220/tasks/providers/setup_ovs_ovn.yml#L25 << this wasnt applied it seems | 11:42 |
f0o | at least for me there's no availability-zone entry | 11:42 |
jrosser | it would be super helpful if you coule see if that task runs at all | 11:46 |
jrosser | and submit a bug if something looks wrong | 11:46 |
f0o | ok it _was_ applied but it seems that I accidentally overrid it when I was debugging the OVN LRP distribution issue yesterday evening in #openstack-neutron because I reapplied the ovn-cms-options=enable-chassis-as-gw cmd which removed the az attribute | 11:48 |
f0o | https://docs.openstack.org/networking-ovn/latest/admin/refarch/provider-networks.html << 'ovs-vsctl set open . external-ids:ovn-cms-options="enable-chassis-as-gw"' dangerous with the AZ change | 11:49 |
f0o | might be safer to have a custom attribute instead of chaining it to ovn-cms-options but I guess that's a bigger change for neutron to do | 11:53 |
f0o | I need to stop tinkering with things on the weekends | 11:54 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!