Bug 1012134

Summary: The base channel change confirmation page contains overly specific text
Product: Red Hat Satellite 5 Reporter: Stephen Herr <sherr>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 560   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-09 10:49:56 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:
Bug Depends On:    
Bug Blocks: 462714    

Description Stephen Herr 2013-09-25 19:34:35 UTC 
Description of problem:
If you change your base channel and Satellite is not able to automatically map a child channel to a child of the new base, then it will display a warning. That warning is overly specific, assuming that you are changing the base channel to an EUS channel instead of a generic custom channel.

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

How reproducible:
always

Steps to Reproduce:
1. Have a system profile that is subscribed to at least one base channel.
2. Clone the base channel, but don't clone the child channel.
3. Change the systems base channel to the cloned channel
4. On the confirmation page you will see:

Actual results:
Warning: If you have installed packages from any channels that are highlighted above, those packages will no longer receive software updates, including critical security updates, when this system is moved to Extended Update Support. 

Expected results:
Warning: If you have installed packages from any channels that are highlighted above, those packages will no longer receive software updates, including critical security updates, when this system is moved to the new base channel.
Comment 1 Tomas Lestach 2018-04-09 10:49:56 UTC 
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.