Bug 1328971

Summary:	Multiple invocations of Register Nodes leads to corruption of node display
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	Installation - RHELOSP	Assignee:	cchase
Status:	CLOSED ERRATA	QA Contact:	Thom Carlin <tcarlin>
Severity:	medium	Docs Contact:	Dan Macpherson <dmacpher>
Priority:	unspecified
Version:	1.0	CC:	bthurber, jmatthew
Target Milestone:	ga	Keywords:	Triaged
Target Release:	1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-13 16:28:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1342594

Description Thom Carlin 2016-04-20 18:41:22 UTC

Description of problem:

Erroneous duplication of Register Nodes leads to eventual node display corruption in web UI.

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

TP3 RC4

How reproducible:

100%

Steps to Reproduce:
1. Install QCI and TripleO ISOs
2. Log in each system to run launch-fusor*-installer
3. Deploy OpenStack
4. In Register Nodes, Register the same CSV file over and over

Actual results:

Corrupt display (see attachment)

Expected results:

Appropriate error handling

Additional info:

Although the reproducer is trivial, it may be indicative of an underlying problem.

Comment 3 Thom Carlin 2016-04-20 18:55:34 UTC

Created attachment 1149166 [details]
Checksum for sosreport

The checksum is: 6d94578075521763d2cfa7f678a57c11

Comment 5 Thom Carlin 2016-07-12 19:45:38 UTC

Verified in QCI-1.2-RHEL-7-20160711.t.1. Error message *properly* displayed:
There were errors encountered while trying to parse the CSV file.

Row 1, Column 5 "<<mac address>>" is not an available MAC address
Row 2, Column 5 "<<mac address>>" is not an available MAC address

Comment 11 errata-xmlrpc 2016-09-13 16:28:13 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-2016:1862