Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Created attachment 1000539 [details]
production.log

Description of problem:
subscription-manager unregister throws traceback in production.log

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150303.0

How reproducible:
Always

Steps to Reproduce:
1.Install sat6. Import a manifest, sync, publish, promote. Create activation keys.
2.Register and subscribe a content host
# subscription-manager register --org="Default_Organization" --activationkey="ak4"
3.Unregister the content host
# subscription-manager unregister

Actual results:
traceback in  /var/log/foreman/production.log errors (see screenshot)

Expected results:
No errors

Additional info:

Couple of clarifying questions:

1) Was this a regular system you registered? Not a hypervisor?
2) Can you describe your activation key and what was configured on it?
3) Are you able to reproduce this on a clean system where you have only gone through the steps you mentioned?

(In reply to Eric Helms from comment #4)
> 1) Was this a regular system you registered? Not a hypervisor?
This was a regular system

> 2) Can you describe your activation key and what was configured on it?
A general activation key with employee subscriptions attached.

> 3) Are you able to reproduce this on a clean system where you have only gone
> through the steps you mentioned?
Yes

*** This bug has been marked as a duplicate of bug 1208100 ***