** Also affects: nova/train
Importance: Undecided
Status: New
** No longer affects: nova/trunk
--
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/1885528
Title:
s
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
** Also affects: nova/victoria
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
En
** Also affects: nova/wallaby
Importance: Undecided
Status: 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/1851545
Title:
Port update exception on nova uns
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Also affects: nova/wallaby
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/ussuri
Importance: Undecided
Status: New
-
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
** Also affects: nova/victoria
Importance: Undecided
Status: New
** Also affects: nova/wallaby
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https:/
Public bug reported:
we are having 2 compute nodes and we want to
those 2 compute nodes using nfs to share disk so there are 3 resource providers
compute node1 for cpu/mem
compute node2 for cpu/mem
disk pool for shared storage
now we want to live migrate the VM from compute 1 to compute 2
it'
This bug was fixed in the package neutron - 2:16.3.2-0ubuntu3
---
neutron (2:16.3.2-0ubuntu3) focal; urgency=medium
* d/p/revert-rely-on-worker-count-for-hashring-caching.patch: Revert
patch from 16.3.2 due to SR-IOV regression (LP: #1931244).
-- Corey Bryant Tue, 08 Jun 202
This bug was fixed in the package neutron - 2:18.0.0-0ubuntu2.1
---
neutron (2:18.0.0-0ubuntu2.1) hirsute; urgency=medium
* d/gbp.conf: Create stable/wallaby branch.
* d/p/revert-rely-on-worker-count-for-hashring-caching.patch: Revert
patch due to SR-IOV regression (LP: #19312
This bug was fixed in the package neutron - 2:18.0.0-0ubuntu2.1
---
neutron (2:18.0.0-0ubuntu2.1) hirsute; urgency=medium
* d/gbp.conf: Create stable/wallaby branch.
* d/p/revert-rely-on-worker-count-for-hashring-caching.patch: Revert
patch due to SR-IOV regression (LP: #19312
Reviewed: https://review.opendev.org/c/openstack/neutron/+/794236
Committed:
https://opendev.org/openstack/neutron/commit/cc3dc7c8508a142b614ee9cfe3f4a6766f62d8b8
Submitter: "Zuul (22348)"
Branch:master
commit cc3dc7c8508a142b614ee9cfe3f4a6766f62d8b8
Author: Rodolfo Alonso Hernandez
Date:
Hi, looks like you are not using the horizon master branch. This bug is
already fixed by
https://review.opendev.org/c/openstack/horizon/+/777654.
Feel free to backport it if you are using an old branch.
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notificat
Hi, Could you please check the format of policy files under ``POLICY_FILES``
[1] for both nodes.
looking at the logs for the first node you are using '.json' format that's why
you are seeing
those deprecation warnings and for node2 maybe you are using '.yaml' format
that's why you are
only seein
Reviewed: https://review.opendev.org/c/openstack/nova/+/796269
Committed:
https://opendev.org/openstack/nova/commit/e59fc77c3d924cfab6ddcd780ae0604a84e64c30
Submitter: "Zuul (22348)"
Branch:master
commit e59fc77c3d924cfab6ddcd780ae0604a84e64c30
Author: Balazs Gibizer
Date: Mon Jun 14 14:0
Reviewed: https://review.opendev.org/c/openstack/nova/+/796319
Committed:
https://opendev.org/openstack/nova/commit/b02a95a18b5da37db6d4f30a5dea07e2a4187245
Submitter: "Zuul (22348)"
Branch:master
commit b02a95a18b5da37db6d4f30a5dea07e2a4187245
Author: Mohammed Naser
Date: Mon Jun 14 16:5
Public bug reported:
I just realized that we have submitted a spec [0] without following the
Neutron RFE process [1].
I'll repeat the summary here:
Off-path SmartNIC DPUs introduce an architecture change where network
agents responsible for NIC switch configuration and representor
interface plug
After looking into errors in case description and logs in comment #4,
both seems to fail waiting for sb_idl object.
AttributeError: 'MetadataProxyHandler' object has no attribute 'sb_idl'
AttributeError: 'MetadataAgent' object has no attribute 'sb_idl'
Once the failure is in MetadataAgent proces
Public bug reported:
Reproduction scenario:
- create a large base image (50 GB or so). This could be done for example by
creating a VM, filling its ephemeral storage (which is 50 GB in our case) with
lots of junk data, shutting down the VM, and creating an image from that.
- create a VM based o
Public bug reported:
Description
===
So far, the soft-deleted instance can not be evacuated.
When the node can not be fixed or exceed the reclaim window,
the instance can not be restored for ever.
Steps to reproduce
==
* Set `reclaim_instance_interval` to 300s, and restart
20 matches
Mail list logo