[Yahoo-eng-team] [Bug 1613900] [NEW] Unable to use 'Any' availability zone when spawning instance

Public bug reported: While using Mitaka, we found that by default, using js backend, it is not possible to choose 'any' availability zone. The issue is not fixed in master branch. For python implementation the logic is: https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboar

[Yahoo-eng-team] [Bug 1580703] Re: Ironic client wrapper is unable to use keystone V3

I just needed to setup keystone v2 in an Ironic section. Still, V2 is marked as 'Deprecated' in Keystone. ** 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).

[Yahoo-eng-team] [Bug 1581246] [NEW] Ironic driver: _cleanup_deploy is called with incorrect parameters

Public bug reported: stable/mitaka release. If error happens in _generate_configdrive Ironic driver fails cleanup because of 2016-05-12 22:44:55.295 9282 ERROR nova.compute.manager [instance: 7f8769b3-145a-4b81-8175-e6aa648e1c2a] File "/usr/lib/python2.7/site-packages/nova/compute/manager.p

[Yahoo-eng-team] [Bug 1580703] [NEW] Ironic client wrapper is unable to use keystone V3

Public bug reported: While trying to set up nova-compute with an Ironic driver and keystone V3 I got an error "Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error" /etc/nov

[Yahoo-eng-team] [Bug 1559246] [NEW] Performance issues when have 1k+ Ironic BM instances

Public bug reported: We have an Ironic deployment with about 1500 BMs, 1k+ of them are already provisioned. The current Ironic architecture doesn't allow us to have more than one 'ironic compute node'. As a result nova-compute service is 100% busy with periodic tasks like updating instances statu