[Yahoo-eng-team] [Bug 1746483] [NEW] Not able to boot from Volume / Volume snapshot when using isolated_images

Public bug reported: Description === When using isolated_images, isolated_hosts and restrict_isolated_hosts_to_isolated_images=true I'm not able to create running instance with volume/volume snapshot as a source. Instance goes to ERROR state with reason: Failed to compute_task_build_in

[Yahoo-eng-team] [Bug 1762347] [NEW] [ocata] Logout on duplicated swift container name

Public bug reported: "Create new container" form is validating name of the new container by checking access on Swift backend with each character entered. Lets create "new10" containter (when container with name "new" already exists in different project) Swift backend gets: GET /swift/v1/AUTH_xx

[Yahoo-eng-team] [Bug 1779277] [NEW] nova-conductor problem with SSL handshake

Public bug reported: After migration from Ocata to Pike I see some problems with nova- conductor. When I try to migrate a host, I get an error: 2018-06-29 10:24:42.546 811 WARNING keystoneauth.identity.generic.base [req-cc32cfb6-48ff-4803-bcea-96758514459c 5f620a8543154df1930316a7bf15f47e bd58

[Yahoo-eng-team] [Bug 1793094] [NEW] Router: add port doesn't take IP from allocation pool

Public bug reported: I have: - external network with /24 subnet with .1 as a gateway - allocation pool in this subnet (from .100 to .200) I, as a user: - create router without binding to external network - add port from external subnet I got an addr .1 (my gateway) on my new port. More: When I

[Yahoo-eng-team] [Bug 1720128] [NEW] [ocata] second instance resize fails on same host

Public bug reported: With `allow_resize_to_same_host=true` nova removes instance directory on host after confirming resize. First resize works fine, although directore is removed. Second resize fails, because nova cannot mv instance dir to instance_resize. Workaround: power cycle instance after r

[Yahoo-eng-team] [Bug 1737900] [NEW] Random volume type on create volume from image

Public bug reported: I want to create a new volume from image, starting from context menu on images list (url: horizon/project/images). There is a form, where I can specify name, size, AZ, and volume type. For all my tests, volume type is randomly choosen from existing two (in my setup). The

[Yahoo-eng-team] [Bug 1280299] Re: missing choice 'storage type' when creating a new volume during instance creation

I would like to reopen this issue. I need to have a choice of volume type when creating new volume-based instances. ** Changed in: horizon Status: Expired => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack D

[Yahoo-eng-team] [Bug 1738392] [NEW] glance location-add fails on cinder backend

Public bug reported: Hello, I'm trying to setup cinder backend for glance. After many config tries, I still fail on reaching cinder during image-create (when cinder is default store) or location-add (when is not). some of glance-api.conf: [DEFAULT] show_image_direct_url = True show_multiple_lo

[Yahoo-eng-team] [Bug 1705467] [NEW] [Get me a network] auto-allocated networks does not verify tenant ID while creating

Public bug reported: Environment: Ocata According to current docs, in order to create auto-allocated network in tenant, following command should be invoked: `neutron auto-allocated-topology-show [project_id]` Unfortunatelly, this command does not verify if given project exists, so it's easy to