[Yahoo-eng-team] [Bug 1461473] [NEW] Unable to call neutron v2 API from nova: AuthorizationFailure: No valid authentication is available

Public bug reported: When I call neutron v2 API from nova driver, it reported AuthorizationFailure, I've no idea about how this happen and in previous verion, there is no problem: Traceback (most recent call last): File /opt/mydriver/compute/manager.py, line 2006, in _fix_instance_nw_info

[Yahoo-eng-team] [Bug 1454149] [NEW] self._event is None that causes AttributeError: 'NoneType' object has no attribute 'pop'

Public bug reported: Here is the log: 2015-05-11 17:17:50.655 14671 ERROR nova.compute.manager [req-ed95e1f2-11d3-404c-ac78-8c1d5e24bfbf ff514b152688486b9dd9752b3d67fa78 689d7e1036e64e0fbf7fd8b4f51d2e57 - - -] [instance: b83786e1-a222-4409-8d46-65c08c70fa5c] Setting instance vm_state to ERROR

[Yahoo-eng-team] [Bug 1454153] [NEW] nova.openstack.common.loopingcall run outlasted interval

Public bug reported: In the latest nova code, the loopingcall seems abnormal that prevents our code to be okay, the log is: 2015-05-12 03:52:26.905 2594 WARNING nova.openstack.common.loopingcall [req-5d2fe3c6-6ee5-4dad-9e40-2a3ba3f33434 - - - - -] task function __swallowed at 0x59635f0 run

[Yahoo-eng-team] [Bug 1453358] Re: Using volume v2 client instead of v1 to get local volume

This is a powervc-driver issue, and I've already fixed it, thank you. @mzoeller ** Project changed: nova = powervc-driver ** Changed in: powervc-driver Assignee: (unassigned) = Jerry Cai (caimin) ** Changed in: powervc-driver Importance: Undecided = Medium ** Changed in: powervc-driver

[Yahoo-eng-team] [Bug 1453358] [NEW] Using volume v2 client instead of v1 to get local volume

Public bug reported: There is something wrong with volume v1 api to get volume detail info, need to use volume v2 client instead of v1 to get local volume. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo!

[Yahoo-eng-team] [Bug 1447989] [NEW] nova volume-detach volume failed due to arguments counts mismatch?

Public bug reported: nova attached succeeded but when detach, after debug the nova manager reports error: /usr/lib/python2.7/site-packages/nova/compute/manager.py(4927)detach_volume() - self.volume_api.detach(context.elevated(), volume_id) Start Invalid input received: The

[Yahoo-eng-team] [Bug 1447039] [NEW] No flavor with a name or ID of '' exists reported when call nova flavor-show {id}

Public bug reported: Create flavor by the following method: flavors.create(name, memory, vcpus, root_gb, ephemeral_gb=ephemeral_gb, flavorid=flavorid, swap=swap,

[Yahoo-eng-team] [Bug 1432969] [NEW] 'Instance' object has no attribute 'get_flavor' when call compute_api.update

Public bug reported: 2015-03-12 02:47:49.802 19706 ERROR nova.notifications [req-88f518da-f29e-4e85-9a23-093bdd40287c - - - - -] [instance: b8a02182-68d1-4255-b0e4-25a3608a9812] Failed to send state update notification 2015-03-12 02:47:49.802 19706 TRACE nova.notifications [instance:

[Yahoo-eng-team] [Bug 1416269] [NEW] boot vm failed with --block-device set as attach volume failed during boot

Public bug reported: When attach a existing vm during booting vm by following cmd: nova boot --flavor small --image c7e8738b-c2c6-4365-a305-040bfbd1b514 --nic net-id=abfe3157-d23c-4d15-a7ff-80429a7d9b27 --block-device

[Yahoo-eng-team] [Bug 1410649] [NEW] Table instance_system_metadata's colume value is too short to contain the metadata, Data too long for column 'value' at row 1

Public bug reported: It worked well in juno release, but in kilo, the error occurred. We'd like to insert some long metadata into instance_system_metadata, but it reported Data too long for column 'value' at row 1. 2015-01-14 13:47:15.607 30360 ERROR oslo.db.sqlalchemy.exc_filters [-]

[Yahoo-eng-team] [Bug 1408591] [NEW] AttributeError: 'Instance' object has no attribute 'get_flavor' when call compute_api.update

Public bug reported: In nova/notifications.py(370)info_from_instance(): The AttributeError: 'Instance' object has no attribute 'get_flavor' throws on: instance_type = instance.get_flavor() The stacktrace is: - self.compute_api.update(context, local_instance, **base_options)