[Yahoo-eng-team] [Bug 1721286] Re: Create volume from image displays incorrect AZs

2018-01-03 Thread Corey Bryant 
I've verified this bug is fixed in artful-proposed and pike-proposed by
creating a volume from the images tab and it is successfully created in
the selected volume AZ.

** Changed in: cloud-archive/pike
   Status: Fix Committed => Fix Released

** Changed in: horizon (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
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:
  Fix Released
Status in Ubuntu Cloud Archive pike series:
  Fix Released
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:
  Fix Released
Status in horizon source package in Artful:
  Fix Released
Status in horizon source package in Bionic:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

  See original description.

  [Regression Potential]

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

  [Original 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@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  |  |
  |

[Yahoo-eng-team] [Bug 1721286] Re: Create volume from image displays incorrect AZs

2017-12-11 Thread Corey Bryant 
This bug was fixed in the package horizon - 3:11.0.4-0ubuntu1~cloud0
---

 horizon (3:11.0.4-0ubuntu1~cloud0) xenial-ocata; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 horizon (3:11.0.4-0ubuntu1) zesty; urgency=medium
 .
   * New stable point release for OpenStack Ocata (LP: #1736149).
   * d/p/fetch-cinder-availability-zones-list-for-volume-creation.patch:
 Cherry-pick patch from upstream stable/ocata branch to properly fetch and
 show Cinder AZs during volume creation (LP: #1721286).


** Changed in: cloud-archive/ocata
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
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:
  Fix Released
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:
  Fix Released
Status in horizon source package in Artful:
  Fix Committed
Status in horizon source package in Bionic:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

  See original description.

  [Regression Potential]

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

  [Original 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@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  |

[Yahoo-eng-team] [Bug 1721286] Re: Create volume from image displays incorrect AZs

2017-12-11 Thread Launchpad Bug Tracker 
This bug was fixed in the package horizon - 3:11.0.4-0ubuntu1

---
horizon (3:11.0.4-0ubuntu1) zesty; urgency=medium

  * New stable point release for OpenStack Ocata (LP: #1736149).
  * d/p/fetch-cinder-availability-zones-list-for-volume-creation.patch:
Cherry-pick patch from upstream stable/ocata branch to properly fetch and
show Cinder AZs during volume creation (LP: #1721286).

 -- Corey Bryant   Mon, 04 Dec 2017 08:50:37
-0500

** Changed in: horizon (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
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:
  Fix Committed
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:
  Fix Released
Status in horizon source package in Artful:
  Fix Committed
Status in horizon source package in Bionic:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

  See original description.

  [Regression Potential]

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

  [Original 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@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

[Yahoo-eng-team] [Bug 1721286] Re: Create volume from image displays incorrect AZs

2017-12-04 Thread Corey Bryant 
For Ubuntu Artful (pike), this fix is included in the following stable
point release: https://bugs.launchpad.net/cloud-archive/+bug/1734990

** Also affects: horizon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: horizon (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: horizon (Ubuntu Artful)
   Status: New => Fix Committed

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/queens
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/queens
   Status: New => Fix Released

** Changed in: cloud-archive/pike
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
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@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 |
  |

[Yahoo-eng-team] [Bug 1721286] Re: Create volume from image displays incorrect AZs

2017-10-23 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/513763
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=b9972f73b008c48618909240665e80550e7fc3ed
Submitter: Zuul
Branch:master

commit b9972f73b008c48618909240665e80550e7fc3ed
Author: Ivan Kolodyazhny 
Date:   Fri Oct 20 17:57:57 2017 +0300

Fetch Cinder availability zones list for volume creation

We have to fetch and show Cinder availability zones list during volume
creation and volume creation from image.

Change-Id: I1c8746870d94c183f5ef510c1ce09b3fc9c84220
Closes-Bug: #1721286


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1721286

Title:
  Create volume from image displays incorrect AZs

Status in OpenStack openstack-dashboard charm:
  Invalid
Status in OpenStack Dashboard (Horizon):
  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@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 |