Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This bug is very similar to bug 818786 and probably reproducible using the same steps. Below is a trace from a recent automation test run attempting to migrate a classic system consuming many RHN Channels. Notice at the end: ssl.SSLError: The read operation timed out.
The problem that remains when this error occurs is:
1. the rhn systemid file remains on the system even though RHN Classic appears to have mostly unregistered leaving the system in a funky state.
> [root@jsefler-6 ~]# yum repolist
> Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
> This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
> There was an error communicating with RHN.
> RHN channel support will be disabled.
> Error communicating with server. The message was:
>
> Error Message:
> Please run rhn_register (or up2date --register on Red Hat Enterprise Linux 3 or later)
> as root on this client
> Error Class Code: 9
> Error Class Info: Invalid System Credentials.
> Explanation:
> An error has occurred while processing your request. If this problem
> persists please enter a bug report at bugzilla.redhat.com.
> If you choose to submit the bug report, please be sure to include
> details of what you were trying to do when this error occurred and
> details on how to reproduce this problem.
>
> repolist: 0
> [root@jsefler-6 ~]#
2. Because the script aborted during the traceback, the system's registration to RHN Classic is not well defined AND the system has not even attempted registration to RHSM. Hence the system is definitely not compliant and NOT receiving any updates.
My suggested improvement is that the script should catch this exception and then...
A. spit out a message stating something like: "Did not receive a completed unregistration message from RHN Classic for profile 'rhsm-automation.jsefler-6.usersys.redhat.com' with RHN System ID '1023719104'. Please investigate on the Customer Portal."
B. march on with the rest of the script moving the /etc/sysconfig/rhn/systemid to systemid.save and then continuing with the RHSM registration process.
Version-Release number of selected component (if applicable):
[root@jsefler-6 ~]# rpm -q subscription-manager-migration
subscription-manager-migration-1.1.10-1.el6.x86_64
How reproducible:
usually occurs when many (greater than 60) RHN Channels are classically consumed. In the case above, it occurred which consuming 40 child channels. Usually 40 channels can be migrated within the SSL timeout limit.
Steps to Reproduce:
see bug 818786
ssh root.redhat.com rhn-migrate-classic-to-rhsm.tcl '--force --servicelevel=Premium' qa redhatqa testuser1 password admin null
Stdout:
spawn rhn-migrate-classic-to-rhsm --force --servicelevel=Premium
Red Hat account: qa
Password:
System Engine Username: testuser1
Password:
Org: admin
Retrieving existing RHN Classic subscription information ...
+-----------------------------------------------------+
System is currently subscribed to these RHN Classic Channels:
+-----------------------------------------------------+
rhel-x86_64-server-6
rhel-x86_64-server-clusteredstorage-6-beta
rhel-x86_64-server-6-osop-1-jbosseap-debuginfo
rhel-x86_64-server-6-osop-1-infrastructure-beta-debuginfo
rhel-x86_64-server-6-osop-1-infrastructure-debuginfo
rhel-x86_64-server-rhsclient-6
rhel-x86_64-server-dts-6-beta-debuginfo
rhel-x86_64-server-dts-6
sam-rhel-x86_64-server-6-debuginfo
sam-rhel-x86_64-server-6-beta-debuginfo
rhel-x86_64-server-6-rhevm-3-beta-debuginfo
rhel-x86_64-rhev-agent-6-server-beta-debuginfo
rhel-x86_64-rhev-mgmt-agent-6-debuginfo
rhel-x86_64-server-6-rhevh
rhel-x86_64-server-6-cf-tools-1-beta
rhel-x86_64-rhev-agent-6-server
rhel-x86_64-rhev-mgmt-agent-6
rhel-x86_64-server-6-mrg-grid-2
rhel-x86_64-server-6-cf-se-1-beta-debuginfo
rhel-x86_64-server-6-cf-ce-1
rhel-x86_64-server-ei-replication-6-debuginfo
rhel-x86_64-server-hts-6-beta
rhn-tools-rhel-x86_64-server-6
rhel-x86_64-server-sjis-6-beta
rhel-x86_64-server-sap-6
rhel-x86_64-server-hpn-6-beta-debuginfo
rhel-x86_64-server-hpn-6
rhel-x86_64-server-supplementary-6-debuginfo
rhel-x86_64-server-sfs-6
rhel-x86_64-server-rs-6-htb-debuginfo
rhel-x86_64-server-optional-6-htb-debuginfo
rhel-x86_64-server-lb-6-htb
rhel-x86_64-server-lb-6
rhel-x86_64-server-ha-fastrack-6-debuginfo
rhel-x86_64-server-ha-6-htb
rhel-x86_64-server-fastrack-6-debuginfo
rhel-x86_64-server-fastrack-6
rhel-x86_64-server-6-htb-debuginfo
rhel-x86_64-server-optional-6-beta
rhel-x86_64-server-6-osop-1-rhc-debuginfo
rhel-x86_64-server-6-osop-1-rhc-beta
+-----------------------------------------------------+
No product certificates are mapped to these RHN Classic channels:
+-----------------------------------------------------+
rhel-x86_64-server-clusteredstorage-6-beta
rhel-x86_64-server-rhsclient-6
sam-rhel-x86_64-server-6-beta-debuginfo
rhel-x86_64-server-6-mrg-grid-2
rhel-x86_64-server-ei-replication-6-debuginfo
rhel-x86_64-server-hts-6-beta
rhn-tools-rhel-x86_64-server-6
rhel-x86_64-server-rs-6-htb-debuginfo
rhel-x86_64-server-optional-6-htb-debuginfo
rhel-x86_64-server-lb-6-htb
rhel-x86_64-server-ha-fastrack-6-debuginfo
rhel-x86_64-server-ha-6-htb
rhel-x86_64-server-fastrack-6-debuginfo
rhel-x86_64-server-fastrack-6
rhel-x86_64-server-6-htb-debuginfo
+-----------------------------------------------------+
Installing product certificates for these RHN Classic channels:
+-----------------------------------------------------+
rhel-x86_64-server-6
rhel-x86_64-server-6-osop-1-jbosseap-debuginfo
rhel-x86_64-server-6-osop-1-infrastructure-beta-debuginfo
rhel-x86_64-server-6-osop-1-infrastructure-debuginfo
rhel-x86_64-server-dts-6-beta-debuginfo
rhel-x86_64-server-dts-6
sam-rhel-x86_64-server-6-debuginfo
rhel-x86_64-server-6-rhevm-3-beta-debuginfo
rhel-x86_64-rhev-agent-6-server-beta-debuginfo
rhel-x86_64-rhev-mgmt-agent-6-debuginfo
rhel-x86_64-server-6-rhevh
rhel-x86_64-server-6-cf-tools-1-beta
rhel-x86_64-rhev-agent-6-server
rhel-x86_64-rhev-mgmt-agent-6
rhel-x86_64-server-6-cf-se-1-beta-debuginfo
rhel-x86_64-server-6-cf-ce-1
rhel-x86_64-server-sjis-6-beta
rhel-x86_64-server-sap-6
rhel-x86_64-server-hpn-6-beta-debuginfo
rhel-x86_64-server-hpn-6
rhel-x86_64-server-supplementary-6-debuginfo
rhel-x86_64-server-sfs-6
rhel-x86_64-server-lb-6
rhel-x86_64-server-optional-6-beta
rhel-x86_64-server-6-osop-1-rhc-debuginfo
rhel-x86_64-server-6-osop-1-rhc-beta
Product certificates installed successfully to /tmp/migratedProductCertDir.
Preparing to unregister system from RHN Classic ...
Traceback (most recent call last):
File "/usr/sbin/rhn-migrate-classic-to-rhsm", line 713, in <module>
main()
File "/usr/sbin/rhn-migrate-classic-to-rhsm", line 698, in main
unRegisterSystemFromRhnClassic(sc, sk)
File "/usr/sbin/rhn-migrate-classic-to-rhsm", line 378, in unRegisterSystemFromRhnClassic
result = sc.system.deleteSystems(sk, systemId)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1237, in request
errcode, errmsg, headers = h.getreply()
File "/usr/lib64/python2.6/httplib.py", line 1064, in getreply
response = self._conn.getresponse()
File "/usr/lib64/python2.6/httplib.py", line 990, in getresponse
response.begin()
File "/usr/lib64/python2.6/httplib.py", line 391, in begin
version, status, reason = self._read_status()
File "/usr/lib64/python2.6/httplib.py", line 349, in _read_status
line = self.fp.readline()
File "/usr/lib64/python2.6/socket.py", line 433, in readline
data = recv(1)
File "/usr/lib64/python2.6/ssl.py", line 215, in recv
return self.read(buflen)
File "/usr/lib64/python2.6/ssl.py", line 136, in read
return self._sslobj.read(len)
ssl.SSLError: The read operation timed out
Stderr:
ExitCode: 1
commit 7bfbf4ffd9f336bd28f8cb2ee3582361fd30f011
Author: Alex Wood <awood>
Date: Fri Nov 30 14:37:57 2012 -0500
881952: Warn and continue if encountering a failure during system deletion.
Requests to RHN Classic to delete a system can sometimes run long
enough to timeout. Instead of throwing a stacktrace and aborting,
we now warn the user of the potential failure then do the
necessary local clean-up.
Got following message while migrating with many subscription
Preparing to unregister system from RHN Classic ...
Did not receive a completed unregistration message from RHN Classic for system 1023878699.
Please investigate on the Customer Portal at https://access.redhat.com.
Attempting to register system to Red Hat Subscription Management ...
The system has been registered with id: 9909bb77-d56e-4784-a16f-d4509fd252ce
System 'dhcp193-87.pnq.redhat.com' successfully registered to Red Hat Subscription Management.
As per comment 5 its working fine , so resolving defect as verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0350.html