Closed joelsmith closed 4 years ago
We saw the liveness probe failing on the starter-ca-central-1 cluster.
Liveness probe for "hawkular-metrics-sf0c9_openshift-infra(8110e54a-b4d1-11e7-982f-02ac
3a1f9d61):hawkular-metrics" failed (failure): Failed to access the status endpoint : <urlopen error [Errno 111] Connection refused>.
Traceback (most recent call last):
File "/opt/hawkular/scripts/hawkular-metrics-liveness.py", line 48, in <module>
if int(uptime) < int(timeout):
ValueError: invalid literal for int() with base 10: ''
@mwringe or @jsanda PTAL cc @eparis
File "/opt/hawkular/scripts/hawkular-metrics-liveness.py", line 48 How do we fix this issue? I am currently facing this problem in one of the cluster
@jsanda Can you take a look?
/retest
/retest
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closed this PR.