Bug 1368145 - Document that DHCP range is split for discovered and managed hosts
Summary: Document that DHCP range is split for discovered and managed hosts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: doc-Installation_Guide
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 1.0
Assignee: Julie
QA Contact: bmorriso
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-18 14:18 UTC by Jason Montleon
Modified: 2016-09-13 16:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 16:37:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1361332 0 unspecified CLOSED Hypervisor host fails to convert to managed host during RHEV deployment 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2016:1862 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.0 2016-09-13 20:18:48 UTC

Internal Links: 1361332

Description Jason Montleon 2016-08-18 14:18:23 UTC 
Description of problem:
We need to document that the IP address range specified during install is split between discovered hosts and managed hosts. Discovered hosts are converted to managed hosts during provisioning. This means you effectively need twice as many IP addresses available as hosts you intend to provision.
Comment 4 bmorriso 2016-09-08 17:41:19 UTC 
Verified in version 1.0 of the documentation.
Comment 6 errata-xmlrpc 2016-09-13 16:37:05 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/RHEA-2016:1862
Note You need to log in before you can comment on or make changes to this bug.