Bug 1439916 - Duplicate instances shown in Automate Explorer upon instance creation
Summary: Duplicate instances shown in Automate Explorer upon instance creation
Keywords:
Status: CLOSED DUPLICATE of bug 1544844
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: cfme-future
Assignee: Zita Nemeckova
QA Contact: Dave Johnson
URL:
Whiteboard: automate:ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-06 20:24 UTC by Jeffrey Cutter
Modified: 2018-03-19 14:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-19 13:17:44 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
duplicate instance after creation (9.39 KB, image/png)
2017-04-06 20:24 UTC, Jeffrey Cutter
no flags Details

Description Jeffrey Cutter 2017-04-06 20:24:13 UTC
Created attachment 1269481 [details]
duplicate instance after creation

Description of problem:

Sometimes when creating a new instance in Automate Explorer duplicate instances are displayed in the frame on the left.  See attached pic.

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

5.7.1.3.20170221135006_818f133

How reproducible:

Intermittent.  I have seen it in two different completely separate environments now.  I can't seem to reproduce it myself however.  It seems to happen somewhat regularly, but not constantly.

Steps to Reproduce:
1.  Add an instance and maybe it happens, sorry I can't figure out any further rhyme or reason at this time.
2.
3.

Actual results:

Get duplicate instances showing on the left until you refresh the screen.

Expected results:

Get only one instance on the left.

Additional info:

See pic.

Comment 2 Jeffrey Cutter 2017-04-06 20:32:46 UTC
I should add that when this occurs, you have to refresh the page to be able to make additional changes to the instance.

Comment 3 Dustin Scott 2017-07-03 13:52:55 UTC
+1 for this bug.

I would agree that this bug should be listed as a 'high' priority.  I have seen customers actually try and delete some of the duplicate instances (before refresh), and instead they delete the valid instance and not the displayed duplicate.  Very, very dangerous.  The workaround is, of course, to refresh the page before further continuing.


Also, I have found that this is 100% reproducible when attempting to copy an instance, into the same domain, and same namespace with a new name.

This is also reproducible in 5.7.2.1.

Comment 4 Zita Nemeckova 2018-03-19 13:17:44 UTC

*** This bug has been marked as a duplicate of bug 1544844 ***


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