I reproduced this issue but it sounds a cinder or cinderclient bug.
horizon uses Cinder API v3.0, so the change of
https://review.openstack.org/#/c/573093/ should not affect horizon.
I set the logging level of cinderclient in horizon to DEBUG and got the
following log:
Public bug reported:
/v3/limits POST method for "Create Limits"
When setting a domain-id for "project_id" in request body, it still
successfully creates a limit for the domain.
It is strange since we use a "project_id" to create limits for domain.
My test request was:
{
"limits":[
Reviewed: https://review.openstack.org/586059
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=314a06359e4eaa7a858f2ba88c98b0a849376aba
Submitter: Zuul
Branch:master
commit 314a06359e4eaa7a858f2ba88c98b0a849376aba
Author: Oleg Bondarev
Date: Thu Jul 26 16:01:09 2018
Reviewed: https://review.openstack.org/584365
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=2d532963fa2e013e16cc403f2674a4488c4170ab
Submitter: Zuul
Branch:master
commit 2d532963fa2e013e16cc403f2674a4488c4170ab
Author: Corey Bryant
Date: Fri Jul 20 09:01:56 2018
Please look at
https://github.com/openstack/neutron/blob/master/neutron/tests/unit/plugins/ml2/test_port_binding.py#L102.
This test case runs fine using 'host' default value. Yours is a corner
case in which not passing host + the fact that the port is owned by
compute produces and undesired
Public bug reported:
If you boot a virtual instance with UEFI, the UEFI NVRAM is lost on a
cold migration.
The default storage for the virtual UEFI NVRAM is in
/var/lib/libvirt/qemu/nvram/, and the file is not being copied over on
cold migration.
** Affects: nova
Importance: Undecided
Reviewed: https://review.openstack.org/574240
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4729fa819675ca511fe0027950d9aadf0aebef1b
Submitter: Zuul
Branch:master
commit 4729fa819675ca511fe0027950d9aadf0aebef1b
Author: Yikun Jiang
Date: Mon Jun 11 20:30:55 2018
Reviewed: https://review.openstack.org/585661
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=bef7e9a717f3bca45b5edd0ebc65ab1dde5942d9
Submitter: Zuul
Branch:master
commit bef7e9a717f3bca45b5edd0ebc65ab1dde5942d9
Author: Lucian Petrut
Date: Wed Jul 25 10:17:50 2018
Reviewed: https://review.openstack.org/588097
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=3cd5198d5a767566e3cbba5a33ac4a7ae3d53aef
Submitter: Zuul
Branch:master
commit 3cd5198d5a767566e3cbba5a33ac4a7ae3d53aef
Author: Matt Riedemann
Date: Wed Aug 1 18:51:31 2018
Public bug reported:
https://review.openstack.org/574582
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/glance" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
Public bug reported:
The information in doc/source/reference/rpc.rst is stale and should
probably be updated or removed so that it doesn't confuse people.
** Affects: nova
Importance: Undecided
Status: New
** Tags: docs
--
You received this bug notification because you are a
** Changed in: nova
Importance: Medium => Low
** Changed in: nova
Status: Confirmed => Opinion
--
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/1420662
Title:
Bug 1488111 is what I was thinking about, but Lee clarified the issue
for me. The scenario is like:
1. spawn on host1 fails, reschedule to host2
2. prep_block_devices fails on host2 because of the volume attachment issue
mentioned
** Also affects: nova/queens
Importance: Undecided
Reviewed: https://review.openstack.org/588096
Committed:
https://git.openstack.org/cgit/openstack/networking-powervm/commit/?id=59fbf0a3b6f14d54a0369408a8bc6bb2ad9df874
Submitter: Zuul
Branch:master
commit 59fbf0a3b6f14d54a0369408a8bc6bb2ad9df874
Author: Matthew Edmonds
Date: Wed Aug 1
Reviewed: https://review.openstack.org/587922
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=99db9faae5c1e84e5aa8586c32ffcca7a61ae276
Submitter: Zuul
Branch:master
commit 99db9faae5c1e84e5aa8586c32ffcca7a61ae276
Author: Dan Smith
Date: Wed Aug 1 10:16:41 2018 -0700
Public bug reported:
Description
===
After creating a volume which resulted with status = "error", an attempt to
attach the volume to VM will fail and will change the volume status to -
"available".
Steps to reproduce
==
1. Create volume with status = "error".
2. Try to
Public bug reported:
Description
===
When doing live-migration, if a host that does not exist or cannot be found is
specified as destination, live-migration will fail and instance will get stuck
in status "migrating".
Steps to reproduce
==
nova live-migration vm
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [x] This doc is inaccurate in this way: __
In below part of document:
"Use the database access client
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [X] This doc is inaccurate in this way: __
In below section "Add the compute node to the cell
19 matches
Mail list logo
