Bug 1880741
| Summary: | origin e2e test fails due to mysterious taints | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Michael Gugino <mgugino> |
| Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
| Cloud Compute sub component: | Other Providers | QA Contact: | sunzhaohua <zhsun> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | ||
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| 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: | 2020-10-27 16:42:58 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: | |||
Hit this again here: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_machine-api-operator/706/pull-ci-openshift-machine-api-operator-master-e2e-vsphere-serial/1308850247107088384 Tested locally didn't meet this again, move this to verified. clusterversion: 4.6.0-0.nightly-2020-09-26-202331 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 (OpenShift Container Platform 4.6 GA Images), 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:4196 |
When we scale up a worker in origin e2e test, the node that gets created has the following taints: Sep 19 02:48:24.028: INFO: node/ci-op-469ls8mj-129d4-b5f8x-worker-7hmtt had unexpected taints: []v1.Taint{v1.Taint{Key:"kubernetes.io/e2e-taint-key-43604c41-e393-4fb0-ae30-904ffbc870d0", Value:"testing-taint-value-fd73330a-2df4-4fd2-96e4-a432000a1cd7", Effect:"PreferNoSchedule", TimeAdded:(*v1.Time)(nil)}} Searching through the repo, various pod logs, and machines/machinesets, it's unclear how or why these taints are getting applied. After fixing this bug, this issue might go away: https://bugzilla.redhat.com/show_bug.cgi?id=1880738 It's still unclear why these taints are being applied, so we need to ensure that we either account for them or have them stop being applied. Failed test: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-vsphere-serial/1307118468956426240 origin e2e tests I'm referring to: https://github.com/openshift/origin/blob/f749b790af49f66b558b04f4ffd2799dd4a1e165/test/extended/machines/scale.go#L121