Bug 1446887 - Incorrect message when attempting to add a Container Provider with incorrect Endpoint's port
Summary: Incorrect message when attempting to add a Container Provider with incorrect ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-30 09:08 UTC by Pavel Zagalsky
Modified: 2017-04-30 09:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-30 09:15:22 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Zagalsky 2017-04-30 09:08:09 UTC
Description of problem:
When attempting to add a Containers Provider with an incorrect port the 
app will give an incorrect message

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

How reproducible:
Every time

Steps to Reproduce:
1. Go to Compute --> Containers --> Providers
2. Attempt to add a Container Provider with SSL as the Security Protocol and intentionally incorrect SSL Port ie 13000
3.

Actual results:
1. There's an incorrect message when attempting to validate the provider
" Credential validation was not successful: nested asn1 error "


Expected results:
When a user attempts to add a Provider with an incorrect port he should receieve a better error message:
" Credential validation was not successful: incorrect port provided "
Or something like that

Comment 2 Pavel Zagalsky 2017-04-30 09:15:22 UTC
Eh ignore.
It's working fine


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