Bug 1476576

Summary: Hawkular does not allow access using management-admin token
Product: Red Hat CloudForms Management Engine Reporter: Einat Pacifici <epacific>
Component: C&U Capacity and UtilizationAssignee: Yaacov Zamir <yzamir>
Status: CLOSED NOTABUG QA Contact: Einat Pacifici <epacific>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: epacific, fsimonce, jhardy, obarenbo
Target Milestone: GA   
Target Release: 5.8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: container
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-02 08:46:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evm.log and screenshot none

Description Einat Pacifici 2017-07-30 12:22:54 UTC
Created attachment 1306582 [details]
evm.log and screenshot

Description of problem:
When attempting to add a provider and validate the hawkular endpoint. CFME returns error: 

"Credential validation was not successful: <html><head><title>Error</title></head><body>403 - Forbidden</body></html>"

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

How reproducible:
Sometimes: Reproduction depends on the provider/hawkular endpoint setup

Steps to Reproduce:
1.Add Openshift provider to CFME by adding default endpoint - validate (SSL without validation) and pass successfully
2.Try to add hawkular endpoint (SSL without validation) and click Validate


Actual results:
CFME Shows error: Credential Validation was not succssful

Expected results:
Hawkular endpoint validation should be successful if all relevant information entered was valid.

Additional info:
evm.log and screenshot attached.

Comment 3 Einat Pacifici 2017-08-02 08:46:25 UTC
After further investigation, I have decided to close this BZ. It does not reproduce on a clean install and we have not been able to consistently reproduce this issue.