Bug 1390197 - Typo in fusor-initial-setup
Summary: Typo in fusor-initial-setup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-installer
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 1.1
Assignee: Derek Whatley
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-31 13:28 UTC by Thom Carlin
Modified: 2017-02-28 01:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:40:38 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 Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description Thom Carlin 2016-10-31 13:28:41 UTC 
Description of problem:

Typo in fusor-initial-setup error message

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

fusor-1.1.1-1.el7sat

How reproducible:

100%

Steps to Reproduce:
1. fusor-initial-setup

Actual results:

Path '/etc/.fusor-initial-setup.done' exists
Exitting as it looks like we already ran.

Expected results:

Path '/etc/.fusor-initial-setup.done' exists
Exiting as it looks like we already ran.

Additional info:

/usr/bin/fusor-initial-setup, Line 19
Comment 2 Derek Whatley 2016-10-31 19:48:46 UTC 
Fixed in https://github.com/fusor/fusor-initial-setup/commit/2cdb7b2e47658df6876c200af1acb5fb3b9f8be4
Comment 3 John Matthews 2016-11-01 14:05:59 UTC 
Will be in compose of 11/1
Comment 4 Tasos Papaioannou 2016-11-02 18:20:59 UTC 
Verified on QCI-1.1-RHEL-7-20161101.t.0.
Comment 7 errata-xmlrpc 2017-02-28 01:40:38 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-2017:0335
Note You need to log in before you can comment on or make changes to this bug.