[Yahoo-eng-team] [Bug 1933416] Re: loadbalancer create error

Please reports this to the Octavia project via their storyboard project below: https://docs.openstack.org/octavia/latest/contributor/contributing.html#reporting-a-bug https://storyboard.openstack.org/#!/project/openstack/octavia ** Changed in: nova Status: New => Invalid -- You

[Yahoo-eng-team] [Bug 1933417] Re: loadbalancer create error

Please reports this to the Octavia project via their storyboard project below: https://docs.openstack.org/octavia/latest/contributor/contributing.html#reporting-a-bug https://storyboard.openstack.org/#!/project/openstack/octavia ** Changed in: nova Status: New => Invalid -- You

[Yahoo-eng-team] [Bug 1921306] Re: When Instance is paused state, live migration failure.

This smells like a known QEMU issue that we encountered in CI a while ago causing the underlying guest to crash: [QEMU] Back-n-forth live migration of a paused VM results in QEMU crash with: "bdrv_inactivate_recurse: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed."

[Yahoo-eng-team] [Bug 1933418] Re: loadbalancer create error

Please reports this to the Octavia project via their storyboard project below: https://docs.openstack.org/octavia/latest/contributor/contributing.html#reporting-a-bug https://storyboard.openstack.org/#!/project/openstack/octavia ** Changed in: nova Status: New => Invalid -- You

[Yahoo-eng-team] [Bug 1934937] Re: Heartbeat in pthreads in nova-wallaby crashes with greenlet error

** 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/1934937 Title: Heartbeat in pthreads in nova-wallaby crashes with greenlet error Status in

[Yahoo-eng-team] [Bug 1902276] Re: libvirtd going into a tight loop causing instances to not transition to ACTIVE

What do we want to do with this bug? Ultimately the underlying issue is with the version of libvirt shipped in Bionic that's outside of our control. Should we move the bug to the libvirt component and ask the Ubuntu team if a rebase is even feasible? ** Also affects: libvirt Importance:

[Yahoo-eng-team] [Bug 1934135] Re: nova cannot create instances, because it doesn't find the network

Can you look for req-272816ee-1601-4ed2-95e0-a9119c6af1a1 in your neutron logs? That's the request from Nova to Neutron that failed for you, tracing that request-id through the logs should show you why the request failed. ** Also affects: neutron Importance: Undecided Status: New **

[Yahoo-eng-team] [Bug 1916052] Re: Unable to create trust errors in glance-api

** Also affects: glance/wallaby Importance: Undecided Status: New ** Changed in: glance/victoria Status: Fix Released => In Progress ** Changed in: glance/wallaby Status: New => In Progress ** Changed in: glance/wallaby Importance: Undecided => High ** Also affects:

[Yahoo-eng-team] [Bug 1885928] Re: Unable to spawn VM from community image

** Changed in: glance Status: New => Triaged ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Also affects: glance/victoria Importance: Undecided Assignee: Erno Kuvaja (jokke) Status: Triaged ** Also affects: glance/xena Importance: Undecided

[Yahoo-eng-team] [Bug 1926404] Re: HTTP 413 : Failed to add object to Swift. Got error from Swift

** Changed in: glance Status: New => Triaged ** Changed in: glance Importance: Undecided => High ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High Status: Triaged ** Also affects: glance/xena

[Yahoo-eng-team] [Bug 1925368] Re: [L3] Router GW can be updated without checking router routes

Reviewed: https://review.opendev.org/c/openstack/neutron/+/789929 Committed: https://opendev.org/openstack/neutron/commit/5fb5653ffe700a8f9fb0949d16ecbf0978b61fb6 Submitter: "Zuul (22348)" Branch:master commit 5fb5653ffe700a8f9fb0949d16ecbf0978b61fb6 Author: Rodolfo Alonso Hernandez Date:

[Yahoo-eng-team] [Bug 1927872] Re: Cannot encode a text script as base64 in write_files

[Expired for cloud-init because there has been no activity for 60 days.] ** Changed in: cloud-init Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init.