Bug 1798315
| Summary: | gitCommit and gitVersion is invalid for openshift-console-operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Management Console | Assignee: | bpeterse |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | aos-bugs, bpeterse, jesusr, jfan, jhadvig, jokerman, pkrupa, yapei |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1798305 | Environment: | |
| Last Closed: | 2020-05-04 11:33:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Junqi Zhao
2020-02-05 05:54:00 UTC
*** Bug 1791003 has been marked as a duplicate of this bug. *** $ oc adm release info registry.svc.ci.openshift.org/ocp/release:4.4.0-0.nightly-2020-02-07-001901 --pullspecs | grep console
console quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:744f6c645fbb455b7f10ad209f49e8a77251f48f9b3dcec34ba01ccf66ad07f2
console-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:aa3942a361374b3addfd29ff58b450403271af0eb266664bee7913b052214a91
$ oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:aa3942a361374b3addfd29ff58b450403271af0eb266664bee7913b052214a91 | grep -i commit
Environment: SOURCE_GIT_COMMIT=59dd82da10e641899cd0c1038e641d3dc16d8c06
io.openshift.build.commit.id=59dd82da10e641899cd0c1038e641d3dc16d8c06
io.openshift.build.commit.url=https://github.com/openshift/console-operator/commit/59dd82da10e641899cd0c1038e641d3dc16d8c06
[yapei@New_Mac console-operator]$ git log 59dd82da10e641899cd0c1038e641d3dc16d8c06 | grep '#377'
Merge pull request #377 from jhadvig/bz1798315
When search in prometheus
count(kubernetes_build_info{job!~"kube-dns|coredns",gitVersion="v0.0.0-master+$Format:%h$"}) by (gitCommit, gitVersion,namespace)
It still returns
{gitCommit="$Format:%H$",gitVersion="v0.0.0-master+$Format:%h$",namespace="openshift-console-operator"} 1
{gitCommit="$Format:%H$",gitVersion="v0.0.0-master+$Format:%h$",namespace="openshift-service-catalog-controller-manager-operator"} 1
{gitCommit="$Format:%H$",gitVersion="v0.0.0-master+$Format:%h$",namespace="openshift-service-catalog-apiserver-operator"} 1
This is checked against 4.4.0-0.nightly-2020-02-07-001901
We expose `openshift_console_operator_build_info` metrics for the console-operator.
Tried to query `openshift_console_operator_build_info{namespace="openshift-console-operator"}"` but without any result.
Also tried to query the authentication operator with:
`openshift_cluster_authentication_operator_build_info{namespace="openshift-authentication-operator"}`
but without any result, which comes to question if you are using a valid query?
(In reply to Jakub Hadvig from comment #11) > We expose `openshift_console_operator_build_info` metrics for the > console-operator. > Tried to query > `openshift_console_operator_build_info{namespace="openshift-console- > operator"}"` but without any result. > > Also tried to query the authentication operator with: > `openshift_cluster_authentication_operator_build_info{namespace="openshift- > authentication-operator"}` > but without any result, which comes to question if you are using a valid > query? we don't need to check with "kubernetes_build_info{namespace="openshift-console-operator"}" now, according to the comment,`openshift_console_operator_build_info` metrics should be exposed for console-operator, but it is not, tracked in Bug 1806787 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |