Bug 1319275 - VM provisioning : dropdown lists greyed out in new volume fields
Summary: VM provisioning : dropdown lists greyed out in new volume fields
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 16:38 UTC by Ivan Necas
Modified: 2019-09-26 14:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:19:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dropdown lists are not greyed out anymore (89.43 KB, image/png)
2016-05-20 12:08 UTC, Kedar Bidarkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14041 0 None None None 2016-04-22 16:49:19 UTC

Description Ivan Necas 2016-03-18 16:38:26 UTC 
When provisioning a new VMWare vm, in storage section when i want to add a second volume after the default one, Datastore Cluster and Data Store drop-down lists can't be modified.
Comment 1 Ivan Necas 2016-03-18 16:38:28 UTC 
Created from redmine issue http://projects.theforeman.org/issues/14041
Comment 3 Bryan Kearney 2016-03-22 12:10:14 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14041 has been closed
-------------
Dominic Cleal
Applied in changeset commit:26eeda8011cf1c16be9446625b201c36ebe70751.
Comment 4 Kedar Bidarkar 2016-05-20 12:03:57 UTC 
While VM Provisioning, and trying to create new volume fields, the dropdown lists:

Datastore Cluster and Data Store can now be modified.


VERIFIED with sat62-snap12.1
Comment 5 Kedar Bidarkar 2016-05-20 12:08:53 UTC 
Created attachment 1159889 [details]
dropdown lists are not greyed out anymore
Comment 6 Bryan Kearney 2016-07-27 11:19:38 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-2016:1501
Note You need to log in before you can comment on or make changes to this bug.