Description of problem: Error message given when "up2date --channel=(anychannel) -l" is run with a channel specified to which the client is not subscribed: "This system may not be updated until it is associated with a channel." The error is misleading. The system is associated with a channel, just not that particular one. Version-Release number of selected component (if applicable): up2date-4.4.69-8 How reproducible: always Steps to Reproduce: 1. Register an i386 system to hosted. 2. Run up2date --channel=rhn-tools-rhel-3-as-ia64 -l. This is a valid channel, but the system is not subscribed to it. Actual results: [root@test07 root]# up2date --channel=rhn-tools-rhel-3-as-ia64 -l An error has occurred: This system may not be updated until it is associated with a channel. See /var/log/up2date for more information Expected results: It should say something like: 1- If the channel does not exist on the server: "The specified channel does not exist." 2- If the channel is valid but the system is not subscribed to it: "The system is not subscribed to the specified channel." Additional info: [Fri May 12 16:43:40 2006] up2date updating login info [Fri May 12 16:43:40 2006] up2date logging into up2date server [Fri May 12 16:43:40 2006] up2date successfully retrieved authentication token from up2date server [Fri May 12 16:43:40 2006] up2date This system may not be updated until it is associated with a channel. [Fri May 12 16:43:40 2006] up2date File "/usr/sbin/up2date", line 1282, in ? sys.exit(main() or 0) File "/usr/sbin/up2date", line 601, in main rhnChannel.setChannels(tempchannels) File "/usr/share/rhn/up2date_client/rhnChannel.py", line 285, in setChannels return getChannels(label_whitelist=whitelist) File "/usr/share/rhn/up2date_client/rhnChannel.py", line 183, in getChannels raise up2dateErrors.NoChannelsError(_("This system may not be updated until it is associated with a channel."))
User bnackash's account has been closed
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.