Information has dried up on this, marking as invalid for now.
** 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).
Hmm, thinking about this, its related to issues with
inject_network_info.
Currently people call inject_network_info, and potentially alter
xenstore, then call resetnetwork.
So, sadly, this behaviour is now being used as a feature.
** Changed in: nova
Status: Confirmed = Invalid
--
You
This is bogus
** 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/1225900
Title:
xenapi: race condition in
This is still happening, lets bring this back
** Changed in: nova
Status: Invalid = Triaged
--
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/1188141
Title:
Public bug reported:
Any errors after the XenServer migrate command completes currently can
cause the users VM to be deleted.
While there should be some cleanup performed, deleting the VM does not
make sense for the XenAPI driver.
** Affects: nova
Importance: Medium
Assignee: John
Public bug reported:
When the XenAPI driver resizes a boot partition, it does not take care
to add back the boot partition flag.
With PV images, this is not really needed, because Xen doesn't worry
about the partition being bootable, but for HVM images, it is stops the
image from booting any
in extract_flavor
instance_type[key] = type_fn(sys_meta[type_key])
KeyError: 'instance_type_memory_mb'
This then continues to happen on every run of the periodic task, and
starts to fill up the DB with instance faults.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt
Sounds more like a cinder issue, although the detach probably gets
called through nova.
** Project changed: nova = cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
seem like a cinder thing, but throw it back if you were using the nova
api.
** Project changed: nova = cinder
--
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/1277339
*** This bug is a duplicate of bug 1251920 ***
https://bugs.launchpad.net/bugs/1251920
Already fixed, marking as invalid.
** Changed in: nova
Status: New = Invalid
** This bug has been marked a duplicate of bug 1251920
Tempest failures due to failure to return console logs from an
You need to update your virtual environment, it should then install
oslo.config.
./run_tests -u
Please re-open if this doesn't fix your issue. Its probably better to
ask about this in IRC or the ML.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because
I think that is as expected, it updates all the metadata to that
supplied, however, its a bit confusing.
** Tags added: api
** Changed in: nova
Status: New = Triaged
** Tags added: nova-client
** Tags removed: nova-client
** Tags added: novaclient
** Also affects: python-novaclient
This isn't a nova issue, please raise on the ML or raise a devstack bug.
** 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 an oslo bug, rather than nova, but needs an experts eye
** Tags added: zmq
** Also affects: oslo
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering
this errors, (add_ip_address_to_vm seems
particuarly likely to hit issues), it seems best to tidy up the xenstore
writing code so we consistently add/remove keys from the live copy and
the copy in xenapi.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt
Public bug reported:
In the filter scheduler, schedule_run_instance sends notifications, but
select_destinations does not.
This is inconsistent, and we should send start/end notifications from
both code paths.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt
Public bug reported:
The notifications are quite out of sync with some of the instance object
changes, in particular these very useful details are not included:
* progress
* cell_name
** Affects: nova
Importance: Wishlist
Assignee: John Garbutt (johngarbutt)
Status
detecting a reboot.
Either way, we need to take more care to detect reboots while talking to
the agent.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Tags: xenserver
** Changed in: nova
Importance: Undecided = Medium
** Changed
.
** Affects: nova
Importance: Low
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Tags: xenserver
** Changed in: nova
Importance: Undecided = Low
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Assignee: (unassigned) = John Garbutt
Public bug reported:
The current cells state updates only reserve an amount of capacity.
Really it should be trying to keep a number of hosts free, at least that
was the original intention.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status
Actually this is rubbish, its there for a reason.
** 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/1376681
Title:
.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: Triaged
** Tags: xenserver
** Tags added: xenserver
** Changed in: nova
Status: New = Triaged
** Changed in: nova
Importance: Undecided = Medium
** Changed in: nova
Assignee
** Also affects: python-novaclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1340596
Title:
Tests fail due to
code path, to ensure both behave in a similar way to any
network errors.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Tags: xenserver
** Changed in: nova
Status: New = In Progress
** Changed in: nova
Importance
This seems unlikely at this point, marking as will not fix.
** Changed in: nova
Status: Triaged = Won't Fix
--
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/1024944
Blueprint changed by John Garbutt:
Definition Status: Approved = Obsolete
--
Autobackup When Deprovisioning
https://blueprints.launchpad.net/nova/+spec/auto-backup-terminate
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe
Public bug reported:
The resize ephemeral disk blueprint has regressed the ability to spawn
instances with ephemeral disks.
** Affects: nova
Importance: High
Assignee: John Garbutt (johngarbutt)
Status: Triaged
** Tags: xenserver
** Tags added: xenserver
** Changed
There is a blueprint for the fix for this:
https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
This was fixed in the nova agent, and is now fixed. Clearly had another
bug or blueprint open for the fix.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
*** This bug is a duplicate of bug 1250162 ***
https://bugs.launchpad.net/bugs/1250162
Fixed here:
https://github.com/openstack/nova/commit/9393ed0a8546ce393e354614e87056c795abd22b
** This bug has been marked a duplicate of bug 1250162
xenapi: Agent update ordering
--
You received this
Sorry, I don't see this as something we should support.
If you have a fix, I am cool with that, but its a very complicated bit
of code, I would rather make simpler not more complex, for just an edge
case.
** Changed in: nova
Status: Triaged = Won't Fix
--
You received this bug
test, and modifying it to look at when there are around 200 hosts,
which is still quite a modest size.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Tags: scheduler
** Changed in: nova
Status: New = Triaged
** Changed
Blueprint changed by John Garbutt:
Work items changed:
Work items:
- pool-based live-migration: INPROGRESS
- cross pool live-migration: TODO
+ pool-based shared storage live-migration: INPROGRESS
+ standalone host EXT live-migration: TODO
scheduler based migration: TODO
tempest tests: TODO
Blueprint changed by John Garbutt:
Whiteboard changed:
- Ewan Mellor is working on this.
+ Ewan Mellor was working on this.
+
+ XenServer 6.0 now includes the required changes to support for this
+ feature.
--
XenAPI text console support
https://blueprints.launchpad.net/nova/+spec/xenapi-text
Moved to will not fix, since it is an issue in XenServer not OpenStack
** Changed in: nova
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
No one has been complaining about this, so it probably isn't worth fixing.
The rules need revisiting in the light of quantum anyways.
** Changed in: nova
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
It was due to errors due to some setup issues and failed tests.
It really just a symptom of some other issues, lets ignore this one.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
COW is on by default, and cache_image=all and I have resized, and
everything seemed to work.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This has since been fixed, code inspection says it works in folsom
onwards.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Currently only VHD based SRs are supported. It would work if you use
NFS.
Unfortunately, LVHD is also not supported with Cinder right now either.
It doesn't really fit the model Cinder has. However, if your array is
supported over raw iSCSI with Cinder, it should work with XCP.
The LVHD SR does
The issue is covered elsewhere
** Changed in: nova
Status: Confirmed = 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/1155068
Title:
xenapi: errors when
Removing this, it will be revisited with the move from nova-network to
quantum.
** Changed in: nova
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
It seems this is invalid, and should be fixed by 1161619
** Changed in: nova
Status: Triaged = 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/1162973
I have a blueprint for this now:
https://blueprints.launchpad.net/nova/+spec/xenapi-server-log
** Changed in: nova
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This is a bit of non issue
** Changed in: nova
Status: Confirmed = Won't Fix
--
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/954913
Title:
xenapi host refresh
** 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/1185843
Title:
xenapi: bittorrent plugin download_vhd does not
On closer inspection, it looks like we are OK, in general. Will need to
find more specific cases.
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Yep, this is either a nova agent issue, or a end-user issue.
Either way, its not a Nova bug.
** Changed in: nova
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This seems to have been fixed by a different change I can't track down,
removing from bug list
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
can't find this in the scheduler any more, marking as invalid for now,
please correct me if I am wrong!
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
the agent update has its own issues, we should probably add this
workaround.
** Changed in: nova
Status: Invalid = Triaged
** Changed in: nova
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
hmm, seems to work fine, need more details
** 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/1226449
Title:
I don't think we have seen this recently. Lets close this out for now,
and keep watching.
** 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).
to make sure when the upload fails, glance puts the image into
the failed state, not the active state.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Tags: xenserver
** Changed in: nova
Importance: Undecided = Medium
** Changed
: xenserver
** Changed in: nova
Assignee: John Garbutt (johngarbutt) = (unassigned)
--
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/1422342
Title:
xenapi: soft reboot
Public bug reported:
To reproduce the problem, build an instance with a config drive
attached, and keypair selected, when the deployment is using cells.
This is the change that caused this issue:
Public bug reported:
While retrieving servers, the sort and pagination query string
parameters are treated as search options.
These parameters are passed down to the DB layer and eventually
filtered out when an AttributeError is caught because they do not
exist on the Instance model.
This is
** Also affects: nova/kilo
Importance: Undecided
Status: New
** Changed in: nova/kilo
Milestone: None = kilo-rc3
--
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: Fix Committed = 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/1392773
Title:
Live migration of volume backed instances
Public bug reported:
Its not very clear whats going on here, but here is the symptom.
One of the nova-compute nodes appears to lock up:
http://logs.openstack.org/67/175067/2/check/check-tempest-dsvm-multinode-full/7a95fb0/logs/screen-n-cpu.txt.gz#_2015-05-29_23_27_48_296
It was just completing
its not really released yet, move back to fix committed.
** Changed in: nova
Status: Fix Released = Fix Committed
** Changed in: nova
Importance: Undecided = Medium
** Changed in: nova
Assignee: (unassigned) = Jim Rollenhagen (jim-rollenhagen)
--
You received this bug
of OrphanedInstanceErrors
when listing instances, because the instance no longer has any flavors.
** Affects: nova
Importance: Medium
Assignee: John Garbutt (johngarbutt)
Status: In Progress
** Affects: nova/kilo
Importance: Undecided
Assignee: Dan Smith (danms)
Status
Public bug reported:
nova-manage fails if instance has no flavor in sys_meta when trying to
move them all to instance_extra.
But mostly the instance_type table includes the correct information, so
it should be possible to copy it from there.
** Affects: nova
Importance: Medium
docker is not in the nova tree any more, so this is no longer in scope
for nova.
** Changed in: nova
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Apparently the move to os_brick means we don't need this fixing any
more.
** Tags added: volumes
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering
patch is abandoned, saying this is a valid failure as things are
misconfigured.
** Tags added: libvirt
** 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
Looks like this is invalid now os-brick has merged.
** Tags added: volumes
** 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).
This was reverted, but now has a patch open for review again
** Changed in: nova
Milestone: liberty-2 = None
** Changed in: nova
Status: Fix Released = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Apparently this is a two part fix, the second part is here:
https://review.openstack.org/#/c/170118
** Changed in: nova
Status: Fix Released = In Progress
** Changed in: nova
Milestone: liberty-1 = None
--
You received this bug notification because you are a member of Yahoo!
Marking this as invalid, as I think this is the correct behaviour.
There was talk of adding the ability to resize a volume during resize
using BDM, but thats a spec.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
This has spun out of:
https://bugs.launchpad.net/nova/+bug/1491511
v2_legacy allows trailing whitespace, so v2.0 compat needs to also
accept those request.
To make it simpler, best to strip all the trailing whitespace in v2.0.
** Affects: nova
Importance: High
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova
Assignee: Rajesh Tailor (rajesh-tailor) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
The owner of the instance should not be able to reset state, that is
totally as intended.
A policy issue will never make an instance go to error, I think you are
hitting a different issue here. Please double check the logs, I suspect
if you are using KVM, you are missing the qemu agent from your
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Status: New => Confirmed
** Changed in: nova/mitaka
Importance: Undecided => High
** Changed in: nova/mitaka
Milestone: None => mitaka-rc2
--
You received this bug notification
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Importance: Undecided => High
** Changed in: nova/mitaka
Status: New => Confirmed
** Changed in: nova/mitaka
Milestone: None => mitaka-rc2
--
You received this bug notification
Seems like a nasty regression, adding to mitaka rc2
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Milestone: None => mitaka-rc2
** Tags added: mitaka-rc-potential
--
You received this bug notification because you are a member of Yahoo!
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Milestone: None => mitaka-rc3
** Changed in: nova/mitaka
Status: New => Fix Committed
** Changed in: nova/mitaka
Importance: Undecided => Critical
** Changed in: nova/mitaka
nova-docker is not part of upstream nova, or supported by upstream Nova.
Moving to the nova-docker project.
** Also affects: nova-docker
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member
** Changed in: nova
Status: Confirmed => Invalid
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1504725
Title:
rabbitmq-server restart twice, log is
Given this is for cells, and cells is now largely frozen code, marking
as opinion.
** Changed in: nova
Status: Confirmed => Opinion
** Tags added: cells
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
So I think this is actually python-novaclient.
It checks to see if its a valid id, and correctly gets 404.
This seems like the correct/expected behaviour.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
This doc should not be fixed, it has now been removed.
** 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/1537625
Title:
So I think cinder has fixed this now they have improved state handling.
It moves into the detaching state, which causes the duplicates to fail.
We need to double check this again on master, so marking as invalid for
now, while we wait for a valid repo steps and logs capturing the error
that
*** This bug is a duplicate of bug 1439869 ***
https://bugs.launchpad.net/bugs/1439869
** This bug has been marked a duplicate of bug 1439869
encrypted iSCSI volume attach fails when iscsi_use_multipath is enabled
--
You received this bug notification because you are a member of Yahoo!
So please report this issue with the package author. This is not an
upstream bug, we have no packing upstream.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Looks like this got fixed in libvirt.
** Tags added: neutron sriov
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This sounds like something that needs fixing in the appropriate os-brick
logic for system z
** Also affects: os-brick
Importance: Undecided
Status: New
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1463911
Title:
IPV6 fragmentation and mtu issue
Status in neutron:
Confirmed
Status in linux package in
This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. This bug can be reopened (set back
to "New") if someone decides to work on this.
** Changed in: nova
Status:
So to fix this on stable releases, the bug should be targeted for that
stable release.this is still invalid for master.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
So this behaviour is correct. The volume size is inferred from the
flavor, unless the user chooses otherwise. It's really not related. The
quota and usage in Nova is only tracking local disk, cinder tracks all
volumes.
Given all that, marking this as invalid for now.
** Changed in: nova
This is too old to be useful, let's kill this one.
** Changed in: nova
Status: Confirmed => 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
So that behaviour is as designed.
Disabled only stops new instances landing on that host. You can still
manage your existing instances. The intent is to allow an admin to
migrate or live-migrate instances off the host.
I think we probably want some extra level of disabled to signal that
existing
Looks like this got fixed, marking it as invalid.
** Changed in: nova
Status: Confirmed => 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/1412285
Title:
*** This bug is a duplicate of bug 1574988 ***
https://bugs.launchpad.net/bugs/1574988
This but has already been fixed here:
https://github.com/openstack/nova/commit/2647f91ae97844a73176fc1c8663d9b186bdec1a
** This bug has been marked a duplicate of bug 1574988
--
You received this bug
We should say Fix Released for this.
** Changed in: nova
Status: Fix Committed => 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/1569555
Title:
= -1: raise libvirtError
('virDomainUndefine() failed', dom=self)
2017-02-05 02:33:46.364 19770 ERROR nova.compute.manager [instance:
62034d78-3144-4efd-9c2c-8a792aed3d6b] libvirtError: Domain not found: no domain
with matching uuid '62034d78-3144-4efd-9c2c-8a792aed3d6b' (instance-0431)
201
While this bug is correct, this feature has now been deprecated, and is
bug frozen.
** 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).
the process to exit, but it doesn't seem to quite fully exit
the process.
It seems like this happens only when CONF.upgrade_levels.compute =
"auto"
This was spotted in this OSA change:
https://review.openstack.org/#/c/367752
** Affects: nova
Importance: Medium
Assignee: Jo
So sbezverk_ confirmed the issue was the --config-dir that priv-sep was
passing to the worker. I am looking into a fix for that now.
** Also affects: oslo.privsep
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification
1 - 100 of 111 matches
Mail list logo
