[Yahoo-eng-team] [Bug 1248022] Re: Nova scheduler not updated immediately when a baremetal node is added or removed

** Changed in: ironic Status: Triaged => Opinion ** Changed in: ironic Importance: Medium => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1248022

[Yahoo-eng-team] [Bug 1489059] Re: "db type could not be determined" running py34

** Changed in: ironic-lib Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1489059 Title: "db type could not be

[Yahoo-eng-team] [Bug 2033083] Re: [OVN] The router GW is "restoring" the NAT rule that disables SNAT

Marking invalid, this is how it worked with OVS as well, it just means we can't pass TFTP traffic through OVN. ** 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.

[Yahoo-eng-team] [Bug 2028003] [NEW] neutron fails with postgres on subnet_id

Public bug reported: Ironic's postgres CI test job has started to fail with an error rooted in Neutron's database API layer. Specifically how that API is interacting with SQLAlchemy to interact with postgres. Error: DBAPIError exception wrapped.: psycopg2.errors.GroupingError: column

[Yahoo-eng-team] [Bug 2026757] [NEW] dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

Public bug reported: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds

[Yahoo-eng-team] [Bug 1925388] Re: Incorrect reference to 802.1ad in network_data.json schema

** Changed in: ironic Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1925388 Title: Incorrect reference to 802.1ad in network_data.json

[Yahoo-eng-team] [Bug 1982489] [NEW] keystoneauth dependencies appear broken

Public bug reported: Using python 3.8.5 on Debian, trying to run tox commands, it appears the test-requirements.txt defines ranges of packages. Even with an upgraded pip, although it seems to default to by base os pip of 22.1.2, dependency resolution takes 30+ minutes. Updating hacking, certifi,

[Yahoo-eng-team] [Bug 1944201] [NEW] neutron-openvswitch-agent crashes on start with firewall config of br-int

Public bug reported: In upstream CI, Ironic jobs have been encountering failures where we never find the networking to be stood up by neutron. Investigation into what was going on led us to finding the neutron-openvswitch-agent in failed state, exited due to RuntimeError, just a few seconds after

[Yahoo-eng-team] [Bug 1766301] [NEW] ironic baremetal node ownership not checked with early vif plugging

ss scheduling by flavor disabled which will result in a high liklihood that the same physical baremetal node will be selected. This can be preproduced fairly easily with TripleO and a lack of a resource class defined on the flavor. ** Affects: nova Importance: Undecided Assignee: Julia

[Yahoo-eng-team] [Bug 1682222] Re: Instance deployment failure due to neutron syntax error

Thank you! This bug seems like it is more appropriate for the ironic project. I'm unable to a access the URL you posted a link to. If you could post ir-cond.log to the bug, It would assist in context and a allow us to better understand exactly what occurred. Again, Thank you. -Julia ** Also

[Yahoo-eng-team] [Bug 1391699] [NEW] nova vm networking failed to initialize as step after interface creation failed.

Public bug reported: On a juno-2 TripleO based system, after performing a node upgrade via `nova rebuild`, we encountered an issue where some virtual machines were unreachable. Upon further investigation, we found that the OVS VIF was missing, and the root cause was that the re-creation failed