Bug 1288032 - provider name deleted after selecting type when adding a new provider from list of previous names
provider name deleted after selecting type when adding a new provider from li...
Status: NEW
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
5.5.0
x86_64 Linux
low Severity low
: GA
: cfme-future
Assigned To: Dan Clarizio
Dafna Ron
provider:add
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-03 05:53 EST by Dafna Ron
Modified: 2016-10-11 12:20 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
logs (180.80 KB, application/x-gzip)
2015-12-03 05:53 EST, Dafna Ron
no flags Details

  None (edit)
Description Dafna Ron 2015-12-03 05:53:31 EST
Created attachment 1101763 [details]
logs

Description of problem:

log in to cfme -> Navigate to containers-> providers -> Add New Containers Provider 
Add name (select from the ui's suggestion of past names) -> select openshift Atomic from the scroll-> name disappears

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

cfme-5.5.0.13-1.el7cf.x86_64

How reproducible:

100%

Steps to Reproduce:
1. log in to cfme -> Navigate to containers-> providers -> Add New Containers Provider 
2. Add name (select from the ui's suggestion of past names) -> select openshift Atomic from the scroll-> name disappears

3.

Actual results:

name disappears

Expected results:

Name should be consistent

Additional info: logs
Comment 1 Federico Simoncelli 2015-12-03 07:33:10 EST
This happens when the connection with the CFME UI is extremely slow and there's a race between the name update, e.g.:

  /ems_infra/form_field_changed/new?name=test

and the ems type update, e.g.:

  /ems_infra/form_field_changed/new?server_emstype=openstack_infra


This is not specific to containers it happens for every type of ems.

Reproducibility may be high on slow connections and if the user is too quick in selecting the ems type (not 100%).

Removing container from the whiteboard and Dan I'll leave this assigned to you.

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