[Yahoo-eng-team] [Bug 1803331] [NEW] Root disk lost when resizing instance from imagebackend to rbd backed flavor

Public bug reported: We have flavor classes using different nova disk backends that are separated using host aggregates. For example, we have a flavor named l1.tiny which is using imagebackend, and s1.small using rbd backend. The hypervisors configured for imagebackend are added to the host

[Yahoo-eng-team] [Bug 1751349] [NEW] Keystone auth parameters cannot be configured in [keystone] section

Public bug reported: I am seeing nova-api attempting to use the keystone public endpoint when /v2.1/os-quota-sets is called on my Pike deployment. This is not valid in my environment; the API must use the internal endpoint to reach keystone. When the public endpoint is used, the connection sits

[Yahoo-eng-team] [Bug 1740951] [NEW] Unable to dump policy

Public bug reported: I'm having issues dumping policy from Keystone in Pike root@aio1-keystone-container-398c6a0f:~# /openstack/venvs/keystone-16.0.6/bin/oslopolicy-policy-generator --namespace keystone WARNING:stevedore.named:Could not load keystone Traceback (most recent call last): File

[Yahoo-eng-team] [Bug 1671921] [NEW] Boot from Volume invalid BDM

Public bug reported: Booting from volume in the new launch panel causes the following BDM: {"server": {"name": "test", "imageRef": "", "availability_zone ": "us-dfw-1", "key_name": "test", "flavorRef": "9340639a-2883-48ca-811f-01519e527648", "block_device_mapping": [{"volume_id":

[Yahoo-eng-team] [Bug 1671288] [NEW] live_migration_uri to live_migration_scheme SSH settings

Public bug reported: I saw in the Ocata release notes that live_migration_uri is deprecated, and there is mention of a new setting called live_migration_scheme. However, the new config option live_migration_scheme does not appear in the ocata configuration reference[1]. I am also curious how the

[Yahoo-eng-team] [Bug 1601964] [NEW] Policy file distribution breaks security group panel

Public bug reported: When using POLICY_FILES_PATH and POLICY_FILES with Mitaka Horizon + Default nova/neutron policy files, the security group CRUD options are not showing up. After I add "create_security_group": "" to the neutron policy file, the create button shows up. This behavior did not

[Yahoo-eng-team] [Bug 1489194] [NEW] hw_scsi_model from glance image is not used when booting instance from new volume

Public bug reported: When creating an instance backed by a cinder volume, the disk device /dev/vda is used regardless of image settings. I am using the following image metadata to set virtio-scsi driver on my instances: hw_disk_bus=scsi hw_scsi_model=virtio-scsi When I boot instances using a