Bug 1383192 - Last selected Automate name space no longer exist displayed after importing datastore classes
Summary: Last selected Automate name space no longer exist displayed after importing d...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: eclarizi
QA Contact: Dave Johnson
URL:
Whiteboard: ui:automate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 07:03 UTC by Aziza Karol
Modified: 2018-10-02 14:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
snapshot (84.91 KB, image/png)
2016-10-10 07:03 UTC, Aziza Karol 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Aziza Karol 2016-10-10 07:03:07 UTC 
Created attachment 1208737 [details]
snapshot

Description of problem:


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

How reproducible:
100%

Steps to Reproduce:
1.create a automate->explorer and add new domain
2.Then Navigate to Automate->import/export.
3.choose file to upload, and import the datastore classes to the above created domain.
4.once the commit is successful,click on back button and then navigate to Automate explorer page

Actual results:
Last selected Automate name space no longer exist is displayed in UI.see attached screenshot

Expected results:
This message should not be displayed.

Additional info:
Comment 2 Josh Carter 2018-10-02 14:33:16 UTC 
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!
Comment 3 Josh Carter 2018-10-02 14:34:00 UTC 
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!
Comment 4 Josh Carter 2018-10-02 14:35:27 UTC 
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

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