Bug 681725 - ISE when sending HW profile from 6Client
Summary: ISE when sending HW profile from 6Client
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Backend
Version: rhn522
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: rhn-dev-list
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 03:09 UTC by Jan Hutař
Modified: 2017-07-05 15:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jan Hutař 2011-03-03 03:09:48 UTC
Description of problem:
I'm getting ISE when I'm registering or syncing profile against Hosted (Prod on rhn.redhat.com). I do not see this ISE when registering against RHN Satellite 5.4.0.


Version-Release number of selected component (if applicable):
rhnlib-2.5.22-9.el6.noarch
rhn-client-tools-1.0.0-39.el6.noarch
What is now on Prod


How reproducible:
always


Steps to Reproduce:
1. rhnrek_ks ... (without --nohardware)

or

1. rhn-profile-sync


Actual results:
# rhn-profile-sync 
Updating package profile...
Updating hardware profile...
An error has occurred:
Internal Server Error
See /var/log/up2date for more information
# less /var/log/up2date
[Wed Mar  2 22:00:43 2011] up2date Updating package profile
[Wed Mar  2 22:00:48 2011] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhn-profile-sync", line 55, in <module>
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 74, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhn-profile-sync", line 46, in main
    rhnHardware.updateHardware()
  File "/usr/share/rhn/up2date_client/rhnHardware.py", line 12, in updateHardware
    hardwareList)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 39, in _request1
    ret = self._request(methodname, params)
  File "/usr/lib/python2.6/site-packages/rhn/rpclib.py", line 387, in _request
    raise pe
<class 'xmlrpclib.ProtocolError'>: <ProtocolError for xmlrpc.rhn.redhat.com /XMLRPC: 500 Internal Server Error>


Expected results:
Should work

Comment 6 Thomas "Shea" DeAntonio 2017-07-05 15:15:59 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Comment 7 Thomas "Shea" DeAntonio 2017-07-05 15:16:00 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).


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