[Bug 1721286] Re: Create volume from image displays incorrect AZs

[Corey Bryant]

Ubuntu SRU details:

[Impact]

Horizon will fetch and show the correct Cinder availability zones during
volume creation and volume creation from image.

[Test Case]

See bug description above.

[Regression Potential]

Very low as this patch is cherry-picked with no additional changes from
the upstream stable/ocata branch.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1721286

Title:
  Create volume from image displays incorrect AZs

Status in OpenStack openstack-dashboard charm:
  Invalid
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ocata series:
  New
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in Ubuntu Cloud Archive queens series:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Zesty:
  New
Status in horizon source package in Artful:
  Fix Committed
Status in horizon source package in Bionic:
  Fix Released

Bug description:
  Running openstack-origin cloud:ocata-xenial on stable/17.08 charms, we have an environment with the following Nova availability zones:
    west-java-1a
    west-java-1b
    west-java-1c
  When going to the Images tab of the project in Horizon, and selecting the far-right drop-down menu for any image and selecting "Create Volume" we are presented with a dialog which includes an Availability Zone drop-down which lists the above three AZs, none of which have a cinder-api or cinder-volume host residing within.  When trying to create a volume from an instance on this dashboard, we get the error:

  Invalid input received: Availability zone 'west-java-1a' is invalid.
  (HTTP 400)

  When using Launch Instance with Create New Image = Yes, from same
  Image on the Images tab, we still get the same AZ dropdowns, but the
  system initializes the new volume and attaches to a running instance
  in that AZ properly.

  Also, when using the Volumes tab and pressing the Create New Volume
  button, we can create a volume from any image, and the Availability
  Zone in this dialog only shows the "nova" AZ.

  To re-create, build openstack ocata-xenial with three computes, one in
  each of 3 new AZs, cinder-api, cinder-ceph, and a minimal ceph
  cluster, all with defaults and load image into glance either with
  glance-simplestreams-sync or other method.  Click into Horizon's
  Images tab of admin project and click the drop-down of an image and
  select Create Volume.  Fill out the form, you should only see the 3
  new AZs but no nova AZ for creation of the volume, it should give the
  404 error.

  You'll notice that you might have the following availability zones:
  openstack availability zone list
  +--------------+-------------+
  | Zone Name    | Zone Status |
  +--------------+-------------+
  | internal     | available   |
  | west-java-1a | available   |
  | west-java-1b | available   |
  | west-java-1c | available   |
  | nova         | available   |
  | nova         | available   |
  | nova         | available   |
  +--------------+-------------+

  This 404 error is coming from the cinder api and has nothing to do
  with glance/images.  It's simply that cinder's availability zone is
  "nova" and the nova aggregate-based availability zones should not be
  used in a cinder availability zone pull-down on the Images tab Create
  Volume dialog.

  jujumanage at cmg01z00infr001:~/charms/cinder$ openstack volume create --availability-zone nova --size 50  foo
  +---------------------+--------------------------------------+
  | Field               | Value                                |
  +---------------------+--------------------------------------+
  | attachments         | []                                   |
  | availability_zone   | nova                                 |
  | bootable            | false                                |
  | consistencygroup_id | None                                 |
  | created_at          | 2017-10-04T15:37:34.804855           |
  | description         | None                                 |
  | encrypted           | False                                |
  | id                  | ca32eb14-60f8-42c8-a5ef-d7687d25d606 |
  | migration_status    | None                                 |
  | multiattach         | False                                |
  | name                | foo                                  |
  | properties          |                                      |
  | replication_status  | None                                 |
  | size                | 50                                   |
  | snapshot_id         | None                                 |
  | source_volid        | None                                 |
  | status              | creating                             |
  | type                | None                                 |
  | updated_at          | None                                 |
  | user_id             | b327544aba2a482b9f12f1e6e615c394     |
  +---------------------+--------------------------------------+
  jujumanage at cmg01z00infr001:~/charms/cinder$ openstack volume create --availability-zone west-java-1a --size 50  foo
  Invalid input received: Availability zone 'west-java-1a' is invalid. (HTTP 400) (Request-ID: req-2f7d7d00-f361-4772-9f71-66e4ebaefdc3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1721286/+subscriptions