Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 213072 - SSM configuration: Subscribe to Channels bad text and 500 error
SSM configuration: Subscribe to Channels bad text and 500 error
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Grant Gainey
Preethi Thomas
Depends On:
Blocks: rhn500h-config-mgmt
  Show dependency treegraph
Reported: 2006-10-30 13:51 EST by Ken Ganong
Modified: 2007-04-18 13:52 EDT (History)
1 user (show)

See Also:
Fixed In Version: rhn500h
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-12 23:33:24 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 Ken Ganong 2006-10-30 13:51:30 EST
on the SSM configuration Subscribe to Channels page
Go to Systems -> Select systems -> Manage -> Configuration -> Subscribe to
Channels -> select channels -> Continue

1. text for this page still says HELPFUL TEXT!!
2. If you click the Apply Subscriptions button you will get 500 error
3. The nav doesn't show subscribe tab selected on this page.

The 500 error is about the list set tag change for the new list tag.
Comment 1 Ken Ganong 2006-10-31 15:09:41 EST
Also had some errors caused by too strict permission checking.

Fixed as of subversion revision 105175.
Comment 2 Ken Ganong 2006-11-13 12:20:25 EST
Moving bugs to ON_DEV
Comment 3 Ken Ganong 2006-12-05 09:59:11 EST
Moving my bugs to ON_QA
Comment 4 Ken Ganong 2006-12-15 16:01:49 EST
Passing on my config management bugs to ggainey
Comment 5 Preethi Thomas 2007-01-17 10:36:21 EST
verified. qapush#5
Comment 6 Preethi Thomas 2007-03-06 15:29:46 EST
verified in stage.
Comment 7 Brandon Perkins 2007-03-12 23:33:24 EDT
Closed in the rhn500h Release.

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