Public bug reported:
This issue similar to https://bugs.launchpad.net/nova/+bug/1634773,
Reproduce steps:
1. create an instance with system disk in rbd backend, named Instance-for-backup
2. create the first backup of this instance, such as: nova backup
Instance-for-backup backup-1 daily 2
3. cre
I got the same error with havana-stable nova while I booting a kvm instance
with libvirt driver,
2014-05-20 14:44:13.179 24237 DEBUG nova.virt.disk.mount.api
[req-63dccfa5-ed06-4daa-8759-ee22c1259edf 830d8718e9e4454a886dee12ce3e8b8e
dfbb396e096e4f2f95f2d7b6a6713e8c] Umount /dev/mapper/nbd9p1 unm
is added after this change.
** Affects: nova
Importance: Undecided
Assignee: wangpan (hzwangpan)
Status: New
** Changed in: nova
Assignee: (unassigned) => wangpan (hzwangpan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, wh
** Changed in: nova
Assignee: wangpan (hzwangpan) => (unassigned)
** 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.launchp
Public bug reported:
this config is defined in nova/virt/libvirt/volume.py, but it's also
used in nova/virt/libvirt/imagebackend.py, and it is not imported to
this module, so a NoSuchOptError is raised while running tests of rbd
image in nova/tests/virt/libvirt/test_imagebackend.py.
Traceback (mo
Public bug reported:
The reason is that, nova wants to cache the base image even if it is
doing a cold migration operation, this is a redundant and wrong thing,
when the image is deleted, then an ImageNotFound exception is raised.
reproduce steps:
1) create an instance
2) delete the image of inst
cd7fd864
Submitter: Jenkins
Branch: master
commit 844df860c38ac38550b8d1739fd53131cd7fd864
Author: Wangpan
Date: Fri Jan 17 10:35:12 2014 +0800
libvirt: handle exception while get vcpu info
If an exception is raised while get a libvirt domain's vcpu info,
the update_available_resource periodic task will b
Public bug reported:
during we cold-migrating or resizing an instance to another host(or during
deleting it), the get_console_output
method may raise an InstanceNotFound excetpion if the instance is not on the
hypervisor, this is an expected error,
so we should add the InstanceNotFound excetpion
Public bug reported:
reproduce steps:
1. create an instance under Folsom
2. update nova to Havana
3. resize the instance to another host
4. confirm the resize
5. examine the instance dir on source host
you will find the instance-_resize dir exists there which was
not deleted while confirm
Public bug reported:
reproduce steps:
1. create an instance
2. stop nova-compute and wait for it becomes to XXX in `nova-manage service
list `
3. delete the instance
and you should change these two config in nova.conf:
running_deleted_instance_poll_interval=60
running_deleted_instance_action = re
up_running_deleted_instances()
5227 except Exception as e:
-> 5228 LOG.warning(_("Periodic cleanup failed to delete "
5229 "instance: %s"),
ipdb> n
> /opt/stack/nova/nova/compute/manager.py(5230)_cleanup_running_deleted_instances()
5229 "instance: %s"
f
the instance's project/user will become wrong eventually.
this bug can be reproduced both in stable havana and master.
so we need to backport this fix patch to stable havana.
this bug is similar as Bug #1271429.
** Affects: nova
Importance: Undecided
Assignee: wangpan (hzwangpan)
nce's project/user will become wrong eventually.
this bug can be reproduced both in stable havana and master.
so we need to backport this fix patch to stable havana.
this bug is similar as Bug #1271429.
** Affects: nova
Importance: Undecided
Assignee: wangpan (hzwangpan)
S
Public bug reported:
reproduce steps in my devstack env with latest master branch:
1. change the nova.conf (#force_config_drive = always) and restart nova-compute
2. download the cirros bootable qcow2 image cirros-0.3.0-x86_64-disk.img(wget
https://launchpad.net/cirros/trunk/0.3.0/+download/cirro
Public bug reported:
it is that, if the confirmation is launched through periodic task,
then the project_id and user_id in context are all None, which
result in reservations in DB are also have `NULL` project_id and
user_id, when these reservations are committed, the quotas usage of
the instance's
** Changed in: nova
Status: New => Invalid
** Description changed:
- I got this issue in my stable havana nova,
- the reproduce steps are:
- 1. create a new flavor
- 2. boot an instance with this flavor
- 3. delete the flavor
- 4. restart the nova-compute service
-
- the trace stack in co
Public bug reported:
I got this issue in my stable havana nova,
the reproduce steps are:
1. create a new flavor
2. boot an instance with this flavor
3. delete the flavor
4. restart the nova-compute service
the trace stack in compute.log:
2014-01-21 17:03:58.395 45856 ERROR nova.openstack.common.t
Public bug reported:
I am using stable havana nova.
I got this exception while I delete my kvm instance, but the qemu process of
this instance become to 'defunct' status by some unknown reason(may be a
qemu/kvm bug), and then the periodic task stopped unexpectly everytime, then
the resources of
Public bug reported:
this bug is similar to https://bugs.launchpad.net/nova/+bug/1158897
but this bug is cause by _reserve_quota_delta() method, which will need to
access DB if quota delta is not empty,
the trace log is:
2013-12-19 01:39:40.879 ERROR nova.compute [-] No db access allowed in
nova
** 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/1196424
Title:
vcpu_pin_set is not convenient to configure for c
I was using admin user to add a not created floating ip, the result may be
correct by using admin user.
If a normal user is used, ERROR: floating ip not found (HTTP 404) (Request-ID:
req-25fe91e2-4a7a-4681-a168-538ba6e17f19) will be returned.
So nova do the correct thing as design.
** Changed in
I want to get a clear response of this bug whether it has been fixed or
not, so I reopen it here, thanks for anyone who can give me the fix
commit or something like this.
** Changed in: nova
Status: Fix Released => New
--
You received this bug notification because you are a member of Yaho
I think we can delete a resizing instance now(grizzly), and also an
error instance, so I change this bug to fix released, if I'm wrong,
correct me pls.
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineerin
I think this bug doesn't need to be fixed in nova, so I change it to
'invalid', if its incorrect, fix me pls.
** 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 Comput
I believe this is a bug of kvm, so close this one, may be we need to
wait for kvm fixes it.
** 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://bu
https://review.openstack.org/#/c/22780/
** Changed in: nova
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/1126062
Title:
nov
Our QA has run the same testcase with grizzly(master branch on github)
more than 20 times, this bug doesn't emerge, so I close it now, and if
this bug reappears later in grizzly with more fully tests, I will reopen
it.
** Changed in: nova
Status: Incomplete => Fix Released
--
You received
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: wangpan (hzwangpan) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchp
I think this bug was fixed in Folsom, so change it to fix released.
** Changed in: nova
Status: Triaged => 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/bu
This bug is same as https://bugs.launchpad.net/nova/+bug/1076308, and
was fixed there.
** Changed in: nova
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https:/
I think the latest nova code has implemented what this bug wants to, so
close it.
** Changed in: nova
Status: Confirmed => 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.
31 matches
Mail list logo