** Changed in: nova
Importance: Undecided => High
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Triaged
** Changed in: nova/queens
Importance: Undecided => High
--
You received this bug notification because you
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Assignee: (unassigned) => Elod Illes (elod-illes)
** Changed in: nova/queens
Assignee: (unassigned) => Balazs
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Fix Committed
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in:
Public bug reported:
Blueprint https://blueprints.launchpad.net/nova/+spec/optional-
placement-database added support for configuring a separate database for
the placement service so it's not just part of the nova_api database
(even though it's the same schema for now).
This is important for
Everything goes through nova-conductor for database updates so if that's
down, you have problems. You can reset the state of the instance using
the reset state API (as admin):
https://docs.openstack.org/python-openstackclient/latest/cli/command-
objects/server.html#server-set
nova server set
This is already fixed in master (rocky) and stable/queens:
https://review.openstack.org/#/q/I5c0a6389b759153bae06fa43846f03ac083c3db4
** Changed in: nova
Status: New => Fix Released
** Changed in: nova
Assignee: (unassigned) => caoyuan (cao-yuan)
--
You received this bug
This isn't a nova bug. Check your db configuration, maybe you have too
many open connections or the host running the db is overwhelmed.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: nova/pike
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/1777129
Title:
live migration doc says
Public bug reported:
I noticed this from the nova-compute logs attached to bug 1777157:
2018-06-15 16:23:46.954 7 ERROR nova.compute.manager
[req-69050681-be73-48c5-be25-993f05b0b47e e511323a68a740f597880a1b056e3918
28f4e0797d544d758700e5be42aa82c6 - default default] [instance:
Something is wrong with your configuration, there is no RPC API call
during validate_networks from the API if you're using neutron. Only
nova-network would have an RPC API call for validate_networks. Are you
using nova-network? If not, you should have use_neutron=True in
nova.conf.
** Changed in:
What is the error from the nova-api logs?
** Changed in: nova
Status: New => Incomplete
** 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).
Typo in the bug description, it's not "amdb-no-ssb" it's amd-no-ssb.
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
**
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova
Importance: High => Medium
--
You received this bug notification because you
d.txt%5C%22=7d
275 hits in 24 hours, all failures.
We need to just skip the test in the cells v1 job:
https://review.openstack.org/#/c/576194/
** Affects: nova
Importance: Critical
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Tags: api cells
** Changed in:
://review.openstack.org/#/c/575556/
then it's a 500 error.
** Affects: nova
Importance: High
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Tags: api regression
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
You received this bug notification beca
must be
called with LVM instance as first argument (got str instance instead)
Jun 15 18:35:04.327643 ubuntu-xenial-inap-mtl01-165445 nova-compute[1555]:
ERROR oslo_messaging.rpc.server
Looks like it's due to this:
https://review.openstack.org/#/c/565703/
http://logstash.openstack.org/
Public bug reported:
These warnings are over the nova-api logs in the reference CI job:
http://logs.openstack.org/10/515210/39/check/barbican-simple-crypto-
devstack-
tempest/7b7f049/logs/screen-n-api.txt.gz?level=TRACE#_Jun_15_18_30_55_364299
Jun 15 18:30:55.364299
Public bug reported:
Due to a change in zuul:
http://lists.openstack.org/pipermail/openstack-dev/2018-June/131304.html
ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa is now
running on non-code changes in nova because of how it's defined on nova
in project-config:
Restored the tempest revert: https://review.openstack.org/#/c/575132/
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Status: New => In Progress
** Changed in: tempest
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in
** No longer affects: tempest
--
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/1776684
Title:
MultipleCreateTestJSON.test_multiple_create intermittently fails for
cells
This is likely the reason for the failure, cells v1 doesn't honor that
multi-create instance name contract:
https://github.com/openstack/nova/blob/dd87118acc2bf57f235cb287ed0ee12736263ecb/nova/compute/api.py#L1419
** Also affects: tempest
Importance: Undecided
Status: New
--
You
Public bug reported:
http://logs.openstack.org/75/486475/38/gate/nova-cells-v1/2c2a566/job-
output.txt.gz#_2018-06-13_13_26_17_075329
2018-06-13 13:26:17.110798 | primary | Captured traceback:
2018-06-13 13:26:17.110851 | primary | ~~~
2018-06-13 13:26:17.110932 | primary |
Public bug reported:
The API reference for the rebuild server action does not mention the
preconditions required for rebuild a server, which are pretty basic:
https://developer.openstack.org/api-ref/compute/#rebuild-server-rebuild-
action
Public bug reported:
The alternative hosts calculation code in the scheduler (since Queens)
uses max_attempts incorrectly, as if it's max_retries, but max_attempts
can be set to 1 meaning no retries, but the scheduler would still
calculate that as 1 retry so 1 alternate host.
This is fixed in
** Also affects: nova/pike
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).
in nova, which will fail back to
cinder, and then cinder has to rollback; it's just easier to fail fast
in the cinder API.
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Importance: Und
hanged in: python-novaclient
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
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/1773945
Title:
nova client ser
** Changed in: nova
Status: New => Invalid
** Changed in: nova/queens
Status: Fix Committed => Fix Released
** Changed in: nova/queens
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Tags added: upgrades volumes
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/queens
Status: New => In Progress
--
You received this bug notification because
Public bug reported:
The [api_database] config options have their help text duplicated in the
configuration reference:
https://docs.openstack.org/nova/latest/configuration/config.html#api-
database
For example:
connection¶
Type: string
Default:
The SQLAlchemy connection
Public bug reported:
https://docs.openstack.org/nova/latest/configuration/config.html#filter_scheduler.max_instances_per_host
Refers to the "num_instances_filter" but that's the name of the python
module, not the actual filter, and there are two of them:
NumInstancesFilter
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => In Progress
** Changed in:
Public bug reported:
The API reference for the server 'migrate' (cold migrate) action doesn't
mention any asynchronous post conditions, like that the server goes to
VERIFY_RESIZE status after a successful cold migration and then must be
confirmed or reverted.
Public bug reported:
This came about from a discussion in IRC:
http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-
dev.2018-05-30.log.html#t2018-05-30T16:13:41
The API reference here doesn't mention that for a system-scoped token,
the response body can have a 'system'
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Triaged
--
You received this
-
operators/2018-May/015364.html
This bug is used to track the documentation updates needed in both nova
and neutron.
** Affects: neutron
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann
Public bug reported:
Looking at the nova configuration reference and sample:
https://docs.openstack.org/nova/latest/configuration/config.html
The osprofiler options aren't included:
https://github.com/openstack/osprofiler/blob/master/osprofiler/opts.py
osprofiler is optional but if available
: High
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Tags: cold-migrate openstack-version.ocata regression
--
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
Right there is no Instance 2.4 in stable/pike:
https://github.com/openstack/nova/blob/stable/pike/nova/objects/instance.py#L115
Did you backport some code to the Instance object in Pike?
What is this config option set to?
This isn't really a bug, and there is a blueprint for this with some
discussion:
https://blueprints.launchpad.net/nova/+spec/nova-improvement-of-maximum-
attach-volumes-more-than-26-vols
** Changed in: nova
Status: New => Incomplete
** Changed in: nova
Status: Incomplete =>
Public bug reported:
At every FFU session we talk about the "nova-status upgrade check" CLI
but it's surprisingly missing from the nova upgrade docs:
https://docs.openstack.org/nova/latest/user/upgrade.html
I'm not exactly sure where in the docs we should mention it, probably
early in the
*** This bug is a duplicate of bug 1733736 ***
https://bugs.launchpad.net/bugs/1733736
** This bug has been marked a duplicate of bug 1733736
reclaim_instance_interval causes dirty attached volume
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
*** This bug is a duplicate of bug 1733736 ***
https://bugs.launchpad.net/bugs/1733736
** This bug is no longer a duplicate of bug 1463856
Cinder volume isn't available after instance soft-deleted timer expired
while volume is still attached
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 1733736 ***
https://bugs.launchpad.net/bugs/1733736
** This bug is no longer a duplicate of bug 1463856
Cinder volume isn't available after instance soft-deleted timer expired
while volume is still attached
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 1733736 ***
https://bugs.launchpad.net/bugs/1733736
** This bug is no longer a duplicate of bug 1463856
Cinder volume isn't available after instance soft-deleted timer expired
while volume is still attached
** This bug has been marked a duplicate of bug
Public bug reported:
Any enabled placement request filters are processed during scheduling
here:
https://github.com/openstack/nova/blob/d78055df0e39b53fd481c53429ba77f8c1e1ab09/nova/scheduler/manager.py#L127
But then if we're doing a rebuild, we don't call placement:
This isn't a bug, the command is doing what it was designed to do. If
you don't specify transport_url or database_connection via the CLI
options, the values are pulled from the config file (via either the
--config-file option or the implied /etc/nova/nova.conf) and if you run
it more than once it
The CLI options are optional because if not specified the values are
pulled from the config file, which you can provide via the --config-file
option, and so you don't have to write URLs with credentials into
scripts. The fact it fails with "The specified transport_url and/or
database_connection
** Changed in: nova
Status: In Progress => Fix Released
** 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).
Public bug reported:
Seen here:
http://logs.openstack.org/00/549300/33/check/nova-
cells-v1/fa9aa6c/logs/screen-n-cell-
child.txt.gz?level=TRACE#_May_18_17_09_57_950092
May 18 17:09:57.950092 ubuntu-xenial-inap-mtl01-0004089915 nova-cells[28513]:
ERROR nova.cells.messaging [None
update the
instance.az once a destination host is picked by the scheduler. Note
that the other move operations like unshelve, evacuate and cold migrate
do update the instance.az once a host is picked.
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status
We'll have to backport the fix for this to ocata as well:
https://review.openstack.org/#/q/I464bc2b88123a012cd12213beac4b572c3c20a56
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects:
Public bug reported:
Seen in a CI run here:
http://logs.openstack.org/82/567682/1/check/nova-
next/3920a7e/logs/screen-n-cpu.txt.gz?level=TRACE#_May_11_14_56_54_842884
May 11 14:56:54.842884 ubuntu-xenial-ovh-bhs1-0003978700 nova-compute[32419]:
WARNING nova.virt.libvirt.driver [None
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
://github.com/openstack/nova/blob/bfcbfdf9169765219320abfa3e09ecda8ff1a80c/nova/compute/manager.py#L2095
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Tags: compute libvirt
** Changed in: nova
Status: New => Triaged
** Chan
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => High
** Changed in: nova/ocata
If this is something you think needs to be handled during unstack.sh,
then you need to change it in devstack, not nova.
** Also affects: devstack
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
I'm pretty sure unstack.sh is no longer really supported in devstack.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Sounds like this is all being handled in ironic, which is tracking the
issue in storyboard:
https://storyboard.openstack.org/#!/story/2002000
** Changed in: nova
Status: Confirmed => Invalid
** No longer affects: nova/ocata
** No longer affects: nova/pike
** No longer affects:
*** This bug is a duplicate of bug 1707319 ***
https://bugs.launchpad.net/bugs/1707319
I knew I'd seen this before, and I updated the compute API reference the
last time:
https://review.openstack.org/#/c/489275/
** This bug has been marked a duplicate of bug 1707319
Security group
Found it, this was the change, https://review.openstack.org/#/c/446053/,
in Pike.
I'm not sure what to do here, I guess if the
instance.get('availability_zone') returns None, we have to fallback to
trying to do the up-call.
** Summary changed:
- Old instances can get AVZ from metadata
+
*** This bug is a duplicate of bug 1765144 ***
https://bugs.launchpad.net/bugs/1765144
** This bug has been marked a duplicate of bug 1765144
[keystone_authtoken] auth_url = http://controller:35357 port error, it
should be 5000
--
You received this bug notification because you are a
Yeah as suggested, these docs have some pointers:
https://docs.openstack.org/nova/pike/user/cells.html#first-time-setup
Specifically:
"If you don't specify --database_connection then nova-manage will use
the [database]/connection value from your config file, and mangle the
database name to have
I'm going to mark this as invalid for nova, because it sounds like
either (1) discover_hosts is getting run out of order or (2) this is
already fixed via bug 1755602 and kolla-ansible just needs to use it,
which is the proposed patch.
** Changed in: nova
Status: New => Invalid
--
You
Serial console support was added to the ironic driver in ocata:
https://review.openstack.org/#/c/328157/
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance:
*** This bug is a duplicate of bug 1765144 ***
https://bugs.launchpad.net/bugs/1765144
** This bug has been marked a duplicate of bug 1765144
[keystone_authtoken] auth_url = http://controller:35357 port error, it
should be 5000
--
You received this bug notification because you are a
This isn't a nova error as far as I can tell, it's some problem reading
from the database:
2018-05-09 16:29:33.278 11031 ERROR nova.api.openstack.extensions
DBError: (pymysql.err.InternalError) (1, u"Can't create/write to file
'/tmp/#sql_4038_1.MAI' (Errcode: 2)")
So you probably need to double
Public bug reported:
http://logs.openstack.org/37/522537/27/check/nova-multiattach/7af78b6
/job-output.txt.gz#_2018-05-08_17_39_54_410553
2018-05-08 17:39:54.410553 | primary | {2}
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Assignee: (unassigned) => Brianna Poulos (brianna-poulos)
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in:
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/queens
Importance: Undecided => Low
** Changed in: nova/queens
Assignee: (unassigned) => Radoslav Gerganov (rgerganov)
--
You
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: nova
Status: In Progress => Invalid
** Changed in: devstack
Status: New => Fix Released
** Changed in: devstack
Importance: Undecided => High
** Changed in: devstack
Assignee:
*** This bug is a duplicate of bug 1633249 ***
https://bugs.launchpad.net/bugs/1633249
** This bug has been marked a duplicate of bug 1633249
Boot volume creation failure leaves secondary volume attached to broken
server
--
You received this bug notification because you are a member of
Public bug reported:
http://logs.openstack.org/67/565367/10/gate/nova-
next/3e991f7/logs/screen-n-novnc-
cell1.txt.gz?level=TRACE#_May_04_21_50_42_066687
May 04 21:50:42.066687 ubuntu-xenial-rax-iad-0003876942 nova-novncproxy[30706]:
ERROR nova.console.websocketproxy Traceback (most recent call
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Changed in: nova/mitaka
Status: New => Fix Released
** Changed in: nova/mitaka
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This is likely a side effect of the fix for bug 1728603
https://review.openstack.org/#/c/516395/.
** Tags added: libvirt resize
** Changed in: nova
Status: New => Triaged
** Summary changed:
- After cold-migration, disk.info file leftover on source host
+ After cold-migration of a
** Also affects: nova/pike
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).
** Changed in: nova
Status: New => 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/178
Title:
'image_source' should not be required for Ironic boot
Public bug reported:
If you look at the allowed task_states for hard reboot in the API here:
https://github.com/openstack/nova/blob/644ac5ec37903b0a08891cc403c8b3b63fc2a91c/nova/compute/api.py#L2963
it allows these values:
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Importance: Undecided => High
** Changed in: nova/queens
Status: New => Triaged
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/queens
Importance: Undecided => Mediu
** Changed in: nova/ocata
Status: In Progress => Fix Released
--
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/1765568
Title:
AttributeError: 'NoneType' object has
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/pike
Status: New => Confirmed
--
You received this bug notification because you
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Leopard Ma (leopardma)
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/ocata
Importance: Undecided => Medium
--
You
Add this as a config option on master with a default being the same as
the hard-coded value today (300), and include a 'fixes' release note
with it since this isn't a feature.
** Changed in: nova
Status: New => Triaged
** Also affects: nova/queens
Importance: Undecided
Status:
*** This bug is a duplicate of bug 1666831 ***
https://bugs.launchpad.net/bugs/1666831
** This bug has been marked a duplicate of bug 1666831
Nova recreates instance directory after migration/resize
--
You received this bug notification because you are a member of Yahoo!
Engineering
*** This bug is a duplicate of bug 1666831 ***
https://bugs.launchpad.net/bugs/1666831
** This bug is no longer a duplicate of bug 1592015
libvirt: cleanup of a volume backed instance resize leaves behind the
instance directory
** This bug has been marked a duplicate of bug 1666831
ects: nova
Importance: Low
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Tags: docs
** Changed in: nova
Importance: Medium => Low
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
You received this bug notification because you are a
I insist.
** Changed in: nova
Status: In Progress => 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/1766208
Title:
Lift the restriction on choices for
mox3 is also affected, as seen in the test results for this nova change:
https://review.openstack.org/#/c/564343/
https://github.com/openstack/mox3/blob/285bc2a1760d460080df79f1ed3b0988cab44f7b/mox3/mox.py#L909
** Also affects: python-mox3
Importance: Undecided
Status: New
** Changed
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/pike
Assignee:
Public bug reported:
As seen in py35 CI logs:
b'/home/osboxes/git/nova/.tox/functional-py35/lib/python3.5/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.'
b' return
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Fix Released
** Changed in: nova/ocata
Importance: Undecided => Medium
** Changed in: nova/ocata
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
You received
This isn't a bug, it's already tracked with a blueprint so just use
that:
https://blueprints.launchpad.net/nova/+spec/libvirt-cpu-model-extra-
flags
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Change https://review.openstack.org/#/c/550648/ marked the
block_device_mapping_v2.boot_index parameter for POST /servers as
optional, but it's only optional since this change in Queens:
https://review.openstack.org/#/c/524208/
Before that, you'll get an error like this if
method signature since 'context' was added to
the driver detach_volume method signature in change:
https://review.openstack.org/#/c/549411/
** Affects: nova
Importance: High
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Affects: nova/queens
Importance: High
Public bug reported:
- [x] This doc is inaccurate in this way:
Since the docs were moved into the nova repo in pike, the admin-guide
links in this page are wrong, for example, the 'Volume operations'
section links to:
http://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html
Which
Public bug reported:
We've been seeing this intermittently:
http://logs.openstack.org/33/559033/2/gate/legacy-tempest-dsvm-neutron-
full/ad0acef/logs/screen-n-cpu.txt.gz?level=TRACE#_2018-04-19_21_26_05_260
2018-04-19 21:26:05.260 12465 ERROR nova.compute.manager
I'm trying to get some guidance in the mailing list:
http://lists.openstack.org/pipermail/openstack-
dev/2018-April/129574.html
Marking as Opinion for now.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Low
--
You received this bug
New
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
801 - 900 of 2946 matches
Mail list logo
