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 669449 - Error dialog upon registering
Summary: Error dialog upon registering
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Pradeep Kilambi
QA Contact: J.C. Molet
URL:
Whiteboard:
Depends On:
Blocks: Entitlement-Beta
TreeView+ depends on / blocked
 
Reported: 2011-01-13 17:47 UTC by J.C. Molet
Modified: 2011-01-13 20:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 20:23:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
register error (443.55 KB, image/png)
2011-01-13 17:47 UTC, J.C. Molet 		no flags Details
View All

Description J.C. Molet 2011-01-13 17:47:21 UTC 
Created attachment 473379 [details]
register error

Description of problem:
An error dialog pops up upon every register.  The system actually does register though.

Version-Release number of selected component (if applicable):
subscription-manager-0.93.11-1.git.2.129c8f2.el6.x86_64
subscription-manager-firstboot-0.93.11-1.git.2.129c8f2.el6.x86_64
subscription-manager-gnome-0.93.11-1.git.2.129c8f2.el6.x86_64

Steps to Reproduce:
1. Install rhsm and it's deps
2. Open the gui
3. Register
  
Actual results:
It registers, but throws an error message.

Expected results:
It registers happily.

Additional info:
see attached screenshot.

rhsm.log:

2011-01-13 12:19:56,622 [ERROR] handle_gui_exception() @utils.py:40 - 'canActivate'
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/managergui.py", line 515, in register
    self.emit_consumer_signal()
  File "/usr/share/rhsm/gui/managergui.py", line 523, in emit_consumer_signal
    method()
  File "/usr/share/rhsm/gui/managergui.py", line 272, in registration_changed
    self.refresh()
  File "/usr/share/rhsm/gui/managergui.py", line 288, in refresh
    self._show_buttons()
  File "/usr/share/rhsm/gui/managergui.py", line 314, in _show_buttons
    can_activate = consumer['canActivate']
KeyError: 'canActivate'
Comment 1 Devan Goodwin 2011-01-13 20:23:15 UTC 
I think this is just an issue with the way you're building/testing subscription-manager. It looks like you're doing subscription-manager builds from git master, but hitting a Candlepin server which is tracking the BETA branch. These are now out of sync and won't work.

Both Candlepin and subscription-manager have such a BETA branch, and using the two together should work ok. 

Need to either (a) build subscription-manager from BETA branch in git, or (b) test against a Candlepin server running the latest in candlepin.git master.

(a) is probably what you want in this case. Closing for now, feel free to re-open or let me know if there's any issues.
Note You need to log in before you can comment on or make changes to this bug.