Bug 1635193 - Content Source field gets blank after editing a provisioned host
Summary: Content Source field gets blank after editing a provisioned host
Keywords:
Status: CLOSED DUPLICATE of bug 1564740
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.3.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-02 10:14 UTC by Mahesh Yadav
Modified: 2021-12-10 17:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-02 10:49:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mahesh Yadav 2018-10-02 10:14:03 UTC
Description of problem:
The Content source field gets blank after editing a provisioned host.
Editing back the provisioned host doesn't show the content source field.

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

How reproducible:
Yes it is reproducible

Steps to Reproduce:
1. Selecting the Content Source while provisioning, In this case host group does not have content source configured. Business requirement, hence selecting the content source manually while provisioning a host.
2. Once the host is provisioned, Editing the host should suppose to show the content source field which is appearing blank.
3. The content source field goes blank after editing the host. 

Actual results:
The content source field goes blank after editing the host. 


Expected results:
Editing the host should suppose to show the content source field 


Additional info:
In this case Host group does not have content source configured. User select host group and then select the content source according to business requirement.
This was working in Satellite 6.2

Comment 1 Mahesh Yadav 2018-10-02 10:49:07 UTC

*** This bug has been marked as a duplicate of bug 1564740 ***


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