Bug 1298155 - Warnings displayed when re-running fusor-undercloud-installer
Summary: Warnings displayed when re-running fusor-undercloud-installer
Keywords:
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-13 11:16 UTC by Antonin Pagac
Modified: 2016-09-23 18:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1278866 0 unspecified CLOSED On rerun of launch-fusor-undercloud-installer: too many arguments 2021-02-22 00:41:40 UTC

Internal Links: 1278866

Description Antonin Pagac 2016-01-13 11:16:35 UTC 
Description of problem:
Upon reruning the fusor-undercloud-installer, it outputs these errors/warnings:

"useradd: user 'stack' already exists
mkdir: cannot create directory ‘/tmp/repodata’: File exists"

I don't think it is necessary to display this to an user upon re-running the installer, we probably should anticipate and hide those messages.

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20160107.t.1-RHCI-x86_64-dvd1.iso
RHCIOOO-7-RHEL-7-20160112.t.1-RHCIOOO-x86_64-dvd1.iso

How reproducible:
Always

Steps to Reproduce:
1. Run fusor-undercloud-installer, wait until it ends
2. Run fusor-undercloud-installer again
3.

Actual results:
Warnings/errors displayed upon re-run

Expected results:
No errors should be displayed if the installer can continue and finish

Additional info:
Comment 1 Antonin Pagac 2016-01-13 13:27:52 UTC 
This appears when re-run after a failed run of fusor-undercloud-installer. The installer did not get to removing the /tmp/repodata.
Note You need to log in before you can comment on or make changes to this bug.