Bug 1542115 - [Horizon] "Delete Volume on instance delete" is appearing twice if we boot instance from volume tab under horizon dashboard.
Summary: [Horizon] "Delete Volume on instance delete" is appearing twice if we boot in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Upstream M1
: 15.0 (Stein)
Assignee: Radomir Dopieralski
QA Contact: Eldar Weiss
URL:
Whiteboard:
: 1624719 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-05 15:34 UTC by MD Sufiyan
Modified: 2021-03-11 17:06 UTC (History)
9 users (show)

Fixed In Version: python-django-horizon-15.0.0-0.20190123153319.4a8d00d.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 11:15:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Double Button (70.27 KB, image/jpeg)
2018-02-05 15:34 UTC, MD Sufiyan
no flags Details
Double button not predefined (69.03 KB, image/jpeg)
2018-02-05 15:35 UTC, MD Sufiyan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 600399 0 None MERGED Select correct boot source when launching instance from different sources 2020-10-07 13:33:47 UTC
Red Hat Product Errata RHEA-2019:2811 0 None None None 2019-09-21 11:15:50 UTC

Description MD Sufiyan 2018-02-05 15:34:49 UTC
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.

Comment 1 MD Sufiyan 2018-02-05 15:35:47 UTC
Created attachment 1391581 [details]
Double button not predefined

Comment 2 Udi Kalifon 2018-03-28 13:20:49 UTC
Please check if it's not already fixed in the current release.

Comment 4 Radomir Dopieralski 2018-08-28 13:47:33 UTC
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.

Comment 5 Radomir Dopieralski 2018-08-28 14:56:57 UTC
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.

Comment 7 Radomir Dopieralski 2018-09-18 09:21:16 UTC
This has been now fixed as a part of another bug fix.

Comment 8 Radomir Dopieralski 2018-09-19 12:23:14 UTC
*** Bug 1624719 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2019-09-21 11:15:27 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-2019:2811


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