Bug 1344449

Summary: Reregistering a client after upgrade fails 'Validation failed: Interfaces host must have one primary interface'
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: UpgradesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, cduryee, sghai, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/15357
Whiteboard:
Fixed In Version: rubygem-katello-3.0.0.48-1,katello-installer-base-3.0.0.47-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:30:17 UTC Type: ---
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: 1335807    

Description Justin Sherrill 2016-06-09 17:38:37 UTC
After upgrading to 2.4, if you try to re-register an existing system you get an error:

<pre>
[root@client ~]# subscription-manager register --force
The system with UUID 2f982f65-42d8-468f-ab32-78ade30ec777 has been unregistered
Registering to: centos7-2-4.example.com:443/rhsm
Username: admin
Password: 
Validation failed: Interfaces host must have one primary interface
</pre>

Comment 1 Justin Sherrill 2016-06-09 17:38:38 UTC
Created from redmine issue http://projects.theforeman.org/issues/15357

Comment 2 Justin Sherrill 2016-06-09 17:38:41 UTC
Upstream bug assigned to jsherril

Comment 4 Bryan Kearney 2016-06-13 14:16:18 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/15357 has been closed

Comment 5 Chris Duryee 2016-06-16 19:33:09 UTC
This failed for me with katello tfm-rubygem-katello-3.0.0.49-1.el6sat.noarch. However, if I run the "katello:upgrades:3.0:update_subscription_facet_backend_data" rake task by hand, I'm then able to force register OK.

Comment 7 Brad Buckingham 2016-06-17 14:18:09 UTC
Moving this BZ back to POST as it also needs redmine issue 15351 to work downstream.

Comment 8 Sachin Ghai 2016-07-05 11:28:45 UTC
Verified with sat62 GA snap18.2

I can re-register the existing client after upgrade without any issue.

[root@mac001a4a3ea60f ~]# yum repolist
Loaded plugins: product-id, security, subscription-manager
Default_Organization_RHEL6_RHEL67_x86_64                                                                                       | 2.5 kB     00:00     
repo id                                                                              repo name                                                  status
Default_Organization_RHEL6_RHEL67_x86_64                                             RHEL67_x86_64                                              3,819
repolist: 3,819
[root@mac001a4a3ea60f ~]# subscription-manager register --org Default_Organization --activationkey ak_rhel7 --force
The system with UUID ef82a71b-a2fe-419f-9cd7-d26ec2f8b5c9 has been unregistered
The system has been registered with ID: edcfec6f-b027-4312-8ba9-d8d0dcaa431c 

Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

[root@mac001a4a3ea60f ~]# subscription-manager register --org Default_Organization --activationkey ak_rhel7 --force
The system with UUID edcfec6f-b027-4312-8ba9-d8d0dcaa431c has been unregistered
The system has been registered with ID: 29632baf-ef2f-49d2-9904-ba7677cea351 

Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

[root@mac001a4a3ea60f ~]# 


for issue reported in comment5 related to "update_subscription_facet_backend_data" another issue is filed.

https://bugzilla.redhat.com/show_bug.cgi?id=1351483

Comment 9 Bryan Kearney 2016-07-27 11:30:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501