Bug 1387527 - Problem deploying metrics.Hawkular metrics pod running but in heapster pod logs show "Could not connect to https://hawkular-metrics:443/hawkular/metrics/status. Curl exit code: 7. Status Code 000"
Summary: Problem deploying metrics.Hawkular metrics pod running but in heapster pod lo...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Matt Wringe
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 07:53 UTC by Miheer Salunke
Modified: 2019-12-16 07:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 16:04:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Miheer Salunke 2016-10-21 07:53:24 UTC
Description of problem:

I have re-deployed all metrics pods but heapster can't start correctly and ends in a CrashLoopBackOff status.  The others hawkular pods seems to start correctly but in the heapster log I can see that the metrics service is unreachable with this error:

Could not connect to https://hawkular-metrics:443/hawkular/metrics/status. Curl exit code: 7. Status Code 000
'https://hawkular-metrics:443/hawkular/metrics/status' is not accessible [HTTP status code: 000. Curl exit code 7]. Retrying.

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

How reproducible:
On customer side

Steps to Reproduce:
1.Deploy metrics in 3.2
2.
3.

Actual results:
Metrics deployment not successful

Expected results:
Metrics deployment shall be successful

Additional info:

Comment 12 Matt Wringe 2016-10-27 16:04:22 UTC
I am closing this as not a bug as it appears the root cause is a mismatch where the docker containers which are running are not the ones meant for the configuration files.

The installation documentation for Metrics needs to be followed for this to function properly.


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