Since we are using Yoga and hitting this issue I had a go at reverting
the patch there too and can confirm that it does resolve the problem.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/antelope
Importance: Undecided
Status:
Thanks for flagging the potential security impact of this. Can someone
provide a succinct exploit scenario for how an attacker might cause this
to occur and then take advantage of it? Or is it merely one of those
situations where someone could take advantage of the issue if they
happen to find an
This issue was fixed in the openstack/nova 26.2.1 release.
** Changed in: nova/zed
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This issue was fixed in the openstack/nova 26.2.1 release.
** Changed in: nova/zed
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Reviewed: https://review.opendev.org/c/openstack/nova/+/900831
Committed:
https://opendev.org/openstack/nova/commit/fa3cf7d50cba921ea67eb161e6a199067ea62deb
Submitter: "Zuul (22348)"
Branch:master
commit fa3cf7d50cba921ea67eb161e6a199067ea62deb
Author: Jay Faulkner
Date: Mon Nov 13
Public bug reported:
when doing live migrations for bfv instances the disk remaining in the
nova log says 100 even if there is no disk to migrate
** Affects: nova
Importance: Undecided
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
if an operator has a compute node and reinstalls it but forget to do a
"openstack compute service delete " first (that would wipe the nova-
compute service record and the resource provider in placement) the
reinstalled compute node with the same hostname happily reports it's
Public bug reported:
Neutron 2023.1 29cc1a634e530972614c09fbb212b5f63fd4c374
Ubuntu 20.04
This issue has been identified in a Neutron system running Linux Bridge
networking, but whilst this may no longer be supported I'm posting it in
case the same issue might be relevant for other drivers.
Fixed by https://review.opendev.org/c/openstack/nova/+/899406/2
** Changed in: nova
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2027975
Title:
Add check on network interface name's length
Status in
Public bug reported:
Problem Statement: Creating VM from image work fine, but reboot of that
instance from openstack results in Error state.
Steps to re-create:
1. Create a VM from Openstack with Image as the source. VM is created
successfully.
2. Now issue a openstack server reboot
3.
11 matches
Mail list logo