[Yahoo-eng-team] [Bug 2049559] [NEW] Keysont implements "AccountLocked" but returns "Unauthorized"

Public bug reported: We enabled [security_compliance] in our environment to follow Security compliance and PCI-DSS requirements, and here is our configuration: [security_compliance] lockout_failure_attempts = 3 lockout_duration = 60 My account will be get locked after 3 failure logins, then I tr

[Yahoo-eng-team] [Bug 2049546] Re: neutron-linuxbridge-agent ebtables RULE_DELETE failed (Invalid argument)

*** This bug is a duplicate of bug 2038541 *** https://bugs.launchpad.net/bugs/2038541 This was fixed with https://review.opendev.org/c/openstack/neutron/+/898832 and is a duplicate of https://bugs.launchpad.net/neutron/+bug/2038541 - please try the fix there. ** This bug has been marked a du

[Yahoo-eng-team] [Bug 2049546] [NEW] neutron-linuxbridge-agent ebtables RULE_DELETE failed (Invalid argument)

Public bug reported: neutron-linuxbridge-agent fails and gets stuck when cleaning up ARP protection rules: neutron-linuxbridge-agent[3049824]: Exit code: 4; Cmd: ['ebtables', '-t', 'nat', '--concurrent', '-D', 'neutronMAC-tap50f1af99-28', '-i', 'tap50f1af99-28', '--among-src', 'fa:16:3e:ba:1

[Yahoo-eng-team] [Bug 2049120] Re: Unable to upgrade nova-compute to 2023.1 due to existing hostname

Thanks for the information. It looks like there was a change to /etc/hosts between upgrades that caused the name change. We should be able to either revert that change or remove/reregister these nodes. ** Changed in: nova Status: Incomplete => Invalid -- You received this bug notificati

[Yahoo-eng-team] [Bug 1978489] Re: libvirt / cgroups v2: cannot boot instance with more than 16 CPUs

** Also affects: nova (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bu

[Yahoo-eng-team] [Bug 2049524] [NEW] [Neutron/Nova] Need to fix attaching a vip port on VMs

Public bug reported: >From https://bugs.launchpad.net/neutron/+bug/2018529 Community had raised a fix in A release. But nova can still attach the vip port on VM without failure, even the vip port can not be used.. We can repro it in Neutron A release and OVN based deployment, relied on #2018529

[Yahoo-eng-team] [Bug 2049488] Re: [ovn][source-main] job fails with error: too many arguments to function flow_compose

Reviewed: https://review.opendev.org/c/openstack/neutron/+/905645 Committed: https://opendev.org/openstack/neutron/commit/70f9dd926f7433569df59c2f309f4239b8e8e7c9 Submitter: "Zuul (22348)" Branch:master commit 70f9dd926f7433569df59c2f309f4239b8e8e7c9 Author: yatinkarel Date: Tue Jan 16 13

[Yahoo-eng-team] [Bug 2049488] [NEW] [ovn][source-main] job fails with error: too many arguments to function flow_compose

Public bug reported: Fails as:- 2024-01-16 03:02:53.651183 | controller | gcc -DHAVE_CONFIG_H -I. -I ./include -I ./include -I ./ovn -I ./include -I ./lib -I ./lib -I /opt/stack/ovs/include -I /opt/stack/ovs/include -I /opt/stack/ovs/lib -I /opt/stack/ovs/lib -I /opt/stack/ovs -I /opt/stack/