Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1367158 - An unknown error has occurred
Summary: An unknown error has occurred
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: ISO Installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-15 17:45 UTC by Thom Carlin
Modified: 2016-08-15 18:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-15 18:19:00 UTC


Attachments (Terms of Use)

Description Thom Carlin 2016-08-15 17:45:20 UTC
Description of problem:

Installing ISO resulted in "An unknown error has occurred" in Anaconda.

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

QCI-1.0-RHEL-7-20160812.t.1

How reproducible:

Uncertain

Steps to Reproduce:
1. Install using specified ISO
2. Wait (no entry)

Actual results:

An unknown error has occurred

Expected results:

No errors
Successful install

Additional info:

ISO did checksum correctly (both internally and externally).
Screen contents were lost before I was able to capture details.

Attempting re-install

Comment 1 John Matthews 2016-08-15 17:54:58 UTC
I installed QCI-1.0-RHEL-7-20160815.t.0-QCI-x86_64-dvd1.iso and did not see this issue.

I also installed the 8/12 ISO and did not see this either.

Comment 2 Thom Carlin 2016-08-15 18:03:27 UTC
Re-testing with QCI-1.0-RHEL-7-20160815.t.0-QCI-x86_64-dvd1.iso

Comment 3 Thom Carlin 2016-08-15 18:19:00 UTC
Did not reoccur on same hardware with the later compose.  CLOSING as WORKSFORME but will reopen if it reoccurs (with more information :-))


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