Bug 1130234 - Rubygem-Staypuft: The discovered hosts appear with IP addresses from different subnets.
Summary: Rubygem-Staypuft: The discovered hosts appear with IP addresses from differe...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: unspecified
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-14 15:15 UTC by Alexander Chuzhoy
Modified: 2016-09-29 13:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 13:26:46 UTC


Attachments (Terms of Use)

Description Alexander Chuzhoy 2014-08-14 15:15:34 UTC
Rubygem-Staypuft:  The discovered hosts appear with IP addresses from different subnets.

Environment:
rhel-osp-installer-0.1.10-2.el6ost.noarch
openstack-foreman-installer-2.0.20-1.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-puppet-modules-2014.1-20.el6ost.noarch

Steps to reproduce:
1. Prepare an environment (hosts have NICs in different subnets: PXE/mgmt, tenant, external)
2. run rhel-osp-installer.
3. create any type of deployment and try to assign hosts.

Result:
The hosts will appear with IP addresses from different NICs (tenant,PXE,external), so there's no consistency. This doesn't fail the deployment, but I report it anyway.

Expected results:
I'd expect all the hosts to report their PXE/mgmt IP address - for consistency.

Comment 3 Jaromir Coufal 2016-09-29 13:26:46 UTC
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open.

For new deployments, please, use RHOSP director (starting with version 7).

-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform

[0] https://access.redhat.com/support/policy/updates/openstack/platform


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