I think this is not an issue with nova but the one with puppet-nova.
Actually we fixed the configration related to libvirt on CentOS while we
fixed that mentioned bug, but we still need the same fix for Ubuntu
which has libvirt 6.0 recently.
We already have a proposed fix for the issue
https://re
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Public bug reported:
Failure statement : LB health monitor deletion fails with exception
"Server-side error: "'NoneType' object has no attribute
'load_balancer_id'"
Test executed : 1) Create LB, Virtual servers (HTTP & HTTPS), Pool, Members &
Health monitors
2) Delete LB objects
** Changed in: nova/rocky
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).
https://bugs.launchpad.net/bugs/1806064
Title:
Volume remains in attaching/reserved
Public bug reported:
I´m trying to configure dynamic routing, but when I associate provider
network with the bgp speaker I start to receive these errors:
2020-10-05 16:56:13.028 2304845 ERROR oslo_messaging.rpc.server Traceback (most
recent call last):
2020-10-05 16:56:13.028 2304845 ERROR oslo_
This bug was fixed in the package nova -
2:22.0.0~b3~git2020091410.76b2fbd90e-0ubuntu3~cloud0
---
nova (2:22.0.0~b3~git2020091410.76b2fbd90e-0ubuntu3~cloud0) focal-victoria;
urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
nova (2:22.0.0~b3~git2020091410.76b2fbd90
Public bug reported:
We added support for the 'mixed' CPU policy in Victoria. This required
changes to the 'cpu_policy' field of the 'InstanceNUMACell' object. As
part of that change, we had to check that the consumer of the o.vo
supported the 'mixed' policy and, if not, raise an 'ObjectActionErro
Public bug reported:
hello,
after upgrading from Openstack Train to Ussuri, running on Ubuntu 18.04,
the nova-compute service doesn't start due to the libvirtd service not
starting because of the --listen option being enabled in the
/etc/default/libvirtd file and so, the nova-compute service fail
Reviewed: https://review.opendev.org/722415
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e7e71b2ca67169e6de4cdad71f2c82059132325d
Submitter: Zuul
Branch:master
commit e7e71b2ca67169e6de4cdad71f2c82059132325d
Author: Rodolfo Alonso Hernandez
Date: Tue Apr 21 14:53
This looks like a bug of CentOS package. The horizon bug tracker is not
a place to report a packaging bug. Please file it to the CentOS 8 bug
tracker.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, w
10 matches
Mail list logo
