** Changed in: nova/zed
Status: In Progress => Won't Fix
** Changed in: nova/yoga
Status: In Progress => Won't Fix
** Changed in: nova/xena
Status: In Progress => Won't Fix
** Changed in: nova/wallaby
Status: In Progress => Won't Fix
--
You received this bug notific
Fix has been committed to openstack/nova but is not yet released for
stable/train. Release is proposed here:
https://review.opendev.org/c/openstack/releases/+/773074
** Changed in: nova/train
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a me
Fix has been committed but is not yet released. Release is proposed
here:
https://review.opendev.org/c/openstack/releases/+/773347
** Changed in: nova/ussuri
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I think either way, we would want a patch in glance as well, if it is
using the fsid from ceph.
(later)
Looking through the code, I found that such a change has already been
made:
https://github.com/openstack/glance_store/blob/6266ddf45f4d006cd7a8304224ec0ba0774489c1/glance_store/_drivers/rbd.py
** Changed in: nova
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816468
Title:
Acceleration cinder - glance with ceph not working
To manage notifications about
On the surface, it seems like this is something we could check for in
the libvirt driver and skip the soft reboot timeout cycle if ARM64. The
question I have is, which architecture fields does "ARM64" map to in
nova? ARMV6 or ARMV7 or ARMV7B or AARCH64 or all of them? Or one that I
missed? [1]
[1]
** Tags added: libvirt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748280
Title:
'nova reboot' on arm64 is just 'nova reboot --hard' but slower
To manage notifications about this bug go to:
http
Proposed patch: https://review.openstack.org/#/c/296543/
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) => Corey Wright (coreywright)
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Status: New
*** This bug is a duplicate of bug 1522402 ***
https://bugs.launchpad.net/bugs/1522402
At present, the only way to make the novaclient Python API work with
keystone v3 is to construct a keystoneclient Session object and pass it
to novaclient Client when creating the client object.
>From comme
** Changed in: nova
Assignee: melanie witt (melwitt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova comp
** Changed in: nova
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for quota-show
To manage notifications abo
I lack permission to remove horizon (Ubuntu), so moving back to New.
** Changed in: horizon (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
liv
This isn't really a bug, changing to Wishlist.
** Changed in: nova
Importance: Medium => Wishlist
** Changed in: nova
Status: In Progress => Confirmed
** No longer affects: horizon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Removing horizon as it has its own bug and patch up for this bug 1335999
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute ta
@Julie Thanks for linking the Horizon bug and review. That one will
solve the problem of live migrate not working at all through Horizon,
and it's anyway preferred to provide service host name. It won't however
change the fact that we can't use hypervisor_hostname as a migration
target argument. In
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310340
Title:
live migration fails when use long hostname of a nova compute target
** Changed in: python-novaclient
Importance: Undecided => Wishlist
** Changed in: python-novaclient
Status: New => Confirmed
** Changed in: python-novaclient
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
The documentation at http://developer.openstack.org/api-ref-
compute-v2.html#compute_images is incorrect for the
"GET/v2/{tenant_id}/images/detail" request parameter "type (Optional)"
It says "Value of the type of image, such as BASE, SERVER, or ALL." and
none of those are valid choices.
The va
This appears to be a documentation bug.
** Changed in: python-novaclient
Status: New => Invalid
** Also affects: openstack-api-site
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: python-novaclient
Importance: Undecided => Low
** Changed in: python-novaclient
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156932
Title:
User can
20 matches
Mail list logo
