Public bug reported:
Description
===
VIF unplug operations are failing on Rocky Linux 9.3 with stable/yoga.
This is caused by incompatibility between pyroute2 0.6.6 (yoga u-c) and
the Rocky Linux 9.3 kernel.
Steps to reproduce
==
* Launch a virtual machine
* Try to
Public bug reported:
Following an upgrade from Wallaby to Yoga of a Neutron OVN deployment, I
discovered that openstack-exporter would fail to return metrics for
Neutron agent states with the following error:
time="2023-02-23T10:49:33Z" level=error msg="Failed to collect metric
for exporter:
Public bug reported:
To adapt to updated DNS servers used by the OpenStack cloud, the
following option was used in ml2_conf.ini:
[ovn]
dns_servers = ,
However, instances (including new ones) are still getting the old DNS
servers from DHCP on a subnet with an empty dns_nameservers property.
I
Public bug reported:
Ussuri has the following code in nova/objects/service.py:
OLDEST_SUPPORTED_SERVICE_VERSION = 'Ussuri'
SERVICE_VERSION_ALIASES = {
'Ussuri': 41
}
This prevents Train compute hosts from joining a Ussuri control plane.
** Affects: nova
Importance: Undecided
** Changed in: nova
Status: Invalid => New
--
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/1956983
Title:
Consider making upgrade check for old computes a failure
*** This bug is a duplicate of bug 1952941 ***
https://bugs.launchpad.net/bugs/1952941
This should be resolved by
https://review.opendev.org/c/openstack/nova/+/820153
** This bug has been marked a duplicate of bug 1952941
Migration fails with "NotImplementedError: Cannot load 'pcpuset' in
Public bug reported:
Currently, the upgrade check for older than N-1 computes only produces a
warning.
For example:
Check: Older than N-1 computes
Result: Warning
Details: Current Nova version does not support computes older than
Victoria but the minimum compute service level in your
system
Public bug reported:
After upgrading a Neutron/ML2 OVS deployment from Ussuri to Victoria,
updating the host OS from CentOS Linux 8 to CentOS Stream 8, and
rebooting, DHCP was not functional on some but not all networks.
DHCP agent logs included the following error multiple times:
2021-11-30
Public bug reported:
Description
===
NUMA instances without hw:cpu_policy=dedicated set cannot be restarted after
upgrading from Ussuri to Victoria. The nova-compute service fails with the
following exception:
NotImplementedError: Cannot load 'pcpuset' in the base class
Steps to
Public bug reported:
Description
===
It is impossible to launch instances on freshly deployed hypervisors
with the following configuration:
[workarounds]
reserve_disk_resource_for_image_cache = True
nova-compute logs shows failures to update resources caused by the
Public bug reported:
We have a system with some dead DVR hypervisors. Ports of type
network:floatingip_agent_gateway are still associated with them and in
ACTIVE state. Deleting the L3 agent doesn't delete the ports, which
means extra floating IPs are still consumed.
* Version
OpenStack Train
Public bug reported:
I am trying to delete a nova-compute service for a retired hypervisor:
$ openstack compute service delete 124
Failed to delete compute service with ID '124': Service id 124 refers to
Public bug reported:
The stylesheet referenced in
openstack_dashboard/templates/serial_console.html is incorrect, as the
CSS file has been changed to SCSS in
I0d421d931d252d821a7ecf19a750f73b8241c249:
Instead, the template needs to reference the SCSS file and compile it.
** Affects:
This bug was mistakenly assigned to the Blazar project.
** Project changed: blazar => horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1643767
Title:
14 matches
Mail list logo
