Bug 1700060

Summary:

kube-controller-manager target down due to incorrect port

Product:

OpenShift Container Platform

Reporter:

Seth Jennings <sjenning>

Component:

Monitoring

Assignee:

Frederic Branczyk <fbranczy>

Status:

CLOSED DUPLICATE

QA Contact:

Junqi Zhao <juzhao>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

4.1.0

CC:

anpicker, erooth, minden, mloibl, pkrupa, surbania

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2019-04-16 07:02:11 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
kcm-down.png	none

Description Seth Jennings 2019-04-15 17:33:44 UTC

Created attachment 1555288 [details]
kcm-down.png

See screenshot.

As of https://github.com/openshift/cluster-kube-controller-manager-operator/pull/207, metrics are served from the secure port 10257.

Result is a KubeControllerManagerDown and TargetDown alert.

We need to update the targets.

$ ogcv
NAME      VERSION                        AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.0.0-0.ci-2019-04-15-011801   True        False         3h45m   Cluster version is 4.0.0-0.ci-2019-04-15-011801

Comment 1 Seth Jennings 2019-04-15 17:41:54 UTC

I see there is already a PR for this:
https://github.com/openshift/cluster-monitoring-operator/pull/316

Comment 2 Seth Jennings 2019-04-15 18:19:21 UTC

This is also part of it
https://github.com/openshift/installer/pull/1576

Comment 3 Frederic Branczyk 2019-04-16 07:02:11 UTC

This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1698201. Also components own their monitoring configuration, so please open a bug against the respective components next time. Thank you! :)

*** This bug has been marked as a duplicate of bug 1698201 ***