Bug 1477604

Summary:	Error reading network interface information: <class 'ValueError'> during registration of fc26
Product:	[Community] Spacewalk	Reporter:	Tomas Lestach <tlestach>
Component:	Clients	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.6	CC:	eherget
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-04 08:53:12 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:
Bug Blocks:	1310034, 1484117

Description Tomas Lestach 2017-08-02 12:50:29 UTC

Description of problem:
During registration of a fc26 client I'm getting:
Error reading network interface information: <class 'ValueError'>

Version-Release number of selected component (if applicable):
rhn-setup-2.6.8-3.fc26.noarch (be aware this is rhn-setup from Fc26)

How reproducible:
always

Steps to Reproduce & Actual results:

# grep ID- /etc/sysconfig/rhn/systemid
<value><string>ID-1000169709</string></value>
# rhnreg_ks --serverUrl=http://<fqdn>/XMLRPC --activationkey=<activation-key> --force
Error reading network interface information: <class 'ValueError'>
# grep ID- /etc/sysconfig/rhn/systemid<value><string>ID-1000169710</string></value>

The registration got through. This BZ is about the error message.

Expected results:
No error messages during registration.

Comment 2 Tomáš Kašpárek 2017-08-04 08:53:12 UTC

fixed by commits in bz#147714 closing

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

Comment 3 Tomas Lestach 2017-08-14 13:29:39 UTC

I see no commits in bz#147714.

Comment 4 Tomáš Kašpárek 2017-08-15 06:14:14 UTC

(In reply to Tomas Lestach from comment #3)
> I see no commits in bz#147714.

bz#147714 was a typo, if you look at bug 1477149 which this one is duplicate of, you'll see commits

Comment 5 Eric Herget 2017-09-28 18:07:35 UTC

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.