Bug 2091730 - MCO e2e tests are failing with "No token found in openshift-monitoring secrets"
Summary: MCO e2e tests are failing with "No token found in openshift-monitoring secrets"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Yu Qi Zhang
QA Contact: Rio Liu
URL:
Whiteboard:
: 2092124 (view as bug list)
Depends On:
Blocks: 2092124
TreeView+ depends on / blocked
 
Reported: 2022-05-30 21:57 UTC by Yu Qi Zhang
Modified: 2022-08-10 11:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2092124 (view as bug list)
Environment:
Last Closed: 2022-08-10 11:15:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 3172 0 None open Bug 2091730: create openshift-monitoring token in e2e 2022-05-31 22:10:50 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:15:34 UTC

Description Yu Qi Zhang 2022-05-30 21:57:29 UTC
Around May 26 the MCO e2e-gcp-op tests started failing with 

=== RUN   TestMCCPausedKubeletCAAlert
    mcc_test.go:30: Pausing pool
    mcc_test.go:35: Paused
    mcc_test.go:38: Patching certificate
    mcc_test.go:41: Patched
    mcc_test.go:44: Waiting for rendered config to get stuck behind pause
    mcc_test.go:47: Certificate stuck behind paused (as expected)
    mcc_test.go:50: Getting monitoring token
    mcc_test.go:52: 
        	Error Trace:	mcc_test.go:52
        	Error:      	Expected nil, but got: &errors.errorString{s:"No token found in openshift-monitoring secrets"}
        	Test:       	TestMCCPausedKubeletCAAlert
--- FAIL: TestMCCPausedKubeletCAAlert (20.25s)
FAIL
FAIL	github.com/openshift/machine-config-operator/test/e2e	1258.101s
FAIL

In a pretty consistent fashion, see

https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op

example: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/3166/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/1531149248697995264

Comment 1 Yu Qi Zhang 2022-05-31 21:11:03 UTC
*** Bug 2092124 has been marked as a duplicate of this bug. ***

Comment 4 Sergio 2022-06-02 13:42:13 UTC
Verified using UPI on GCP version:
$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-06-01-200905   True        False         177m    Cluster version is 4.11.0-0.nightly-2022-06-01-200905


Verification steps:
1) clone https://github.com/openshift/machine-config-operator
2) checkout 4.11 branch
3) run e2e tests: "make test-e2e"
4) verify that the test case TestMCCPausedKubeletCAAlert is passing
=== RUN   TestMCCPausedKubeletCAAlert
    mcc_test.go:30: Pausing pool
    mcc_test.go:35: Paused
    mcc_test.go:38: Patching certificate
    mcc_test.go:41: Patched
    mcc_test.go:44: Waiting for rendered config to get stuck behind pause
    mcc_test.go:47: Certificate stuck behind paused (as expected)
    mcc_test.go:50: Getting monitoring token
    mcc_test.go:55: Getting metrics listener service details
    mcc_test.go:75: Metric successfully set
    mcc_test.go:86: Unpausing pool
    mcc_test.go:90: Waiting for config to sync after unpause...
    mcc_test.go:96: Unpaused + Synced
    mcc_test.go:98: Checking for metric value...
    mcc_test.go:109: Metric has correctly been reset after pool unpaused
--- PASS: TestMCCPausedKubeletCAAlert (65.13s)



We move this issue to VERIFIED  status

Comment 6 errata-xmlrpc 2022-08-10 11:15:13 UTC
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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069


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