Bug 1207306

Summary: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Product: Red Hat Enterprise Linux 6 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: Devan Goodwin <dgoodwin>
Status: CLOSED ERRATA QA Contact: John Sefler <jsefler>
Severity: high Docs Contact:
Priority: high    
Version: 6.7CC: alikins, dgoodwin, gpatil, redakkan, skallesh, vmeghana, wpoteat
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:53:38 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:
Bug Depends On:    
Bug Blocks: 1125249    

Description John Sefler 2015-03-30 16:22:58 UTC
Description of problem:
Automated test execution against subscription-manager-1.14.1 and subscription-manager-1.14.2 occasionally hits a dbus Traceback.

I suspect code originally written to satisfy RFE bug 884285 is causing these tracebacks.  In fact, the offending code was stripped from subscription-manager branched for release on rhel7.1 as described in https://bugzilla.redhat.com/show_bug.cgi?id=884285#c20.  I think we may want to strip it from subscription-manager master too.


Version-Release number of selected component (if applicable):
subscription-manager-1.14.1
subscription-manager-1.14.2

How reproducible:
not easily

Steps to Reproduce:
Pasted from an test automation log...
ssh root.redhat.com subscription-manager unsubscribe --all
Stdout:
3 subscriptions removed at the server.
3 local certificates have been deleted.
Stderr:
Traceback (most recent call last):
File "/usr/share/rhsm/subscription_manager/dbus_interface.py", line 59, in emit_status
self.validity_iface.emit_status()
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
ExitCode: 0

Comment 2 John Sefler 2015-03-30 17:47:47 UTC
Although a regression from rhel6.6, this is not a blocker for rhel6.7 because it occurs rarely and when it does occur, you can re-try and probably succeed.

Comment 3 John Sefler 2015-03-30 19:12:13 UTC
Here's another occurrence encountered with subscription-manager-1.14.2-1.git.1.6470ef0.el6.x86_64 against the stage candlepin...

ssh root.lab.eng.bos.redhat.com subscription-manager unsubscribe --all
Stdout:
1 subscription removed at the server.
1 local certificate has been deleted.
Stderr:
Traceback (most recent call last):
File "/usr/share/rhsm/subscription_manager/dbus_interface.py", line 59, in emit_status
self.validity_iface.emit_status()
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ExitCode: 0

Comment 4 Adrian Likins 2015-04-07 16:40:52 UTC
I've seen this and variations of it in cases where subman wasn't installed from an rpm, and the "dbus-send --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig" from the %post wasn't run. That might be an issue, depending on how the tests are setup.

I do suspect there is still some https://bugzilla.redhat.com/show_bug.cgi?id=884285 related wackiness we need to revert for 6.7.

Comment 5 John Sefler 2015-04-07 17:13:41 UTC
QE always installs subscription-manager and python-rhsm onto RHEL from an rpm.

Comment 6 Devan Goodwin 2015-04-07 18:16:55 UTC
*** Bug 1198976 has been marked as a duplicate of this bug. ***

Comment 7 Devan Goodwin 2015-04-07 18:21:02 UTC
*** Bug 1200340 has been marked as a duplicate of this bug. ***

Comment 8 Devan Goodwin 2015-04-09 18:44:41 UTC
We believe this will be fixed by reverting the dbus code that triggers events on compliance status changes.

subscription-manager.git: cf23450fc1d519a7d0e90611499047ce2e7c3334
Will appear in subscription-manager-1.15.3-1

Comment 10 Shwetha Kallesh 2015-04-15 08:33:00 UTC
Dont see any trace back now,marking bug as verified!!

[root@dhcp35-236 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.26.8-1
subscription management rules: 5.12
subscription-manager: 1.14.5-1.el6
python-rhsm: 1.14.2-1.el6

[root@dhcp35-236 ~]# subscription-manager register 
Username: qa
Password: 
The system has been registered with ID: fd4f099c-ecd9-4cce-b0ea-194a10a8972a 
[root@dhcp35-236 ~]# subscription-manager attach --auto


Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

Product Name: Awesome OS Instance Server Bits
Status:       Not Subscribed

Product Name: Awesome OS Server Bits
Status:       Not Subscribed

Unable to find available subscriptions for all your installed products.
[root@dhcp35-236 ~]# subscription-manager remove --all
1 subscription removed at the server.
1 local certificate has been deleted.
[root@dhcp35-236 ~]# subscription-manager unregister
System has been unregistered.

Comment 11 errata-xmlrpc 2015-07-22 06:53:38 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-1345.html