Bug 1296553 - Failed node introspection link leads to Installation Progress page in RHELOSP deployment
Summary: Failed node introspection link leads to Installation Progress page in RHELOSP...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: TP3
: 1.0
Assignee: cchase
QA Contact: Landon LaSmith
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-14
TreeView+ depends on / blocked
 
Reported: 2016-01-07 14:12 UTC by Antonin Pagac
Modified: 2016-04-29 16:22 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Antonin Pagac 2016-01-07 14:12:58 UTC
Description of problem:
During step 2B Register Nodes, when node introspection fails, the error message is a link pointing to step 4B Installation Progress page, which is not correct, and also skips a number of steps. There is no useful option or information on the Installation Progress page and no action is taken.
We should probably point the user to the failing task rather than to the Installation Progress page.

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20151223.t.0-RHCI-x86_64-dvd1.iso
RHCIOOO-7-RHEL-7-20151208.t.0-RHCIOOO-x86_64-dvd1.iso

How reproducible:
Always

Steps to Reproduce:
1. Do a RHELOSP deployment, go to step 2B Register Nodes
2. Fail a node introspection. In my case it was timeout
3. Click on the red error text. It takes you to the Installation Progress page

Actual results:
Installation progress page is shown after clicking on node introspection error

Expected results:
Relevant failing task could be shown when clicking on error message after node introspection error

Additional info:

Comment 1 cchase 2016-03-31 21:04:57 UTC
https://github.com/fusor/fusor/pull/703

Comment 2 Landon LaSmith 2016-04-13 14:28:11 UTC
Install Version: TP3 RC3

Steps:
 1) Create deployment
 2) Detect valid undercloud
 3) Use manual entry to input an invalid MAC node
    - Valid PXE+SSH host with bad mac address 01:23:45:67:89:AB
    - Invalid IPMI host with bad mac address of 10:32:54:76:98:BA

Verified Results: Both nodes failed introspection and the error text for each node provided descriptive information and linked to the respective foreman task page.


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