Bug 1476576 - Hawkular does not allow access using management-admin token
Hawkular does not allow access using management-admin token
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization (Show other bugs)
5.8.0
Unspecified Unspecified
high Severity high
: GA
: 5.8.1
Assigned To: Yaacov Zamir
Einat Pacifici
container
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-30 08:22 EDT by Einat Pacifici
Modified: 2017-08-02 04:46 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-02 04:46:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management


Attachments (Terms of Use)
evm.log and screenshot (648.84 KB, application/x-gzip)
2017-07-30 08:22 EDT, Einat Pacifici
no flags Details

  None (edit)
Description Einat Pacifici 2017-07-30 08:22:54 EDT
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 04:46:25 EDT
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.

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