Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 54650 - Channel Target Systems doesn't appear to work
Channel Target Systems doesn't appear to work
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Devel
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bret McMillan
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2001-10-15 09:33 EDT by Jay Turner
Modified: 2015-01-07 18:52 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-15 13:49:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Turner 2001-10-15 09:33:14 EDT
Description of Problem:
Doesn't appear that the target systems tab in the new channel details page
is presenting the correct information.

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

How Reproducible:

Steps to Reproduce:
1. Log into https://rhn.webqa.redhat.com as rhn7_pager
2. Head to
3. Notice that there are 6 systems subscribed to the 7.0 channel, but only
4 subscribed to the Powertools channel
4. Pull up the details for the Powertools channel
5. Click on the Target Systems

Actual Results:
Nothing appears; message says there are no systems which could be
subscribed to that channel

Expected Results:
Should show the other two profiles which are not subscribed to the channel,
but are to the parent channel.

Additional Information:
Comment 1 Bret McMillan 2001-10-15 13:49:25 EDT
It was correct behavior to show no system.  It's actually supposed to show only
the *entitled* target systems.

I added text to the page to clarify this.  It's checked into cvs now and will be
Comment 2 Jay Turner 2001-11-09 09:58:40 EST
This looks good on rhn.webdev.  Closing out.

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