Bug 2070487 - Setting a Content Source is not persistent
Summary: Setting a Content Source is not persistent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.15.0
Assignee: Lucy Fu
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-31 09:08 UTC by Stephen Wadeley
Modified: 2024-04-23 17:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:11:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35834 0 Normal New Setting a Content Source is not persistent 2022-12-07 13:41:54 UTC
Red Hat Issue Tracker SAT-11960 0 None None None 2024-01-16 16:35:02 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:11:09 UTC

Description Stephen Wadeley 2022-03-31 09:08:48 UTC
Description of problem:

Saving a Content Source appears to work but on reopening the Edit view the setting is blank.

If you set Lifecycle Environment and Content View, and then Content Source, the Media, Partition Table, and Root Password settings are lost and have to be reselected.

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


How reproducible:
Every time


Steps to Reproduce:
1. Create a host with the follow values:
make_fake_host(
        {
            'organization-id': module_host_template.organization.id,
            'architecture-id': module_host_template.architecture.id,
            'domain-id': module_host_template.domain.id,
            'location-id': module_host_template.location.id,
            'medium-id': module_host_template.medium.id,
            'operatingsystem-id': module_host_template.operatingsystem.id,
            'partition-table-id': module_host_template.ptable.id,
        }
2. Open the host for editing and select a Content Source, Submit to save the changes.
3. Open the host for editing and check the Content Source to see if the change persisted.
4. Select the Lifecycle Environment and Content View, and then Content Source. Try to submit the changes.

Actual results:
A change to the Content Source does not persist.
The Media, Partition Table, and Root Password settings are lost and have to be reselected.


Expected results:
A change to the Content Source does persist.
The Media, Partition Table, and Root Password settings are not lost.

Additional info:
Test is using fake capsules

Comment 11 Lucy Fu 2022-12-07 13:41:54 UTC
Created redmine issue https://projects.theforeman.org/issues/35834 from this bug

Comment 12 Bryan Kearney 2022-12-07 16:02:51 UTC
Upstream bug assigned to lufu

Comment 13 Bryan Kearney 2022-12-07 16:02:53 UTC
Upstream bug assigned to lufu

Comment 14 Bryan Kearney 2023-04-06 16:02:35 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35834 has been resolved.

Comment 16 Sam Bible 2024-01-18 21:13:36 UTC
Verified on 6.15 - Snap 5

Steps to Verify:
1. Create a host, and setup the environment for it properly.
2. Verify that the workflow for Create/Edit Host has been updated properly to follow the changes made to address this BZ
  - Edit Host page offers a Hyperlink to the Change Content Source workflow, and LCE/CV/Content Source fields are visible but disabled
  - Create Host page shows all these fields by default.

Expected Results:
The workflows are properly adjusted to these changes, and fields are disabled where appropriate

Actual Results:
The workflows are properly adjusted to these changes, and fields are disabled where appropriate

Comment 19 errata-xmlrpc 2024-04-23 17:11:08 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.15.0 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-2024:2010


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