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:
I'm using katello server and trying to register a rhel61 node using subscription manager.
Node is registered successfully, however getting following "file not found" error:
[root@dhcp201-195 ~]# subscription-manager register --username=admin --password=admin --org=sghai_org --environment=testing
The system has been registered with id: ba853c2a-5e36-4850-9378-3e637552e4b2
org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[root@dhcp201-195 ~]# subscription-manager unregister
org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Version-Release number of selected component (if applicable):
[root@dhcp201-195 ~]# rpm -qa | grep rhsm
python-rhsm-0.96.12-1.el6.noarch
[root@dhcp201-195 ~]# rpm -qa | grep subscription-manager
subscription-manager-0.96.9-1.el6.x86_64
[root@dhcp201-195 ~]#
[root@dhcp201-195 ~]# rpm -qa | grep dbus
dbus-libs-1.2.24-4.el6_0.x86_64
dbus-python-0.83.0-6.1.el6.x86_64
dbus-1.2.24-4.el6_0.x86_64
dbus-glib-0.86-5.el6.x86_64
[root@dhcp201-195 ~]#
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Expected results:
subscription-manager tool should not raise any error while performing register/unregister or any other operation.
Additional info:
I just did a "Minimal" install of /rel-eng/RHEL6.3-20120307.8/6.3/Server/x86_64/
[root@jsefler-r63-server-minimal ~]# tail -5 /root/anaconda-ks.cfg
%packages
@core
@server-policy
%end
[root@jsefler-r63-server-minimal ~]# rpm -qa | grep subscription-manager
subscription-manager-0.99.9-1.el6.x86_64
[root@jsefler-r63-server-minimal ~]# rpm -qa | grep dbus
dbus-libs-1.2.24-5.el6_1.x86_64
dbus-glib-0.86-5.el6.x86_64
dbus-python-0.83.0-6.1.el6.x86_64
[root@jsefler-r63-server-minimal ~]# ls /var/run/dbus/system_bus_socket
ls: cannot access /var/run/dbus/system_bus_socket: No such file or directory
[root@jsefler-r63-server-minimal ~]# subscription-manager register --username qa
Password:
The system has been registered with id: 57fa07a3-8a88-400e-979c-043c1ecd4e29
[root@jsefler-r63-server-minimal ~]# subscription-manager unregister
System has been un-registered.
[root@jsefler-r63-server-minimal ~]#
No org.freedesktop.DBus.Error was encountered during a register and unregister on a "Minimal" install of rhel63 server.
Moving to 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-2012-0804.html