-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.6
-
Low
-
None
-
Unspecified
-
If docs needed, set a value
-
IBM Cloud does not support and will not support customer access to master nodes.
Therefor we need to skip the following conformance tests:
[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "lb-ext.kubeconfig" should be present on all masters and work [Suite:openshift/conformance/parallel/minimal]
[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "lb-int.kubeconfig" should be present on all masters and work [Suite:openshift/conformance/parallel/minimal]
[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "localhost-recovery.kubeconfig" should be present on all masters and work [Suite:openshift/conformance/parallel/minimal]
[Conformance][sig-api-machinery][Feature:APIServer] local kubeconfig "localhost.kubeconfig" should be present on all masters and work [Suite:openshift/conformance/parallel/minimal]
Even though these tests shouldn't fail (because the test shouldn't even see any master nodes to loop through), it still causes flaky test failures on our end.
Please re-assign to correct component location if selected wrong.