Bug 1432963

Summary: Change default options on dashboard
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0 (Mitaka)CC: anande, aortega, athomas, beth.white, mrunge, rdopiera, srevivo, tvignaud
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-12.0.0-0.20170624124155.e8d1dd9.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1460135 (view as bug list) Environment:
Last Closed: 2017-12-13 21:17:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1460135    

Description Eduard Barrera 2017-03-16 13:17:22 UTC
Description of problem:

In RHOSP 10, the default options when launching an instance with the dashboard have changed.

In RHOSP 9, the default boot source was always Image and Create New Volume was always No. In RHOSP 10,  the default boot source seems to be random and when Image is selected, Create New Volume is always true.

Is it possible to change this behaviour?


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

How reproducible:
always

Comment 2 Radomir Dopieralski 2017-03-16 14:35:10 UTC
This setting doesn't allow to customize everything, though. It's also possible to go back to the old launch instance dialogue with old defaults using this:

https://docs.openstack.org/developer/horizon/topics/settings.html#launch-instance-ng-enabled

Comment 3 Eduard Barrera 2017-03-20 13:14:40 UTC
Is it possible to have by default Create New Volume = No when Boot Source is Image ? Attaching image

Comment 4 Eduard Barrera 2017-03-20 13:18:46 UTC
Created attachment 1264758 [details]
Different behaviour RHOS9 and RHOS10

Comment 14 Radomir Dopieralski 2017-06-08 10:57:05 UTC
This has just been fixed upstream: https://review.openstack.org/425283

Comment 15 Beth White 2017-06-09 08:32:54 UTC
This change has been fixed upstream and therefore will be available in the OSP12 release. 

Due to the nature of this bug and the amount of work to make this work in older OSP releases, we will not be backporting this bug in all OSP releases back to 9. We are, however, fixing this in OSP10 as the long life release. Please see the following bug for updates on development progress:

https://bugzilla.redhat.com/show_bug.cgi?id=1460135

Comment 17 Beth White 2017-06-29 11:37:41 UTC
*** Bug 1299743 has been marked as a duplicate of this bug. ***

Comment 21 errata-xmlrpc 2017-12-13 21:17:04 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/RHEA-2017:3462