Bug 2123696

Summary: The Value of "Allowed bootdisk types" shows up as subnetfull_host where as it is set as subnet,full_host in Satellite 6.12
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: SettingsAssignee: Ron Lavi <rlavi>
Status: CLOSED ERRATA QA Contact: Shweta Singh <shwsingh>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: apatel, lstejska, mhulan, pcreech, rlavi
Target Milestone: 6.13.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: rubygem-foreman_bootdisk-21.0.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:21:46 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:
Attachments:
Description Flags
6.11 UI view
none
6.12 UI view none

Description Sayan Das 2022-09-02 10:56:05 UTC 
Description of problem:

In Administer --> Settings --> Boot Disk page, The Value of "Allowed bootdisk types" shows up as subnetfull_host where as it is set as subnet,full_host in Satellite 6.12 

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

Satellite 6.12


How reproducible:

Always


Steps to Reproduce:
1. Install a Satellite 6.12

2. Go to Administer --> Settings --> Boot Disk page and check the value of "Allowed bootdisk types"


Actual results:

It shows up as "subnetfull_host" whereas if we edit the value, we will be able to see that it is set as "subnet,full_host"


Expected results:

UI should show the Value properly.


Additional info:

It 's a regression as in 6.11, it used to show up like this in UI,

[subnet, full_host]

whereas backend value set was -> subnet,full_host

This looks much better than how we display in in 6.12
Comment 1 Sayan Das 2022-09-02 10:59:09 UTC 
Created attachment 1909182 [details]
6.11 UI view
Comment 2 Sayan Das 2022-09-02 10:59:45 UTC 
Created attachment 1909183 [details]
6.12 UI view
Comment 3 Leos Stejskal 2022-09-08 13:17:05 UTC 
Hi,
I did some investigation, still don't know why it's happening, but about reproducing:

* It works on latest versions (foreman, foreman_theme_satellite, foreman_bootdisk)
* It doesn't work on Sat-6.12 versions (foreman-3.3, foreman_bootdisk-19.0-stable)
* foreman_satellite_theme doesn't have affect on the behavior

The issue is only in the UI, value of Setting[:bootdisk_allowed_types] is correctly saved in DB: ["subnet", "full_host"].

Since the issue is only UI, and it will be fixed in Sat 6.13, I propose to remove it from the Sat-6.12 scope,
we don't have much time before the GA and there are other issues that require our attention more.

@saydas Are you okay with postponing it to 6.13?
Comment 4 Sayan Das 2022-09-08 13:21:08 UTC 
Hello Yes. It's not causing any impact. It's just a weird UI glitch. I am fine with having it fixed in 6.13.
Comment 5 Ron Lavi 2022-11-28 08:51:27 UTC 
Created redmine issue https://projects.theforeman.org/issues/35794 from this bug
Comment 6 Bryan Kearney 2022-12-20 16:03:27 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35794 has been resolved.
Comment 7 Shweta Singh 2023-01-18 14:27:44 UTC 
Verified.

Version Tested: Satellite 6.12 Snap 6.0

Verification Steps:
1. Navigate to Menu --> Administer --> Settings
2. Click on tab Boot disk.
3. Verify value of "Allowed bootdisk types" is in correct format.

Result:
Value of "Allowed bootdisk types" is [subnet,full_host].
Comment 10 errata-xmlrpc 2023-05-03 13:21:46 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.13 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-2023:2097