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 813297 - Got Traceback with changed hostname
Summary: Got Traceback with changed hostname
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 7.0
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2012-04-17 12:31 UTC by spandey
Modified: 2015-04-23 23:57 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:50:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description spandey 2012-04-17 12:31:02 UTC 
Description of problem:


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


How reproducible:
3/3

Prerequisites : 
Rhel6.3 with following subscription-manager rpm .
subscription-manager-migration-0.99.14-1.git.2.cf76d8e.el6_2.x86_64
subscription-manager-gnome-0.99.14-1.git.2.cf76d8e.el6_2.x86_64
subscription-manager-0.99.14-1.git.2.cf76d8e.el6_2.x86_64
subscription-manager-firstboot-0.99.14-1.git.2.cf76d8e.el6_2.x86_64
subscription-manager-migration-data-1.12.1.3-1.git.0.1b05607.el6_2.noarch

Steps to Repro : 
Login to client console .
Change hostname using following command 
hostname test2
Now launch subscription-manager-gui using subscription-manager-gui command. 

Expected Result : 
Command should successfully executed , and it should open subscription-manager gui 

Actual Result : 
Got Following traceback.

[root@test1 ~]# hostname test2
[root@test1 ~]# subscription-manager-gui 
/usr/sbin/subscription-manager-gui:31: DeprecationWarning: The dbus_bindings module is not public API and will go away soon.

Most uses of dbus_bindings are applications catching the exception
dbus.dbus_bindings.DBusException. You should use dbus.DBusException
instead (this is compatible with all dbus-python versions since 0.40.2).

If you need additional public API, please contact the maintainers via
<dbus.org>.

  import dbus.dbus_bindings
No protocol specified
Traceback (most recent call last):
  File "/usr/sbin/subscription-manager-gui", line 32, in <module>
    import gtk
  File "/usr/lib64/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module>
    _init()
  File "/usr/lib64/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 52, in _init
    _gtk.init_check()
RuntimeError: could not open display
Comment 3 RHEL Program Management 2012-07-10 08:47:29 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 RHEL Program Management 2012-07-11 01:49:13 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 5 RHEL Program Management 2012-12-14 08:47:40 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 6 Bryan Kearney 2013-10-09 21:32:20 UTC 
I now see a a can not display error, which is resolved by logging out nad back in. Calling this fixed.
Comment 7 Sharath Dwaral 2013-10-11 18:21:23 UTC 
Version:
# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.29-1
subscription-manager: 1.10.2-1.el7
python-rhsm: 1.10.2-1.el7


Verification

=== Original hostname ===
# hostname
sharath-70server.usersys.redhat.com

=== Changing hostname ===
# hostname test2

=== Checking Hostname ===
# hostname
test2

=== Launching GUI ===
# subscription-manager-gui
X11 connection rejected because of wrong authentication.
Unable to open a display

=== Exiting ssh ===
# exit
logout

=== Logging back in ===
$ dtop-client70 
root.redhat.com's password: 
Last login: Fri Oct 11 11:24:08 2013 from dhcp129-238.rdu.redhat.com

=== Checking hostname ===
# hostname
test2

=== Launching GUI ===
# subscription-manager-gui

GUI launches successfully
This is an acceptable behavior

VERIFIED
Comment 8 Ludek Smid 2014-06-13 09:50:46 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.