Bug 1911211
| Summary: | Should show the cert-recovery-controller version correctly | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhou ying <yinzhou> |
| Component: | kube-controller-manager | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | aos-bugs, jdelft, jokerman, lmeyer, maszulik, mfojtik, wking |
| Target Milestone: | --- | Keywords: | Reopened, UpcomingSprint |
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 22:35:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1917980 | ||
|
Description
zhou ying
2020-12-28 07:40:37 UTC
These numbers are not injected properly in our CI builds. This is only happening during normal build process performed by ART. I checked with the 4.6 GA version , also could hit the same error , so will re-open this to Release team.
[root@dhcp-140-138 roottest]# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.9 True False 74m Cluster version is 4.6.9
[root@dhcp-140-138 roottest]# oc logs -f po/kube-controller-manager-ip-xxxxx.compute.internal -c kube-controller-manager-recovery-controller
+ timeout 3m /bin/bash -exuo pipefail -c 'while [ -n "$(ss -Htanop \( sport = 9443 \))" ]; do sleep 1; done'
++ ss -Htanop '(' sport = 9443 ')'
+ '[' -n '' ']'
+ exec cluster-kube-controller-manager-operator cert-recovery-controller --kubeconfig=/etc/kubernetes/static-pod-resources/configmaps/kube-controller-cert-syncer-kubeconfig/kubeconfig --namespace=openshift-kube-controller-manager --listen=0.0.0.0:9443 -v=2
W0106 10:41:36.418992 1 cmd.go:204] Using insecure, self-signed certificates
I0106 10:41:36.419202 1 crypto.go:601] Generating new CA for cert-recovery-controller-signer@1609929696 cert, and key in /tmp/serving-cert-535215117/serving-signer.crt, /tmp/serving-cert-535215117/serving-signer.key
I0106 10:41:36.992105 1 observer_polling.go:159] Starting file observer
I0106 10:41:37.039978 1 builder.go:238] cert-recovery-controller version v0.0.0-master+$Format:%h$-$Format:%H$
Checked with latest payload : [root@dhcp-140-138 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-01-21-215614 True False 14m Cluster version is 4.7.0-0.nightly-2021-01-21-215614 [root@dhcp-140-138 ~]# oc logs -f po/kube-controller-manager-ip-10-0-137-3.us-east-2.compute.internal -c kube-controller-manager-recovery-controller .... I0122 05:28:55.250127 1 builder.go:238] cert-recovery-controller version v0.0.0-alpha.0-891-gb2a87786-b2a877865f9b4dc7bb7cf30f6cc9f072f64fd205 Jan we probably should update the env vars being set in Makefile. Theoretically these should be the same which we set for the operator version. the issue has fixed with latest 4.8 payload:
[root@dhcp-140-138 roottest]# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.8.0-0.nightly-2021-02-09-221546 True False 40m Cluster version is 4.8.0-0.nightly-2021-02-09-221546
[root@dhcp-140-138 roottest]# oc logs -f po/kube-controller-manager-ip-10-0-149-168.us-east-2.compute.internal -c kube-controller-manager-recovery-controller
+ timeout 3m /bin/bash -exuo pipefail -c 'while [ -n "$(ss -Htanop \( sport = 9443 \))" ]; do sleep 1; done'
++ ss -Htanop '(' sport = 9443 ')'
+ '[' -n '' ']'
+ exec cluster-kube-controller-manager-operator cert-recovery-controller --kubeconfig=/etc/kubernetes/static-pod-resources/configmaps/kube-controller-cert-syncer-kubeconfig/kubeconfig --namespace=openshift-kube-controller-manager --listen=0.0.0.0:9443 -v=2
W0210 02:12:13.828375 1 cmd.go:204] Using insecure, self-signed certificates
I0210 02:12:13.828585 1 crypto.go:601] Generating new CA for cert-recovery-controller-signer@1612923133 cert, and key in /tmp/serving-cert-963210161/serving-signer.crt, /tmp/serving-cert-963210161/serving-signer.key
I0210 02:12:14.202980 1 observer_polling.go:159] Starting file observer
I0210 02:12:14.225806 1 builder.go:238] cert-recovery-controller version 4.8.0-202102091857.p0-cb87168-cb87168b232951b8b8ead7e75e857fdc92c33597
...
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438 |