Bug 1549128 - [RFE][CloudForms][Storage] Create a new volume choosing availability zones
Summary: [RFE][CloudForms][Storage] Create a new volume choosing availability zones
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.11.0
Assignee: Sam Lucidi
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-26 13:17 UTC by Neha Chugh
Modified: 2019-12-12 13:34 UTC (History)
16 users (show)

Fixed In Version: 5.11.0.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:33:51 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:34:11 UTC

Description Neha Chugh 2018-02-26 13:17:48 UTC
Description of problem:
Unable to choose the availability zone while adding cloud volume

Version-Release number of selected component (if applicable):
5.9.0.20.20180206200727_d1873b9.

How reproducible:
Always

Steps to Reproduce:
  1. Navigate to "Storage -> Block Storage -> Volumes".
  2. In "Configuration" add a new cloud volume.
  3. Create a new volume choossing your Storage Manager, cloud tenant, volume name and size. 


Actual results:
The new cloud volumes always are created in the first availability zone. Then, when you try attach this cloud volume to an instance in other availability zone, you see an error.

Expected results:
You should be able to choose the cloud volume availability zone when created.

Additional info:
The OSP connection is with admin user.

Comment 4 Jerry Keselman 2019-01-10 15:28:43 UTC
OpenStack?  Amazon?  Both?

Comment 9 Alexander Demicev 2019-01-14 13:54:00 UTC
https://github.com/ManageIQ/manageiq-ui-classic/pull/5155

Comment 11 Jerry Keselman 2019-01-24 13:35:59 UTC
Nope.

Comment 21 Ido Ovadia 2019-07-31 14:28:26 UTC
Verified:
=========
5.11.0.16

Comment 23 errata-xmlrpc 2019-12-12 13:33:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4199


Note You need to log in before you can comment on or make changes to this bug.