Public bug reported:
1.execute nova live-migtation $instance_id $dest_host(I use rocky-em version)
2.execute nova instance-action-list $instance_id to get the last operation
request_id as req-xxx
3.check the log with req-xxx key word at source host, I find the log lines has
no request_id
** Changed in: nova
Status: Incomplete => Invalid
--
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/1964587
Title:
default video driver
Status in OpenStack Compute
Public bug reported:
If the port binding is being changed while Neutron keeps changing the
port binding because ovn controller starts claiming the port bindings
then the db sync script may fail:
2022-02-12 18:23:02.332 47 CRITICAL neutron_ovn_db_sync_util
Reviewed: https://review.opendev.org/c/openstack/neutron/+/831214
Committed:
https://opendev.org/openstack/neutron/commit/820b2e26658a3fb5e00a7cedbdc2418d2196aa42
Submitter: "Zuul (22348)"
Branch:master
commit 820b2e26658a3fb5e00a7cedbdc2418d2196aa42
Author: yatinkarel
Date: Mon Feb 28
This fix in Jammy 22.1-14-g2e17a0d6-0ubuntu1~22.04.1 also had an unintended
side-effect where network would not get rendered due and newly launched
instnaces on Jammy were unreachable due to
cloud-init networking being configured as disabled in Oracle images
This fix for this is merged [1] and released to ill update the status
accordingly.
[1]
https://github.com/openstack/neutron/commit/91eb3d8346a8964aa046d1e016d571056de868de
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a
The issue looks exactly to the one reported here
https://bugs.launchpad.net/neutron/+bug/1958964. It was fixed in
https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826257
** Changed in: neutron
Assignee: (unassigned) => Fernando Royo (froyoredhat)
** Changed in: neutron
*** 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
The issue seems to be in ovs, specifically this commit
https://github.com/openvswitch/ovs/commit/355fef6f2ccbcf78797b938421cb4cef9b59af13
. I have created a ppa
https://launchpad.net/~gnuoy/+archive/ubuntu/focal-xena/+packages that
has a copy of the openvswitch package from the xena-proposed UCA.
Public bug reported:
Hello, I saw on amd64 platform nova defaults to use cirrus as video
driver and windows virtual machine got a small resolution.
video driver virtio could allow a larger resolution. And looks like the
driver type cannot be set by user.
My question is why using cirrus as
Public bug reported:
Description
===
When create server API fails because of no valid host, the instance's
status goes into ERROR, and then users delete the instance by delete
server API. After that, users query the instances by list server API,
the deleted error instance is still there
Public bug reported:
I found two block device mappings (bdm) for a volume (mulitattach is
off). Also I am not quite sure where the second bdm is coming from.
Additionaly one of the bdm has no attachment_id.
When detaching the volume it is possible that nova deletes the wrong
attachment, because
Public bug reported:
This is a container for the efforts to be done in Neutron, neutron-lib
and plugins projects to migrate to SQLAlchemy 2.0.
There is currently a patch in neutron-lib to disable the session
"__autocommit" flag, that will be optional in SQLAlchemy 1.4 and
mandatory in SQLAlchemy
13 matches
Mail list logo
