Bug 1614248 - [v2v] Usage of back button in the infrastructure mapping leads to losing clusters list
Summary: [v2v] Usage of back button in the infrastructure mapping leads to losing clus...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: GA
: cfme-future
Assignee: Brett Thurber
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 09:14 UTC by Mor
Modified: 2019-01-17 15:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-17 14:04:16 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (39.81 KB, image/png)
2018-08-09 09:14 UTC, Mor 		no flags Details
View All

Description Mor 2018-08-09 09:14:35 UTC 
Created attachment 1474614 [details]
screenshot

Description of problem:
When creating a new infrastructure mapping and using the back button to correct clusters mapping, this could lead to lost of data in the window.

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

How reproducible:
100%

Steps to Reproduce:
Create a new infrastructure mapping:
Step 1 - Put a name and click next.
Step 2 - Select source and target cluster(s), click add mapping and click next.
Step 3 - Click back.

Actual results:
Source clusters no longer appears in the window.

Expected results:
Should appear.

Additional info:
Comment 2 Brett Thurber 2018-08-15 14:27:55 UTC 
Checked in 5.9.4.2 and am unable to reproduce this issue.  

@Sudhir, can you guys test as well?
Comment 3 Sudhir Mallamprabhakara 2018-09-11 20:16:58 UTC 
KK - Can you test this??
Comment 4 Kedar Kulkarni 2018-09-12 15:02:35 UTC 
Sudhir I think its NOTABUG its how the feature works. If I have assigned a source cluster to some target cluster, then it won't be visible in Source clusters list any more and that is what described as a Bug in Comment 1. So unless I missed something its NOTABUG.
Comment 6 Kedar Kulkarni 2019-01-17 14:04:16 UTC 
I think this is NOT A BUG. Closing.
Note You need to log in before you can comment on or make changes to this bug.