Bug 1732244 - Add hide_create_volume to LAUNCH_INSTANCE_DEFAULTS on RHOSP13
Summary: Add hide_create_volume to LAUNCH_INSTANCE_DEFAULTS on RHOSP13
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 13.0 (Queens)
Hardware: All
OS: Linux
medium
medium
Target Milestone: z13
: 13.0 (Queens)
Assignee: Tatiana Ovchinnikova
QA Contact: ikanias
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-23 04:58 UTC by Meiyan Zheng
Modified: 2024-06-13 22:11 UTC (History)
11 users (show)

Fixed In Version: python-django-horizon-13.0.3-8.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-18 13:08:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:0932 0 None None None 2021-03-18 13:10:06 UTC

Description Meiyan Zheng 2019-07-23 04:58:56 UTC
Description of problem:

There is commit in upstream to hide "Create New Volume" option and have
it rely on the default value that is provide with the create_volume 
option.when launching instance. 
Is it possible to back port it to downstream RHOSP13? 

https://github.com/openstack/horizon/commit/132243183a7cffe6f05571ea48342df5ad9ef73e
https://review.opendev.org/#/c/605813/


Version-Release number of selected component (if applicable):
RHOSP13

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 13 errata-xmlrpc 2021-03-18 13:08:47 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 (Red Hat OpenStack Platform 13.0 bug fix and enhancement 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-2021:0932


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