[Yahoo-eng-team] [Bug 1511539] [NEW] libvirt evacute on ppcle failed with IDE controllers are unsupported for this QEMU binary or machine type

Public bug reported: This is on a liberty release In evacuate, the image_meta is empty. So, we would get the architecture information from host. However, in the nova/virt/libvirt/blockinfo.py get_disk_bus_for_device_type, we didn't have the bus type default for ppcle or ppcle64. So, it ended up

[Yahoo-eng-team] [Bug 1502961] [NEW] libvirt spawn with configdrive failed with UnboundLocalError

Public bug reported: If we create a libvirt sever that requires configdrive, it will fail with follow error: 2015-10-05 09:02:50.714 30941 ERROR nova.compute.manager [instance: ada89410-3ce1-44bf-b1e5-f3a0a9dfd846] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2437

[Yahoo-eng-team] [Bug 1501831] [NEW] Evacuate libvirt instance failed with error 'Cannot load 'disk_format' in the base class'

Public bug reported: openstack-nova-12.0.0-201509202117 When evacuate a libvirt instance, it failed with the following error: NotImplementedError: Cannot load 'disk_format' in the base class 2015-09-30 08:04:47.484 19026 ERROR oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packag

[Yahoo-eng-team] [Bug 1499091] [NEW] Cannot create flavor with printable characters outside of 0xFFFF range

fail with this error. HTTP exception thrown: Invalid input received: Flavor names can only contain printable characters and horizontal spaces. ** Affects: nova Importance: Undecided Assignee: Christine Wang (ijuwang) Status: New ** Changed in: nova Assignee: (unassigne

[Yahoo-eng-team] [Bug 1431652] Re: os-volume_attachments return 500 error code instead of 404 if invalid volume is specified

** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1431652 Title: os-volume_attachments return 500 error code inste

[Yahoo-eng-team] [Bug 1445698] [NEW] _update_usage_from_migrations does not handling InstanceNotFound and cause compute service restart to fail

Public bug reported: Due to bug #1445674, Migration object was not set to error if there is a resize failure. Later on, if we delete the instance, the Migration object will continue to exist. If we were to restart compute service, it will fail to start since _update_usage_from_migrations Versio

[Yahoo-eng-team] [Bug 1445674] [NEW] Fix kwargs['migration'] KeyError in @errors_out_migration

ute/manager.py", line 276, in decorated_function 2015-04-17 04:53:26.418 23056 TRACE oslo_messaging.rpc.dispatcher migration = kwargs['migration'] 2015-04-17 04:53:26.418 23056 TRACE oslo_messaging.rpc.dispatcher KeyError: 'migration' 2015-04-17 04:53:26.418 23056 TRACE osl

[Yahoo-eng-team] [Bug 1431652] [NEW] os-volume_attachments return 500 error code instead of 404 if invalid volume is specified

http://localhost:8774/v2/dd069270f6634cafaf66777c4a2ee137/servers/e44ee780-0b57-4bcb-89ef-ab99e4d7d1a0/os-volume_attachments/volume-815308985 returned with HTTP 500 ** Affects: nova Importance: Undecided Assignee: Christine Wang (ijuwang) Status: New ** Changed in

[Yahoo-eng-team] [Bug 1404268] [NEW] Missing nova context during spawn

Public bug reported: The nova request context tracks a security context and other request information, including a request id that is added to log entries associated with this request. The request context is passed around explicitly in many chunks of OpenStack code. But nova/context.py also stor

[Yahoo-eng-team] [Bug 1389899] [NEW] nova delete shouldn't remove instance from DB if host is not up

Public bug reported: Under nova/compute/api.py, it will delete instance from DB if compute node is not up. I think we should utilize force-delete to handle compute node is not up scenario. So, if compute node is not up, only force- delete can delete the instance. Code flow: delete -> _delete_inst