Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1511530

Summary: Credential validation seems to be successful even though API port is missing
Product: Red Hat CloudForms Management Engine Reporter: Jan Zmeskal <jzmeskal>
Component: ProvidersAssignee: Martin Perina <mperina>
Status: NEW --- QA Contact: Angelina Nikiforova <anikifor>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.9.0CC: gblomqui, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: RHEVM
Attachments:
Description Flags
Credential validation successful without API port none

Description Jan Zmeskal 2017-11-09 14:06:45 UTC
Created attachment 1349944 [details]
Credential validation successful without API port

Description of problem:
When you re-validate provider's credentials and save them while API port is missing, you get info message about being successful. However, authentication is not actually successful without API port and the is reflected in quadicon. This seems inconsistent and is somewhat confusing. 

Version-Release number of selected component (if applicable):
CFME 5.9.0.4
RHV 4.1.7.4

Steps to Reproduce:
1. Have a RHV provider with wrong authentication status (red X in quadicon). Edit its configuration.
2. Make sure API port is blank.
3. Input correct credentials.
4. Click validate. You will get "Credential validation successful" message.
5. Save your changes. They are successfully changed since API port is not required.
6. Authentication status on quadicon is still red X, which is correct.

Actual results:
From user's point of view, there is an inconsistency between success message at credential validation and successful save of configuration and resulting unsuccessful authentication.

Expected results:
These two should be in line.

Comment 2 Dave Johnson 2017-11-09 14:46:54 UTC
Fairly certain this is working as designed, each provider has a default port that we fall back to when port is not given.  Ideally the UI should probably render this if its not.