Bug 875220

Summary:	Strange network behaviour after activation key/autosubscribe in preferences dialog
Product:	Red Hat Enterprise Linux 6	Reporter:	Adrian Likins <alikins>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WORKSFORME	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	awood, bgollahe, bkearney, jsefler, mreid, sforsber, skallesh
Target Milestone:	rc
Target Release:	6.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	817671	Environment:
Last Closed:	2012-12-11 18:24:41 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:	817671
Bug Blocks:	771481

Comment 1 Adrian Likins 2012-12-11 16:39:22 UTC

comment #6 is proving hard to reproduce, since it does happen when there is a dns failure for the cdn hostname. I've seen it in firstboot where networking wasn't quite up yet when we ran our module (since mitigated by some rhn-client-tools changes that make this scenario less likely by being stricter about when it decides it actually needs and has networking). 

The traceback does need better error handling here though, but given
the circumstance of it being a somewhat unrecoverable network error, I don't think that's a huge deal.

Comment 2 Matt Reid 2012-12-11 18:08:43 UTC

The only way I've hit this was in an early implementation of activation keys where we didn't utilize any of the information assigned to an activation key, and then you tried to auto-attach some new subscriptions. Now that activation keys work properly, and we don't allow empty activation keys to be used during registration, I think this will be very hard to run into.

Think this is safe to close Alex?

Comment 3 Alex Wood 2012-12-11 18:24:41 UTC

I think this is safe to close.