Bug 1337294 - Screenshot showing wrong values is chapter 2, section 8-i
Summary: Screenshot showing wrong values is chapter 2, section 8-i
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: doc-Installation_Guide
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Julie
QA Contact: Thom Carlin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-18 18:00 UTC by Jean-Francois Saucier
Modified: 2019-10-10 12:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-06 00:54:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1337286 0 unspecified CLOSED Setting different values for Hostname and Foreman URL result in error 2021-02-22 00:41:40 UTC

Description Jean-Francois Saucier 2016-05-18 18:00:25 UTC 
Description of problem:

The screenshot in chapter 2, section 8-i that show the final state of the fusor-installer before launching the installation is not correct. The screenshot show different values for the "Hostname" and "Foreman URL" fields. 

Currently, having different values give an error at the end of installation and break PXE booting (see attached bugzilla entry).

The screenshot should be changed for one showing the same value for both fields.
Comment 3 Thom Carlin 2016-06-02 17:24:57 UTC 
Failed QA, screenshot unchanged.
Comment 4 Julie 2016-06-03 02:01:49 UTC 
Rebuilt and checked again. The changes are in. Please have a look again.
Comment 5 Thom Carlin 2016-06-03 10:23:26 UTC 
Verified after refreshing browser cache for link.
Comment 6 Julie 2016-06-06 00:54:43 UTC 
Documentation Link: 
https://access.redhat.com/documentation/en/quickstart-cloud-installer/1.0/quickstart-cloud-installer-guide/chapter-2-installing-the-quickstart-cloud-installer
Note You need to log in before you can comment on or make changes to this bug.