Bug 1378900 - Deployment: empty/cut Create Containers Provider dialogue after failure to install
Summary: Deployment: empty/cut Create Containers Provider dialogue after failure to in...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Barak
QA Contact: Einat Pacifici
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 13:21 UTC by Dafna Ron
Modified: 2018-04-17 08:20 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-26 13:56:28 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:


Attachments (Terms of Use)
screenshot and log (4.43 MB, application/x-gzip)
2016-09-23 13:21 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2016-09-23 13:21:51 UTC
Created attachment 1204155 [details]
screenshot and log

Description of problem:

After I failed installing I opened another Create Containers Provider dialogue and the dialogue opened was cut/empty

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

using upstream master/origin hash b2414903aa11
alon's updates merged

How reproducible:

100%

Steps to Reproduce:
1. create a failure in installation (wrong key)
2. open a new Create Containers Provider dialogue
3.

Actual results:

the dialogue opens cut/empty, without option to add details. 

Expected results:

dialogue should be complete and ready for use

Additional info: screenshot and logs

Comment 1 Dave Johnson 2017-07-14 03:49:43 UTC
Please assess the importance of this issue and update the priority accordingly.  Somewhere it was missed in the bug triage process.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.


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