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.

Bug 1394939

Summary:	Software Update fails with an internal system error
Product:	Red Hat Enterprise Linux 6	Reporter:	JC Vickers <jcvickers>
Component:	PackageKit	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.8
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 11:47:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description JC Vickers 2016-11-14 20:00:14 UTC

Description of problem:

Bringing up the Software Update tool throws an internal system error.  Details provided are:

Error Type: <class 'up2date_client.up2dateErrors.NetworkError'>
Error Value: rhn-plugin: Network error: 
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3282, in <module>
    main()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3278, in main
    backend = PackageKitYumBackend('', lock=True)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 238, in __init__
    self.doLock()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 321, in doLock
    self.yumbase.doLock(YUM_PID_FILE)
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 1837, in doLock
    if self.conf.uid != 0:
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 911, in <lambda>
    conf = property(fget=lambda self: self._getConfig(),
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 363, in _getConfig
    self.plugins.run('init')
  File : /usr/lib/python2.6/site-packages/yum/plugins.py, line 184, in run
    func(conduitcls(self, self.base, conf, **kwargs))
  File : /usr/share/yum-plugins/rhnplugin.py, line 118, in init_hook
    login_info = up2dateAuth.getLoginInfo(timeout=timeout)
  File : /usr/share/rhn/up2date_client/up2dateAuth.py, line 219, in getLoginInfo
    login(timeout=timeout)
  File : /usr/share/rhn/up2date_client/up2dateAuth.py, line 186, in login
    li = server.up2date.login(systemId)
  File : /usr/share/rhn/up2date_client/rhnserver.py, line 51, in __call__
    return rpcServer.doCall(method, *args, **kwargs)
  File : /usr/share/rhn/up2date_client/rpcServer.py, line 210, in doCall
    ret = method(*args, **kwargs)
  File : /usr/lib64/python2.6/xmlrpclib.py, line 1199, in __call__
    return self.__send(self.__name, args)
  File : /usr/share/rhn/up2date_client/rpcServer.py, line 40, in _request1
    ret = self._request(methodname, params)
  File : /usr/lib/python2.6/site-packages/rhn/rpclib.py, line 386, in _request
    self._handler, request, verbose=self._verbose)
  File : /usr/lib/python2.6/site-packages/rhn/transports.py, line 188, in request
    return self._process_response(fd, connection)
  File : /usr/lib/python2.6/site-packages/rhn/transports.py, line 195, in _process_response
    fd = resp.decode(fd)
  File : /usr/lib/python2.6/site-packages/rhn/transports.py, line 450, in decode
    fd.close()
  File : /usr/lib64/python2.6/httplib.py, line 544, in close
    self.fp.close()
  File : /usr/lib/python2.6/site-packages/rhn/SSL.py, line 118, in close
    self._really_close()
  File : /usr/lib/python2.6/site-packages/rhn/SSL.py, line 123, in _really_close
    self._connection.shutdown()

Acknowledging the error, produces a dialog indicating all software is up to date.


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


How reproducible:


Steps to Reproduce:
1. Select System => Administration => Software Update
2.
3.

Actual results:

Software Update base window displays, followed immediately by a dialog indicating an internal system error occurred.  Selecting Details gives the output described above.  Acknowledging the error dismisses the Software Update.


Expected results:

Software Update populates with installed packages.


Additional info:

Running RHEL 6.8 in a VirtualBox VMcan on Windows 7

Comment 2 Jan Kurik 2017-12-06 11:47:50 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/