[Yahoo-eng-team] [Bug 1530249] Re: Use six.moves.reduce instead of builtin reduce
Submitted https://review.openstack.org/#/c/268059/ in cinder. ** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) ** Changed in: cinder Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1530249 Title: Use six.moves.reduce instead of builtin reduce Status in Cinder: In Progress Status in Glance: Fix Released Bug description: Builtin function 'reduce' in Python 2 has been moved to standard library module in Python 3 [1]. To make code compatible, we should replace reduce(expr) with six.moves.reduce(expr) [1] http://python3porting.com/stdlib.html#moved-builtins To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1530249/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1529913] Re: use warning to avoid DeprecationWarning
*** This bug is a duplicate of bug 1508442 *** https://bugs.launchpad.net/bugs/1508442 ** This bug has been marked a duplicate of bug 1508442 LOG.warn is deprecated -- 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/1529913 Title: use warning to avoid DeprecationWarning Status in Glance: In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in Manila: In Progress Status in OpenStack Compute (nova): In Progress Status in Trove: Fix Released Bug description: Python 3 deprecated the logger.warn method, see: https://docs.python.org/3/library/logging.html#logging.warning so we prefer to use warning to avoid DeprecationWarning. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1529913/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1529913] Re: use warning to avoid DeprecationWarning
** Also affects: keystone Importance: Undecided Status: New ** Changed in: keystone Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) ** Also affects: nova Importance: Undecided Status: New ** Also affects: manila Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1529913 Title: use warning to avoid DeprecationWarning Status in Glance: In Progress Status in OpenStack Identity (keystone): New Status in Manila: New Status in OpenStack Compute (nova): New Bug description: Python 3 deprecated the logger.warn method, see: https://docs.python.org/3/library/logging.html#logging.warning so we prefer to use warning to avoid DeprecationWarning. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1529913/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1482594] [NEW] __getitem___ is not returning any value
Public bug reported: There are 2 cases where __getitem___ method is not returning any value from fake_volume module. If we are calling a get method it is expected to return some results. ** Affects: nova Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- 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/1482594 Title: __getitem___ is not returning any value Status in OpenStack Compute (nova): In Progress Bug description: There are 2 cases where __getitem___ method is not returning any value from fake_volume module. If we are calling a get method it is expected to return some results. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1482594/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1482588] [NEW] List creation could be rewritten as a list literal
Public bug reported:
In sqlalchemy/artifacts.py --> _out method, list "deparr' is created as
below.
deparr = []
deparr.append(_out(dep.dest, new_show_level))
could be rewritten as
deparr = [_out(dep.dest, new_show_level)]
** Affects: glance
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: In Progress
** Changed in: glance
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1482588
Title:
List creation could be rewritten as a list literal
Status in Glance:
In Progress
Bug description:
In sqlalchemy/artifacts.py --> _out method, list "deparr' is created
as below.
deparr = []
deparr.append(_out(dep.dest, new_show_level))
could be rewritten as
deparr = [_out(dep.dest, new_show_level)]
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1482588/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1482586] [NEW] Dictionary creation could be rewritten as a dictionary literal
Public bug reported:
There are several places where dict is created and then initialized with
keys later.
for example.
test_metadef_resourcetypes.py module,
ResourceTypeController->index method.
filters = {}
filter['namespace'] = namespace
could be rewritten as
filters = {'namespace': namespace}
** Affects: glance
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Changed in: glance
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1482586
Title:
Dictionary creation could be rewritten as a dictionary literal
Status in Glance:
New
Bug description:
There are several places where dict is created and then initialized
with keys later.
for example.
test_metadef_resourcetypes.py module,
ResourceTypeController->index method.
filters = {}
filter['namespace'] = namespace
could be rewritten as
filters = {'namespace': namespace}
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1482586/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1482583] [NEW] name attribute declared twice in ImmutableImageProxy class
Public bug reported: name attribute declared twice in ImmutableImageProxy class in glance/api/authorization.py module. ** Affects: glance Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1482583 Title: name attribute declared twice in ImmutableImageProxy class Status in Glance: In Progress Bug description: name attribute declared twice in ImmutableImageProxy class in glance/api/authorization.py module. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1482583/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470437] [NEW] ImageCacheManager raises Permission denied error on nova compute in race condition
Public bug reported:
ImageCacheManager raises Permission denied error on nova compute in race
condition
While creating an instance snapshot nova calls guest.launch method from
libvirt driver which changes the base file permissions and updates base
file user from openstack to libvirt-qemu (in case of qcow2 image
backend). In race condition when ImageCacheManager is trying to update
last access time of this base file and guest.launch is called by
instance snapshot just before updating the access time,
ImageCacheManager raise Permission denied error in nova compute for
os.utime().
Steps to reproduce:
1. Configure image_cache_manager_interval=120 in nova.conf and use qcow2 image
backend.
2. Add a sleep for 60 sec in _handle_base_image method of libvirt.imagecache
just before calling os.utime().
3. Restart nova services.
4. Create an instance using image.
$ nova boot --image 5e1659aa-6d38-44e8-aaa3-4217337436c0 --flavor 1 instance-1
5. Check that instance is in active state.
6. Go to the n-cpu screen and check imagecache manager logs at the point it
waits to execute sleep statement added in step #2.
7. Send instance snapshot request when imagecache manger is waiting to execute
sleep.
$ nova image-create 19c7900b-73d5-4c2e-b129-5e2a6b13f396 instance-1-snap
8. instance snapshot request updates the base file owner to libvirt-qemu by
calling guest.launch method from libvirt driver.
9. Now when imagecache manger comes out from sleep and executes os.utime it
raise following Permission denied error in nova compute.
2015-07-01 01:51:46.794 ERROR nova.openstack.common.periodic_task
[req-a03fa45f-ffb9-48dd-8937-5b0414c6864b None None] Error during
ComputeManager._run_image_cache_manager_pass
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
Traceback(most recent call last):
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/openstack/common/periodic_task.py", line 224, in
run_periodic_tasks
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
task(self, context)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/compute/manager.py", line 6177, in
_run_image_cache_manager_pass
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
self.driver.manage_image_cache(context, filtered_instances)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 6252, in manage_image_cache
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
self.image_cache_manager.update(context, all_instances)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/libvirt/imagecache.py", line 668, in update
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
self._age_and_verify_cached_images(context, all_instances, base_dir)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/libvirt/imagecache.py", line 598, in
_age_and_verify_cached_images
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
self._handle_base_image(img, base_file)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task File
"/opt/stack/nova/nova/virt/libvirt/imagecache.py", line 570, in
_handle_base_image
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
os.utime(base_file, None)
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
OSError:[Errno 13] Permission denied:
'/opt/stack/data/nova/instances/_base/8d2c340dcce68e48a75457b1e91457feed27aef5'
2015-07-01 01:51:46.794 TRACE nova.openstack.common.periodic_task
Expected result: guest.launch should not update the base file
permissions and owner to libvirt-qemu. Base file owner should remain
unchanged.
Actual result: Libvirt is updating the base file owner which causes
permission issues in nova.
** Affects: nova
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Changed in: nova
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
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/1470437
Title:
ImageCacheManager raises Permission denied error on nova compute in
race condition
Status in OpenStack Compute (Nova):
New
Bug description:
ImageCacheManager raises Permission denied error on nova compute in
race condition
While creating an instance snapshot nova calls guest.launch method
from libvirt driver which changes the base file permissions and
updates base file user from openstack to libvirt-qemu (in case of
qcow2 image backend). In race condition when ImageCacheManager is
trying to update last access time of this base file and guest.lau
[Yahoo-eng-team] [Bug 1470356] [NEW] AttributeError on creating instance with raw image type
Public bug reported:
Nova compute raises AttributeError on creating the instance with raw
image type and instance goes in to error state.
Steps to reproduce:
1. Set image_type = raw in [libvirt] section of nova.conf and restart nova
services.
2. Create an instance using image (I have used default cirros image).
$ nova boot --image 5e1659aa-6d38-44e8-aaa3-4217337436c0 --flavor 1 instance-1
3. Run $ nova list
4. Instance is in Error state and following error is logged in n-cpu logs
2015-06-30 23:13:11.174 DEBUG oslo_concurrency.lockutils
[req-f66cf801-d424-4583-8270-92023c6a70a1 demo demo] Lock
"8d2c340dcce68e48a75457b1e91457feed27a
ef5" released by "copy_raw_image" :: held 0.431s from (pid=29182) inner
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:456
2015-06-30 23:13:11.184 ERROR nova.compute.manager
[req-f66cf801-d424-4583-8270-92023c6a70a1 demo demo] [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569]
Instance failed to spawn
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] Traceback (most recent call last):
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/compute/manager.py", lin
e 2113, in _build_resources
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] yield resources
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/compute/manager.py", lin
e 1985, in _build_and_run_instance
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] block_device_info=block_device_info)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/driver.py",
line 2428, in spawn
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] admin_pass=admin_password)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/driver.py",
line 2827, in _create_image
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] instance, size, fallback_from_host)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/driver.py",
line 5968, in _try_fetch_image_cache
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] size=size)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/imagebacken
d.py", line 234, in cache
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] *args, **kwargs)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/imagebacken
d.py", line 452, in create_image
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] copy_raw_image(base, self.path, size)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/usr/local/lib/python2.7/dist-packages/oslo_c
oncurrency/lockutils.py", line 445, in inner
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] return f(*args, **kwargs)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/libvirt/imagebacken
d.py", line 439, in copy_raw_image
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] disk.extend(image, size)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/disk/api.py", line
197, in extend
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] if not is_image_extendable(image):
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] File
"/opt/stack/nova/nova/virt/disk/api.py", line
272, in is_image_extendable
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] utils.execute('e2label', image.file)
2015-06-30 23:13:11.184 TRACE nova.compute.manager [instance:
4a4913a9-2ea9-4943-b25e-da684edaf569] AttributeError: 'LocalFileImage' object
has no attrib
ute 'file'
2015-06-30 23:13:11.184 TRACE nova.compute.manager
[Yahoo-eng-team] [Bug 1461776] Re: Error messages are encoded to HTML entity
On our fail early principle we should not send these values to the
server at the first place and should validate in glance-client.
** Also affects: python-glanceclient
Importance: Undecided
Status: New
** Changed in: python-glanceclient
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1461776
Title:
Error messages are encoded to HTML entity
Status in OpenStack Image Registry and Delivery Service (Glance):
In Progress
Status in Python client library for Glance:
New
Bug description:
If you pass min_disk or min_ram as -1 to the image create command,
then it shows following error message on the command prompt.
$ glance image-create --name test --container-format bare --disk-format raw
--file --min-disk -1
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Image min_disk
must be >= 0 ('-1' specified). (HTTP 400)
The above error message will be rendered correctly in the browser but
it is not readable on the command prompt.
This issue belongs to v1 API, in case of v2 api it returns proper error
message:
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Cannot be a
negative value (HTTP 400)
So we can make this error message consistent for both the APIs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1461776/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1461776] [NEW] Error messages are encoded to HTML entity
Public bug reported:
If you pass min_disk as -1 to the image create command, then it show
following error message on the command prompt.
$ glance image-create --name test --container-format bare --disk-format raw
--file --min-disk -1
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Image min_disk
must be >= 0 ('-1' specified). (HTTP 400)
The above error message will be rendered correctly in the browser but it
is not readable on the command prompt.
** Affects: glance
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Changed in: glance
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1461776
Title:
Error messages are encoded to HTML entity
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
If you pass min_disk as -1 to the image create command, then it show
following error message on the command prompt.
$ glance image-create --name test --container-format bare --disk-format raw
--file --min-disk -1
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Image min_disk
must be >= 0 ('-1' specified). (HTTP 400)
The above error message will be rendered correctly in the browser but
it is not readable on the command prompt.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1461776/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448040] [NEW] run_tests.sh failed with code coverage
*** This bug is a duplicate of bug 1448031 *** https://bugs.launchpad.net/bugs/1448031 Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova 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/1448040 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448040/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448043] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1448043 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448043/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448039] [NEW] run_tests.sh failed with code coverage
*** This bug is a duplicate of bug 1448031 *** https://bugs.launchpad.net/bugs/1448031 Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova 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/1448039 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448039/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448031] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1448031 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448031/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448054] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1448054 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448054/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448050] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova 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/1448050 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448050/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448051] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1448051 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448051/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1448061] [NEW] run_tests.sh failed with code coverage
Public bug reported: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1448061 Title: run_tests.sh failed with code coverage Status in OpenStack Compute (Nova): New Bug description: When we try to run nova code coverage using ./run_tests.sh --coverage or ./run_tests.sh -c it does not run test suit and fails with following errors Failed to import test module: nova.tests.unit.volume.test_cinder Traceback (most recent call last): File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 445, in _find_test_path module = self._get_module_from_name(name) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/unittest2/loader.py", line 384, in _get_module_from_name __import__(name) File "/opt/stack/nova/nova/tests/unit/volume/test_cinder.py", line 21, in from nova import test File "/opt/stack/nova/nova/test.py", line 47, in from nova.network import manager as network_manager File "/opt/stack/nova/nova/network/manager.py", line 51, in from nova import ipv6 File "/opt/stack/nova/nova/ipv6/__init__.py", line 15, in from nova.ipv6.api import * # noqa File "/opt/stack/nova/nova/ipv6/api.py", line 42, in reset_backend() File "/opt/stack/nova/nova/ipv6/api.py", line 31, in reset_backend CONF.ipv6_backend).driver File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 45, in __init__ verify_requirements=verify_requirements, File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/named.py", line 56, in __init__ self._init_plugins(extensions) File "/opt/stack/nova/.venv/local/lib/python2.7/site-packages/stevedore/driver.py", line 97, in _init_plugins (self.namespace, name)) RuntimeError: No 'nova.ipv6_backend' driver found, looking for 'rfc2462' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1448061/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1443890] [NEW] 'deleted' filter does not work properly for server list
Public bug reported:
When calling server list with deleted filter set to true/false, it
always returns deleted instances to admin.
Steps to reproduce:
Hit curl command with deleted='true', 'false' or any random string (e.g.
deleted='abc')
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='true'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 32d57785556647d4b03e4cacf74e3aea"
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='false'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 32d57785556647d4b03e4cacf74e3aea"
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='abc'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 2c80485a73be4d439440702ae849ec61"
Expected result:
Server list should return deleted instances only when deleted filter contains
any value from ('1', 't', 'true', 'on', 'y', 'yes').
Actual result:
All above commands returns deleted instances even deleted is passed as 'false',
'False' or 'abc'.
** Affects: nova
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Tags: ntt
** Changed in: nova
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
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/1443890
Title:
'deleted' filter does not work properly for server list
Status in OpenStack Compute (Nova):
New
Bug description:
When calling server list with deleted filter set to true/false, it
always returns deleted instances to admin.
Steps to reproduce:
Hit curl command with deleted='true', 'false' or any random string
(e.g. deleted='abc')
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='true'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 32d57785556647d4b03e4cacf74e3aea"
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='false'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 32d57785556647d4b03e4cacf74e3aea"
curl -g -i --cacert "/opt/stack/data/CA/int-ca/ca-chain.pem" -X GET
http://10.69.4.150:8774/v2/58bad77b05ef44f8a9f5fc5089bab30e/servers/detail?deleted='abc'
-H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X
-Auth-Token: 2c80485a73be4d439440702ae849ec61"
Expected result:
Server list should return deleted instances only when deleted filter contains
any value from ('1', 't', 'true', 'on', 'y', 'yes').
Actual result:
All above commands returns deleted instances even deleted is passed as
'false', 'False' or 'abc'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1443890/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1436849] [NEW] Inconsistent delete API in case of soft-delete
Public bug reported: When instance.vm_state is SOFT_DELETED, if we send duplicate delete request there is an inconsistency in delete api. If delete api is called with instance name, it returns an error message while calling it with instance id returns success response and sends duplicate delete call to the server. Steps to reproduce: 1. Set reclaim_instance_interval parameter in nova.conf and restart nova-api and compute services. 2. Create an instance. $ nova boot --flavor 42 --image 7c0b4737-f630-4adc-9907-4868d2571260 test 3. Soft delete instance. $ nova delete test --Will soft delete the instance and update the vm_state to SOFT_DELETED 4. Call delete instance again with instance name. $ nova delete test Response: No server with a name or ID of 'test' exists. ERROR (CommandError): Unable to delete the specified server(s). 5. Call delete instance using instance id. $ nova delete dc4449fe-5229-4b55-ad49-4fc9a5d8367f Response: Request to delete server dc4449fe-5229-4b55-ad49-4fc9a5d8367f has been accepted. (sends duplicate delete request) This is because when we call delete using instance id it fetch instance which is already in SOFT_DELETED state but in case of using instance name it does not fetch instances which are already in SOFT_DELETED state. Ideally it should return same response in both the cases (with instance name and id). Note: Same issue is with force-delete call when instance is in SOFT_DELETED state. ** Affects: nova Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- 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/1436849 Title: Inconsistent delete API in case of soft-delete Status in OpenStack Compute (Nova): New Bug description: When instance.vm_state is SOFT_DELETED, if we send duplicate delete request there is an inconsistency in delete api. If delete api is called with instance name, it returns an error message while calling it with instance id returns success response and sends duplicate delete call to the server. Steps to reproduce: 1. Set reclaim_instance_interval parameter in nova.conf and restart nova-api and compute services. 2. Create an instance. $ nova boot --flavor 42 --image 7c0b4737-f630-4adc-9907-4868d2571260 test 3. Soft delete instance. $ nova delete test --Will soft delete the instance and update the vm_state to SOFT_DELETED 4. Call delete instance again with instance name. $ nova delete test Response: No server with a name or ID of 'test' exists. ERROR (CommandError): Unable to delete the specified server(s). 5. Call delete instance using instance id. $ nova delete dc4449fe-5229-4b55-ad49-4fc9a5d8367f Response: Request to delete server dc4449fe-5229-4b55-ad49-4fc9a5d8367f has been accepted. (sends duplicate delete request) This is because when we call delete using instance id it fetch instance which is already in SOFT_DELETED state but in case of using instance name it does not fetch instances which are already in SOFT_DELETED state. Ideally it should return same response in both the cases (with instance name and id). Note: Same issue is with force-delete call when instance is in SOFT_DELETED state. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1436849/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1428424] Re: Remove use of contextlib.nested
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1428424 Title: Remove use of contextlib.nested Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): In Progress Bug description: The contextlib.nested call has been deprecated in Python 2.7. This causes DeprecationWarning messages in the unit tests. There are also known issues with contextlib.nested that were addressed by the native support for multiple "with" variables. For instance, if the first object is created but the second one throws an exception, the first object's __exit__ is never called. For more information see https://docs.python.org/2/library/contextlib.html#contextlib.nested contextlib.nested is also not compatible in Python 3. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1428424/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1431239] [NEW] Log messages are not translated using marker functions
Public bug reported: According to openstack standards [1], Log messages should be translated with appropriate marker functions. I have found several places where log messages are not translated properly. [1] http://docs.openstack.org/developer/oslo.i18n/guidelines.html#log- translation ** Affects: glance Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: New ** Tags: ntt ** Changed in: glance Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1431239 Title: Log messages are not translated using marker functions Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: According to openstack standards [1], Log messages should be translated with appropriate marker functions. I have found several places where log messages are not translated properly. [1] http://docs.openstack.org/developer/oslo.i18n/guidelines.html#log- translation To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1431239/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1427060] [NEW] Unnecessary bdm entry is created if same volume is attached twice to an instance
Public bug reported: When we try to attach an already attached volume to an instance it raises InvalidVolume exception but creates an entry in block_device_mapping table with deleted flag set to true. Ideally when attach volume fails it should not create any entries in database. Steps to reproduce: 1. Created an instance named test_vm_1. 2. Created a volume named test_volume_1. 3. Verified that instance is in active state and volume is in available state. 4. Attach volume using below command: $ nova volume-attach . 5. Confirmed that volume is in 'in-use' status using below command: $ cinder list. 6. Execute volume-attach command again with same volume_id. $ nova volume-attach . After executing step 6 it raises "Invalid volume" exception and attached volume can be used normally which is correct. But when you check block_device_mapping table using below sql query, you will find an additional bdm entry which should not be created. select * from block_device_mapping where instance_uuid='ee94830b- 5d39-42a7-b8c2-6175bb77563a'; ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1427060 Title: Unnecessary bdm entry is created if same volume is attached twice to an instance Status in OpenStack Compute (Nova): New Bug description: When we try to attach an already attached volume to an instance it raises InvalidVolume exception but creates an entry in block_device_mapping table with deleted flag set to true. Ideally when attach volume fails it should not create any entries in database. Steps to reproduce: 1. Created an instance named test_vm_1. 2. Created a volume named test_volume_1. 3. Verified that instance is in active state and volume is in available state. 4. Attach volume using below command: $ nova volume-attach . 5. Confirmed that volume is in 'in-use' status using below command: $ cinder list. 6. Execute volume-attach command again with same volume_id. $ nova volume-attach . After executing step 6 it raises "Invalid volume" exception and attached volume can be used normally which is correct. But when you check block_device_mapping table using below sql query, you will find an additional bdm entry which should not be created. select * from block_device_mapping where instance_uuid='ee94830b- 5d39-42a7-b8c2-6175bb77563a'; To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1427060/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1410063] [NEW] Remove python-cinderclient from requirement.txt
Public bug reported: Uses of python-cinderclient is moved to glance_store project and not used anymore in glance, so it should be removed from requirement.txt of glance project. ** Affects: glance Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: New ** Tags: ntt ** Changed in: glance Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1410063 Title: Remove python-cinderclient from requirement.txt Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Uses of python-cinderclient is moved to glance_store project and not used anymore in glance, so it should be removed from requirement.txt of glance project. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1410063/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1383117] [NEW] ./run_tests.sh raises error for glance_store in debug mode
Public bug reported:
When we try to run glance_store test suit in debug mode it raises error
“ImportError: Start directory is not importable” with the following
stack trace
$ ./run_tests.sh -d
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 535, in
main(sys.argv, sys.stdout)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 532, in main
stdout=stdout)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 218, in __init__
self.parseArgs(argv)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 257, in parseArgs
self._do_discovery(argv[2:])
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 376, in _do_discovery
loaded = loader.discover(start_dir, pattern, top_level_dir)
File "/usr/lib/python2.7/unittest/loader.py", line 204, in discover
raise ImportError('Start directory is not importable: %r' % start_dir)
ImportError: Start directory is not importable: './glance/tests'
** Affects: glance
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Tags: ntt
** Changed in: glance
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1383117
Title:
./run_tests.sh raises error for glance_store in debug mode
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
When we try to run glance_store test suit in debug mode it raises
error “ImportError: Start directory is not importable” with the
following stack trace
$ ./run_tests.sh -d
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 535, in
main(sys.argv, sys.stdout)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 532, in main
stdout=stdout)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 218, in __init__
self.parseArgs(argv)
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 257, in parseArgs
self._do_discovery(argv[2:])
File
"/home/openstack/glance_store/glance_store/.venv/lib/python2.7/site-packages/testtools/run.py",
line 376, in _do_discovery
loaded = loader.discover(start_dir, pattern, top_level_dir)
File "/usr/lib/python2.7/unittest/loader.py", line 204, in discover
raise ImportError('Start directory is not importable: %r' % start_dir)
ImportError: Start directory is not importable: './glance/tests'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1383117/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1380552] [NEW] Fix for adopt glance.store library in Glance
Public bug reported: The store module is removed from glance project and new glance_store module is created, but the glance project code was not updated properly for the required changes. There are few cases in v1 api which needs to be addressed: 1. _get_from_store method raises store.NotFound exception from glance_store but it is still trying to catch exception.NotFound exception in glance and the actual exception has not been caught which causes 500 HTTPInternalServerError. 2. _get_size method raises store.NotFound exception from glance_store but it is still trying to catch exception.NotFound exception in glance and the actual exception has not been caught which causes 500 HTTPInternalServerError. ** Affects: glance Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: New ** Tags: ntt ** Changed in: glance Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1380552 Title: Fix for adopt glance.store library in Glance Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The store module is removed from glance project and new glance_store module is created, but the glance project code was not updated properly for the required changes. There are few cases in v1 api which needs to be addressed: 1. _get_from_store method raises store.NotFound exception from glance_store but it is still trying to catch exception.NotFound exception in glance and the actual exception has not been caught which causes 500 HTTPInternalServerError. 2. _get_size method raises store.NotFound exception from glance_store but it is still trying to catch exception.NotFound exception in glance and the actual exception has not been caught which causes 500 HTTPInternalServerError. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1380552/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1379798] [NEW] Glance returns HTTPInternalServerError 500 in case of image server is down
Public bug reported: HTTPInternalServerError 500 response is returned to the user while image server is down during downloading the image. When user tries to download the image from the remote location (image server) which is down, Connection refused ECONNREFUSED error is raised on the glance server. Ideally it should return 503 HTTPServiceUnavailable response to the user. Steps to reproduce: 1. Create a file 'test_image.py' at any location. example: /home/openstack/ 2. Run Simple HTTP server using "python -m SimpleHTTPServer 8050" from location mentioned in step 1. 3. Create an image using location parameter. example: glance image-create --name myimage --disk-format=raw --container-format=bare --location http://10.69.4.178:8050/test_image.py 4. Stop Simple HTTP server. 5. Download image using glance image-download created in step 3. Please refer http://paste.openstack.org/show/120165/ for v1 and v2 api logs. ** Affects: glance Importance: Undecided Assignee: Ankit Agrawal (ankitagrawal) Status: New ** Tags: ntt ** Changed in: glance Assignee: (unassigned) => Ankit Agrawal (ankitagrawal) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1379798 Title: Glance returns HTTPInternalServerError 500 in case of image server is down Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: HTTPInternalServerError 500 response is returned to the user while image server is down during downloading the image. When user tries to download the image from the remote location (image server) which is down, Connection refused ECONNREFUSED error is raised on the glance server. Ideally it should return 503 HTTPServiceUnavailable response to the user. Steps to reproduce: 1. Create a file 'test_image.py' at any location. example: /home/openstack/ 2. Run Simple HTTP server using "python -m SimpleHTTPServer 8050" from location mentioned in step 1. 3. Create an image using location parameter. example: glance image-create --name myimage --disk-format=raw --container-format=bare --location http://10.69.4.178:8050/test_image.py 4. Stop Simple HTTP server. 5. Download image using glance image-download created in step 3. Please refer http://paste.openstack.org/show/120165/ for v1 and v2 api logs. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1379798/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1378215] [NEW] If db deadlock occurs for some reason while deleting an image, no one can delete the image any more
on)
File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1320, in
send
application, catch_exc_info=False)
File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1284, in
call_application
app_iter = application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/paste/urlmap.py", line 206, in __call__
return app(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in
__call__
return resp(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 131,
in __call__
response = self.app(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in
__call__
return resp(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in
__call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in
call_func
return self.func(req, *args, **kwargs)
File "/opt/stack/glance/glance/common/wsgi.py", line 683, in __call__
request, **action_args)
File "/opt/stack/glance/glance/common/wsgi.py", line 707, in dispatch
return method(*args, **kwargs)
File "/opt/stack/glance/glance/common/utils.py", line 449, in wrapped
return func(self, req, *args, **kwargs)
File "/opt/stack/glance/glance/api/v1/images.py", line 1058, in delete
registry.delete_image_metadata(req.context, id)
File "/opt/stack/glance/glance/registry/client/v1/api.py", line 175, in
delete_image_metadata
return c.delete_image(image_id)
File "/opt/stack/glance/glance/registry/client/v1/client.py", line 207, in
delete_image
res = self.do_request("DELETE", "/images/%s" % image_id)
File "/opt/stack/glance/glance/registry/client/v1/client.py", line 130, in
do_request
'exc_name': exc_name})
File "/opt/stack/glance/glance/openstack/common/excutils.py", line 82, in
__exit__
six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/glance/glance/registry/client/v1/client.py", line 115, in
do_request
**kwargs)
File "/opt/stack/glance/glance/common/client.py", line 68, in wrapped
return func(self, *args, **kwargs)
File "/opt/stack/glance/glance/common/client.py", line 388, in do_request
headers=copy.deepcopy(headers))
File "/opt/stack/glance/glance/common/client.py", line 85, in wrapped
return func(self, method, url, body, headers)
File "/opt/stack/glance/glance/common/client.py", line 546, in _do_request
raise exception.ServerError()
ServerError: The request returned 500 Internal Server Error.
2014-10-06 00:53:10.055 6827 INFO glance.wsgi.server
[2b47d213-6f80-410f-9766-dc80607f0224 7e7c3a413f184dbcb9a65404dbfcc0f0
309c5ff4082c4231bcc17d8c55c83997 - - -] 10.69.4.178 - - [06/Oct/2014 00:53:10]
"DELETE /v1/images/f9f8a40d-530b-498c-9fbc-86f29da555f4 HTTP/1.1" 500 139
0.239514
** Affects: glance
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Tags: ntt
** Changed in: glance
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1378215
Title:
If db deadlock occurs for some reason while deleting an image, no one
can delete the image any more
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Glance api returns 500 Internal Server Error, if db deadlock occurs in
glance-registry for some reason while deleting an image.
The image 'status' is set to deleted and 'deleted' is set to False. As
deleted is still False, the image is visible in image list but it can not be
deleted any more.
If you try to delete this image it will raise 404 (Not Found) error
for V1 api and 500 (HTTPInternalServerError) for V2 api.
Note:
To reproduce this issue I've explicitly raised "db_exception.DBDeadlock"
exception from "_image_child_entry_delete_all" method under
"\glance\db\sqlalchemy\api.py".
glance-api.log
--
2014-10-06 00:53:10.037 6827 INFO glance.registry.client.v1.client
[2b47d213-6f80-410f-9766-dc80607f0224 7e7c3a413f184dbcb9a65404dbfcc0f0
309c5ff4082c423
1bcc17d8c55c83997 - - -] Registry client request DELETE
/images/f9f8a40d-530b-498c-9fbc-86f29da555f4 raised ServerError
2014-10-06 00:53:10.045 6827 INFO glance.wsgi.server
[2b47d213-6f80-410f-9766-dc80607f0224 7e7c3a413f184dbcb9a65404dbfcc0f0
309c5ff4082c4231bcc17d8c55c83997 - - -] Traceback (most recent call last):
File "/usr/local/lib
[Yahoo-eng-team] [Bug 1353343] [NEW] Cannot recover instance if error occurs during resize
Public bug reported:
Single Node Environment:
When we resize an instance in single node environment, instance directory is
renamed to “_resize” directory.
Then a new directory is created with the instance path on the same node and all
instance files with new configuration will be copied to this directory.
If there is not enough space left on this node to create or copying instance
files then disk full error occurs and VM goes into "error" state.
Multi Node Environment:
When we resize an instance in multi node environment, directory is renamed to
“_resize” directory on source node.
Then a new directory is created with the instance path on the destination node
and all instance files with new configuration will be copied to this directory.
If there is not enough space left on destination node to create or copying
instance files then disk full error occurs and VM goes to "error" state.
As of now in both the cases there is no way to recover instance from the error
state which is not good from end users perspective.
Ideally it should log the warning if disk space is full and should keep the
instance up and running with old configuration.
Stack trace for reference:
2014-07-22 03:50:04.618 ERROR nova.compute.manager
[req-d45a250c-bef9-4b42-96d3-187296dba8b0 admin demo] [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] Setting instance vm_state to ERROR
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] Traceback (most recent call last):
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File
"/opt/stack/nova/nova/compute/manager.py", line 3656, in finish_resize
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] disk_info, image)
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File
"/opt/stack/nova/nova/compute/manager.py", line 3624, in _finish_resize
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] block_device_info, power_on)
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 5053, in finish_migration
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] block_device_info=None,
inject_files=False)
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 2559, in _create_image
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576]
fileutils.ensure_tree(libvirt_utils.get_instance_path(instance))
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File
"/opt/stack/nova/nova/openstack/common/fileutils.py", line 35, in ensure_tree
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] os.makedirs(path)
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] File "/usr/lib/python2.7/os.py", line
157, in makedirs
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] mkdir(name, mode)
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576] OSError: [Errno 28] No space left on
device: '/mnt/stack/data/nova/instances/30003b95-d88a-41f7-8ee2-44bffc524576'
2014-07-22 03:50:04.618 TRACE nova.compute.manager [instance:
30003b95-d88a-41f7-8ee2-44bffc524576]
** Affects: nova
Importance: Undecided
Assignee: Ankit Agrawal (ankitagrawal)
Status: New
** Tags: ntt
** Changed in: nova
Assignee: (unassigned) => Ankit Agrawal (ankitagrawal)
--
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/1353343
Title:
Cannot recover instance if error occurs during resize
Status in OpenStack Compute (Nova):
New
Bug description:
Single Node Environment:
When we resize an instance in single node environment, instance directory is
renamed to “_resize” directory.
Then a new directory is created with the instance path on the same node and
all instance files with new configuration will be copied to this directory.
If there is not enough space left on this node to create or copying instance
files then disk full error occurs and VM goes into "error" state.
Multi Node Environment:
When we resize an instance in multi node environment, directory is renamed to
“_resize” directory on source node.
Then a new directory is created with the instance path o
[Yahoo-eng-team] [Bug 1332560] Re: Image is created without any format when instance snapshot is created
Christopher - I tested this issue with the latest master and now I am able to boot the instance successfully from 0 bytes image which is internally referring to volume snapshot to boot the instance from it. It is mentioned that the new image is simply a bucket of properties (particularly the block device mapping, kernel and ramdisk IDs) with no image data, so I think this is the reason for no image format here. ** 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/1332560 Title: Image is created without any format when instance snapshot is created Status in OpenStack Compute (Nova): Invalid Bug description: When an instance is created using boot from volume, boot from image(creates a new volume) or boot from volume snapshot(creates a new volume), and after creating image snapshot from this instance an image of 0 bytes is created which is neither public nor protected and have no format defined. Steps to reproduce using Horizon: Case 1: Boot instance from volume 1. Go to Project --> Compute --> Volumes and click on 'Create Volume'. 2. Provide volume name, Size and select 'Image' from 'Volume Source' drop-down and an image from 'Use image as a source' drop-down. 3. Click on 'Create Volume' button and a bootable volume will be created. 4. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 5. Provide instance name, select 'Boot from volume' as 'Instance Boot Source' and a bootable volume as 'volume'. 6. Click on 'Launch' button. 7. You will be redirected to instance list page. 8. Click on 'Create Snapshot' to create a snapshot of this instance. 9. In this case a new image of 0 bytes and a volume snapshot will be created. 10. You will be redirected to image list where you will see a new image created with 0 bytes. 11. Neither this image is public nor protected. 12. No format is defined for this image. Case 2: Boot instance from image(creates a new volume) 1. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 2. Provide instance name, select 'Boot from image(creates a new volume)' as 'Instance Boot Source' and an image from the drop-down. 3. Click on 'Launch' button. 4. A new volume will be created and will be attached to this instance. 5. You will be redirected to instance list page. 6. Click on 'Create Snapshot' to create a snapshot of this instance. 7. In this case a new image of 0 bytes and a volume snapshot will be created. 8. You will be redirected to image list where you will see a new image created with 0 bytes. 9. Neither this image is public nor protected. 10. No format is defined for this image. Case 3: Boot instance from volume snapshot(creates a new volume) 1. Go to Project --> Compute --> volumes and click on 'Create Volume' button. 2. Create a bootable volume same as case 1. 3. From volumes list page you will see 'more' button with respect to each volume. 4. Click on 'more', a drop-down will open, select 'Create Snapshot' from this drop-down. 5. A snapshot will be created for this volume. 6. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 7. Provide instance name, select 'Boot from image(creates a new volume)' as 'Instance Boot Source' and an image from the drop-down. 8. Click on 'Launch' button. 9. A new volume will be created and will be attached to this instance. 10. You will be redirected to instance list page. 11. Click on 'Create Snapshot' to create a snapshot of this instance. 12. In this case a new image of 0 bytes and a volume snapshot will be created. 13. You will be redirected to image list where you will see a new image created with 0 bytes. 14. Neither this image is public nor protected. 15. No format is defined for this image. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1332560/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1332560] [NEW] Invalid image is created without any format when instance snapshot is created.
Public bug reported: When an instance is created using boot from volume, boot from image(creates a new volume) or boot from volume snapshot(creates a new volume), an image of 0 bytes is created which is neither public nor protected and have no format defined. Steps to reproduce using Horizon: Case 1: Boot instance from volume 1. Go to Project --> Compute --> Volumes and click on 'Create Volume'. 2. Provide volume name, Size and select 'Image' from 'Volume Source' drop-down and an image from 'Use image as a source' drop-down. 3. Click on 'Create Volume' button and a bootable volume will be created. 4. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 5. Provide instance name, select 'Boot from volume' as 'Instance Boot Source' and a bootable volume as 'volume'. 6. Click on 'Launch' button. 7. You will be redirected to instance list page. 8. Click on 'Create Snapshot' to create a snapshot of this instance. 9. In this case a new image of 0 bytes and a volume snapshot will be created. 10. You will be redirected to image list where you will see a new image created with 0 bytes. 11. Neither this image is public nor protected. 12. No format is defined for this image. Case 2: Boot instance from image(creates a new volume) 1. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 2. Provide instance name, select 'Boot from image(creates a new volume)' as 'Instance Boot Source' and an image from the drop-down. 3. Click on 'Launch' button. 4. A new volume will be created and will be attached to this instance. 5. You will be redirected to instance list page. 6. Click on 'Create Snapshot' to create a snapshot of this instance. 7. In this case a new image of 0 bytes and a volume snapshot will be created. 8. You will be redirected to image list where you will see a new image created with 0 bytes. 9. Neither this image is public nor protected. 10. No format is defined for this image. Case 3: Boot instance from volume snapshot(creates a new volume) 1. Go to Project --> Compute --> volumes and click on 'Create Volume' button. 2. Create a bootable volume same as case 1. 3. From volumes list page you will see 'more' button with respect to each volume. 4. Click on 'more', a drop-down will open, select 'Create Snapshot' from this drop-down. 5. A snapshot will be created for this volume. 6. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 7. Provide instance name, select 'Boot from image(creates a new volume)' as 'Instance Boot Source' and an image from the drop-down. 8. Click on 'Launch' button. 9. A new volume will be created and will be attached to this instance. 10. You will be redirected to instance list page. 11. Click on 'Create Snapshot' to create a snapshot of this instance. 12. In this case a new image of 0 bytes and a volume snapshot will be created. 13. You will be redirected to image list where you will see a new image created with 0 bytes. 14. Neither this image is public nor protected. 15. No format is defined for this image. ** Affects: nova Importance: Undecided Status: New ** Tags: ntt ** Description changed: - When an instance is created using boot from volume, boot from image(creates a new volume) or - boot from volume snapshot(creates a new volume), an image of 0 bytes is created which is - neither public nor protected and have no format defined. + When an instance is created using boot from volume, boot from + image(creates a new volume) or boot from volume snapshot(creates a new + volume), an image of 0 bytes is created which is neither public nor + protected and have no format defined. Steps to reproduce using Horizon: Case 1: Boot instance from volume 1. Go to Project --> Compute --> Volumes and click on 'Create Volume'. 2. Provide volume name, Size and select 'Image' from 'Volume Source' drop-down and an image from 'Use image as a source' drop-down. 3. Click on 'Create Volume' button and a bootable volume will be created. 4. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 5. Provide instance name, select 'Boot from volume' as 'Instance Boot Source' and a bootable volume as 'volume'. 6. Click on 'Launch' button. 7. You will be redirected to instance list page. 8. Click on 'Create Snapshot' to create a snapshot of this instance. 9. In this case a new image of 0 bytes and a volume snapshot will be created. 10. You will be redirected to image list where you will see a new image created with 0 bytes. 11. Neither this image is public nor protected. 12. No format is defined for this image. Case 2: Boot instance from image(creates a new volume) 1. Go to Project --> Compute --> Instances and click on 'Launch Instance' button from the top right. 2. Provide instance name, select 'Boot from image(creates a new volume)' as 'Instance Bo
[Yahoo-eng-team] [Bug 1332558] [NEW] Instance snapshot is created with wrong image format
Public bug reported: When you boot an instance with image of RAW image format then after taking instance snapshot it creates a snapshot with image format QCOW2. Steps to reproduce using Horizon: 1. Go to Project --> Compute --> Images and click on 'Create Image'. 2. Create an image with 'Raw' format. 3. Go to Project --> Compute --> Instances and click on 'Launch Instance'. 4. Boot an instance by selecting the 'Boot from image' as source and newly created raw image from the Image Name drop-down. 5. Click on 'Create Snapshot' to create a snapshot of this instance. 6. You will be redirected to image list page where you will see the format of snapshot as 'QCOW2'. Ideally the snapshot format should be same as its source image. ** Affects: nova Importance: Undecided Status: New ** Tags: ntt -- 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/1332558 Title: Instance snapshot is created with wrong image format Status in OpenStack Compute (Nova): New Bug description: When you boot an instance with image of RAW image format then after taking instance snapshot it creates a snapshot with image format QCOW2. Steps to reproduce using Horizon: 1. Go to Project --> Compute --> Images and click on 'Create Image'. 2. Create an image with 'Raw' format. 3. Go to Project --> Compute --> Instances and click on 'Launch Instance'. 4. Boot an instance by selecting the 'Boot from image' as source and newly created raw image from the Image Name drop-down. 5. Click on 'Create Snapshot' to create a snapshot of this instance. 6. You will be redirected to image list page where you will see the format of snapshot as 'QCOW2'. Ideally the snapshot format should be same as its source image. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1332558/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1282910] [NEW] fixed ip address assigned twice to the vm
Public bug reported: If the vm fails to spawn on the nova compute node where it was suppose to run, then it reschedules to run the vm on the another compute node. After the vm is created successfully on the another node, you will notice that VM is assigned 2 fixed ip addresses. Expected output: only one fixed ip address should be assigned to a VM. Actual output: openstack@development-009:/opt/stack/nova/nova/compute$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 42016c47-40c3-4562-b2b5-d3c8199cc4e6 | nova-42016c47-40c3-4562-b2b5-d3c8199cc4e6 | ACTIVE | - | Running | private=10.0.0.81, 10.0.0.82 | +--+---+++-+--+ To reproduce this issue, you will need to explicitly raise Exception from compute/manafger.py->_spawn method. ** Affects: nova Importance: Undecided Assignee: Ankit Agrawal (ankit11-agrawal) Status: New ** Tags: ntt ** Changed in: nova Assignee: (unassigned) => Ankit Agrawal (ankit11-agrawal) -- 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/1282910 Title: fixed ip address assigned twice to the vm Status in OpenStack Compute (Nova): New Bug description: If the vm fails to spawn on the nova compute node where it was suppose to run, then it reschedules to run the vm on the another compute node. After the vm is created successfully on the another node, you will notice that VM is assigned 2 fixed ip addresses. Expected output: only one fixed ip address should be assigned to a VM. Actual output: openstack@development-009:/opt/stack/nova/nova/compute$ nova list +--+---+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+--+ | 42016c47-40c3-4562-b2b5-d3c8199cc4e6 | nova-42016c47-40c3-4562-b2b5-d3c8199cc4e6 | ACTIVE | - | Running | private=10.0.0.81, 10.0.0.82 | +--+---+++-+--+ To reproduce this issue, you will need to explicitly raise Exception from compute/manafger.py->_spawn method. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1282910/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
