Bug 1012134 - The base channel change confirmation page contains overly specific text
The base channel change confirmation page contains overly specific text
Status: NEW
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI (Show other bugs)
560
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomas Lestach
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2013-09-25 15:34 EDT by Stephen Herr
Modified: 2015-08-10 15:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Herr 2013-09-25 15:34:35 EDT
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.

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