Bug 1729968

Summary:	Editing disk size of a Compute Profile for a VMware Compute Resource makes the whole Storage section disappear
Product:	Red Hat Satellite	Reporter:	Ron van der Wees <rvdwees>
Component:	Compute Resources - VMWare	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Radek Mynar <rmynar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5.0	CC:	chrobert, egolov, mhulan, oezr, rmynar
Target Milestone:	6.8.0	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-1.22.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:58:49 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:

Description Ron van der Wees 2019-07-15 12:43:23 UTC

Description of problem:

When editing the disk size of a Compute Profile for a VMware Compute Resource,
selecting and removing the value for Size makes the whole Storage section of
this page disappear. This does not happen when selecting the existing value
and iso. removing the existing value, directly start entering a new value!

Version-Release number of selected component (if applicable):
satellite-6.5.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a Compute Resource with Provider VMware
2. goto https://<sat>/compute_profiles
3. Select an existing CP
4. Select the newly created CR from 1
5. Under storage select the value for the size
6. Press <backspace>

Actual results:
The whole Storage section of this compute profile disappears!

Expected results:
Value for the existing disk size to be empty by the Storage section to be
present.


Additional info:
So far this seems only related to the VMware provider. Tested with for example
RHV and this does not happen with that provider.

Comment 2 Ondřej Ezr 2020-03-04 00:14:40 UTC

This is already solved in upstream and fixed in satellite 6.6

Comment 3 Bryan Kearney 2020-03-04 01:00:39 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26273 has been resolved.

Comment 4 Radek Mynar 2020-06-29 17:23:38 UTC

VERIFIED with Satellite 6.8 SNAP 6.0

I followed steps from initial comment. The Storage section stayed visible all the time.

Comment 7 errata-xmlrpc 2020-10-27 12:58:49 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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366