Created attachment 1391580 [details] Double Button Description of problem: "Delete Volume on instance delete" is appearing twice if we boot instance from volume tab under horizon dashboard. Version-Release number of selected component (if applicable): OSP11 python-django-horizon-11.0.3-3.el7ost.noarch How reproducible: Everytime (for OSP10 and OSP11) Steps to Reproduce: 1. Create a volume from image (eg : cirros) 2. Launch the instance from volume tab and select the volume as a source 3. "Delete Volume on instance delete" button will appear twice. Actual results: "Delete Volume on instance delete" is appears twice. Sometimes the volume is not predefined, which should be always there otherwise the option to launch an instance from a volume makes no sense. After pressing F5 (refresh) the volume will be predefined. The double button is always there. Same works fine if we boot instance from horizon tab. Expected results: a) There should be one "Delete Volume on instance delete" button. b) volume should alway be predefined we select volume as source. Additional info: This works fine in OSP12 version, issue seems to be in OSP10 and OSP11 version only.
Created attachment 1391581 [details] Double button not predefined
Please check if it's not already fixed in the current release.
I can confirm this is still a problem in osp13. Curiously, it only happens when the volume is freshly created. On the second attempt, the volume is not automatically selected, so the normal mechanism hides the extra fields (volume size and the second "delete volume on instance delete". It seems like the code that is supposed to hide the fields when "volume" is selected is not getting run when the volume is pre-selected.
The problem is not present in OSP14 or later, because in those versions selecting "launch as instance" doesn't pre-fill the volume field. That is probably a separate (or related) bug.
This has been now fixed as a part of another bug fix.
*** Bug 1624719 has been marked as a duplicate of this bug. ***
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-2019:2811