Bug 1155665 - rubygem-staypuft: Hosts don't get registered in staypuft and don't appear in the "discovered hosts" list.
Summary: rubygem-staypuft: Hosts don't get registered in staypuft and don't appear in ...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 5.0 (RHEL 7)
Hardware: x86_64
OS: Linux
Target Milestone: z2
: Installer
Assignee: Mike Burns
QA Contact: Alexander Chuzhoy
Depends On:
TreeView+ depends on / blocked
Reported: 2014-10-22 15:01 UTC by Alexander Chuzhoy
Modified: 2014-11-04 17:03 UTC (History)
7 users (show)

Fixed In Version: rhel-osp-installer-0.4.5-2.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-11-04 17:03:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1800 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Installer Bug Fix Advisory 2014-11-04 22:00:19 UTC

Description Alexander Chuzhoy 2014-10-22 15:01:50 UTC
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 Alexander Chuzhoy 2014-10-22 15:05:10 UTC
rubygem-staypuft: Hosts don't get registered in staypuft and don't appear in the "discovered hosts" list.


Steps to reproduce:
1. Install rhel-osp-installer.
2. pxeboot the machines to register in staypuft.

Occasionally bare metal and VMs don't get registered.
Looking at the console of the booting machines - the following message is shown:
Could not send facts to foreman

Expected result:
All the hosts should get registered and appear under the discoveered machines.

Comment 3 Alexander Chuzhoy 2014-10-22 15:08:38 UTC
In the VM setup I was able to register the VMs after switching from the rtl8139 driver to virtio.
With that said the vNIC used for PXE was already configured with virtio and rtl8139 driver was configured on other vNICs.

Comment 4 Alexander Chuzhoy 2014-10-22 15:15:07 UTC
While not being able to register in staypuft, the booted VMs can reach the staypuft machine by IP/hostname with no issues and can be reached from it.

Comment 6 Alexander Chuzhoy 2014-10-22 17:41:39 UTC
I hit the same issue on baremetal setup  with Dell PowerEdge R320 machines.

Message on the console, after "registering host with Foreman":

Could not send facts to Foreman: getaddrinfo: Name or service not known

Comment 10 Lukas Zapletal 2014-10-23 09:19:00 UTC
Alex, can you describe me full VM setup how to reproduce this bug? I tried almost all cases and it always boots fine for me. Please describe me your setup in full detail: NICs, booting NIC, drivers, networks (DHCP, network, netmask, NAT or isolated). Thanks.

Comment 11 Alexander Chuzhoy 2014-10-23 13:52:16 UTC
While my VMs had 3 vNICs - I didn't experince the issue.
Nic1 = virtio (PXE/management) - internal DHCP. isolated.
Nic2 = rtl8139 (tenant)  - there's a DHCP in the virtual network, but in staypuft I configure the network to use internal DB. Isolated.
Nic3 = rtl8139 (external) - uses DHCP, bridged outside
* No bondings.

After I added one more vNIC (doesn't matter if it's virtio or rtl8139) - started hitting the issue. After the issue appeared - I tried to change all drivers to virtio and then all to to rtl8139 - no luck. 

If I remove the 4th NIC and revert the changes - the issue goes away.

Comment 16 Mike Burns 2014-10-24 13:42:08 UTC
doc text not required, this was an internally found and fixed bz

Comment 18 Alexander Chuzhoy 2014-10-24 15:23:00 UTC

The reported issue doesn't reproduce in the same bare metal setup it reproduced earlier.

Comment 20 errata-xmlrpc 2014-11-04 17:03:47 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.


Note You need to log in before you can comment on or make changes to this bug.