[Yahoo-eng-team] [Bug 1552042] Re: Host data corruption through nova inject_key feature

The fix merged to master https://review.opendev.org/c/openstack/nova/+/324720 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1919357] Re: "Secure live migration with QEMU-native TLS in nova"-guide misses essential config option

** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Josephine Seifert (josei) ** Changed in: nova Importance: Undecided => High ** Also affects: nova/stein Importance: Undecided Status: New ** Also affects: nova/victoria

[Yahoo-eng-team] [Bug 1917409] Re: neutron-l3-agents won't become active

*** This bug is a duplicate of bug 1883089 *** https://bugs.launchpad.net/bugs/1883089 ** This bug has been marked a duplicate of bug 1883089 [L3] floating IP failed to bind due to no agent gateway port(fip-ns) -- You received this bug notification because you are a member of Yahoo!

[Yahoo-eng-team] [Bug 1885528] Re: snapshot delete fails on shutdown VM

** Also affects: nova/rocky Importance: Undecided Status: New ** Also affects: nova/queens Importance: Undecided Status: New ** Also affects: nova/ussuri Importance: Undecided Status: New ** Also affects: nova/victoria Importance: Undecided Status: New

[Yahoo-eng-team] [Bug 1918250] Re: live migration is failing with libvirt >= 6.8.0

@Martin: You reported this against the upstream nova project but you are linking to the RDO specific nova wrapper code. Is the reported problem really affects the upstream nova project? I'm marking this Invalid from upstream nova perspective. If you disagree then please set it back to New and

[Yahoo-eng-team] [Bug 1886855] Re: Insufficient error handling when parsing iscsiadm -m node output with blank iscsi target

** No longer affects: nova -- 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/1886855 Title: Insufficient error handling when parsing iscsiadm -m node output with blank

[Yahoo-eng-team] [Bug 1907756] Re: ERROR: No matching distribution found for hacking<3.1.0, >=3.0.1

** Changed in: nova Status: In Progress => Fix Released -- 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/1907756 Title: ERROR: No matching distribution found for

[Yahoo-eng-team] [Bug 1896621] Re: instance corrupted after volume retype

https://review.opendev.org/c/openstack/nova/+/758732 has been released in ussuri 21.2.0 ** Changed in: nova/ussuri Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1919487] [NEW] virDomainBlockCommit called when deleting a snapshot via os-assisted-volume-snapshots even when instance is shutoff

Public bug reported: Description === Attempting to delete a NFS volume snapshot (via c-api and the the os- assisted-volume-snapshots n-api) of a volume attached to a SHUTOFF instance currently results in n-cpu attempting to fire off a virDomainBlockCommit command even though the instance

[Yahoo-eng-team] [Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

FWIW I know what the snapd issue is, the issue is that snapd does not and will not work in a nested LXD container, we need to add code to make snapd.seeded.service die/exit gracefully in this situation. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd

[Yahoo-eng-team] [Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

it's interesting that apparmor appears to work ok in the first-level container, but fails in the nested container, e.g.: $ lxc shell lp1905493-f root@lp1905493-f:~# systemctl status apparmor ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service;

[Yahoo-eng-team] [Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

The systemd-logind problem is due to dbus defaulting to apparmor mode 'enabled', but apparmor can't do much of anything inside a container so it fails to start, and dbus can't contact it. In the 2nd level container, create a file like '/etc/dbus-1/system.d/no- apparmor.conf' with content:

[Yahoo-eng-team] [Bug 1919386] Re: Project administrators are allowed to view networks across projects

Fix merged in neutron-lib. ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1919386 Title: Project administrators are

[Yahoo-eng-team] [Bug 1552042] Re: Host data corruption through nova inject_key feature

Thanks for following up on this longstanding report. Given the fix is unlikely to be backported to supported stable branches, the VMT considers such reports class B1 ( https://security.openstack.org/vmt- process.html#incident-report-taxonomy ) so there's no call for issuing an advisory. **

[Yahoo-eng-team] [Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

Yep, that's what I've found; cloud-init is just waiting for its later stages to run, which are blocked by snapd.seeded.service exiting. ** Changed in: cloud-init Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1905701] Re: Do not recreate libvirt secret when one already exists on the host during a host reboot

https://review.opendev.org/c/openstack/nova/+/765769 proposed to stable/victoria ** Also affects: nova/queens Importance: Undecided Status: New ** Also affects: nova/rocky Importance: Undecided Status: New ** Also affects: nova/trunk Importance: Undecided Status: