-
Bug
-
Resolution: Unresolved
-
Normal
-
4.16.0
-
None
-
Low
-
No
-
CNF Compute Sprint 250, CNF Compute Sprint 251, CNF Compute Sprint 252, CNF Compute Sprint 253, CNF Compute Sprint 254, CNF Compute Sprint 255, CNF Compute Sprint 256, CNF Compute Sprint 257, CNF Compute Sprint 258, CNF Compute Sprint 259, CNF Compute Sprint 260, CNF Compute Sprint 261, CNF Compute Sprint 262
-
13
-
False
-
-
Release Note Not Required
-
In Progress
-
This is a clone of issue OCPBUGS-27847. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-27465. The following is the description of the original issue:
—
Description of problem:
The test implementation in https://github.com/openshift/origin/commit/5487414d8f5652c301a00617ee18e5ca8f339cb4#L56 assumes there is just one kubelet service or at least that it is always the first one in the MCP. Which just changed in https://github.com/openshift/machine-config-operator/pull/4124 and the test is failing.
Version-Release number of selected component (if applicable):
master branch of 4.16
How reproducible:
always during test
Steps to Reproduce:
1. Test with https://github.com/openshift/machine-config-operator/pull/4124 applied
Actual results:
Test detects a wrong service and fails
Expected results:
Test finds the proper kubelet.service and passes
Additional info:
- blocks
-
OCPBUGS-34998 origin tests fail when two systemd service files are present in the kubelet machineconfig
- New
- clones
-
OCPBUGS-27847 origin tests fail when two systemd service files are present in the kubelet machineconfig
- Verified
- is blocked by
-
OCPBUGS-27847 origin tests fail when two systemd service files are present in the kubelet machineconfig
- Verified
- is cloned by
-
OCPBUGS-34998 origin tests fail when two systemd service files are present in the kubelet machineconfig
- New
- links to