Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1145801

Summary: Rubygem-Staypuft: One of the discovered machines doesn't show its NICs, hence it's impossible to assign the NICs of the machine to the respective network post deployment creation.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rubygem-staypuftAssignee: Mike Burns <mburns>
Status: CLOSED NOTABUG QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: lzap, mburns, sclewis, yeylon
Target Milestone: z1   
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 18:12:35 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:
Attachments:
Description Flags
production.log from the staypuft host. none

Description Alexander Chuzhoy 2014-09-23 19:21:06 UTC 
Rubygem-Staypuft:  One of the discovered machines doesn't show its NICs, hence it's impossible to assign the NICs of the machine to the respective network post deployment creation.

Environment:
rhel-osp-installer-0.3.6-1.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-foreman-installer-2.0.26-1.el6ost.noarch
openstack-puppet-modules-2014.1-21.8.el6ost.noarch


Steps to reproduce:
1. run rhel-osp-installer.
2. Create a deployment of any type.
3. Assign hosts to roles.
4. Go to the Hosts tab of the deployment and click on the "Assigned" link.

Result:
The NICs column is empty for one node. This makes assigning NICs to appropriate network impossible when selecting this host and clicking on 'Configure Networks'.

Expected result:
The NICs of all hosts should be visible in the NICs column of assigned hosts.
Comment 1 Alexander Chuzhoy 2014-09-23 19:23:00 UTC 
Created attachment 940582 [details]
production.log from the staypuft host.
Comment 2 Alexander Chuzhoy 2014-09-23 20:02:16 UTC 
Reproduced on another installation with the same version of environment:

The error I get on the console in both cases: 

response from Foreman 500: {"error" : {"message": "Validation failed: MAC address has already been taken, IP address has already been taken"} }
Comment 3 Lukas Zapletal 2014-09-24 08:16:49 UTC 
Hey,

check if this patch is already in your codebase:

commit d455f32cde8fa60e41474bbaab0b8af1d7aded50
Refs: 0.1-3210-gd455f32
Author:     Marek Hulan <mhulan>
AuthorDate: Mon Jun 30 17:56:04 2014 +0200
Commit:     Greg Sutcliffe <gsutclif>
CommitDate: Wed Sep 3 16:24:23 2014 +0100

Fixes #6444 - add support for virtual NICs

Please attach the facts just to confirm nothing is wrong with the discovery image. But I think this is Foreman related rather than bug in the discovery image.
Comment 4 Mike Burns 2014-09-24 13:41:52 UTC 
(In reply to Lukas Zapletal from comment #3)
> Hey,
> 
> check if this patch is already in your codebase:
> 
> commit d455f32cde8fa60e41474bbaab0b8af1d7aded50
> Refs: 0.1-3210-gd455f32
> Author:     Marek Hulan <mhulan>
> AuthorDate: Mon Jun 30 17:56:04 2014 +0200
> Commit:     Greg Sutcliffe <gsutclif>
> CommitDate: Wed Sep 3 16:24:23 2014 +0100
> 
> Fixes #6444 - add support for virtual NICs
> 
> Please attach the facts just to confirm nothing is wrong with the discovery
> image. But I think this is Foreman related rather than bug in the discovery
> image.

Yes, this patch is backported in our build.
Comment 5 Mike Burns 2014-09-24 18:12:35 UTC 
This appears to have been narrowed down to a conflicting mac address/ip address between 2 hosts so an environmental issue rather than a bug.