Default OpenShift Conformance test suite (kubernetes/conformance) scheduled by OPCT is reporting permanent failures.

    4.13+

    Always

    1. Install a cluster on AWS provider with platform type External
    2. Create OPCT requirements (dedicated node / label and taints)
    3. Run OPCT w/ default workflow
    4. Collect and review the results for "kubernetes conformance"
    

 $ for RES in $(ls ci-result_opct*.tar.gz); do echo "Extractubg kube failures from $RES..."; jq -r '.provider.plugins["10-openshift-kube-conformance"].testsFailuresPriority[].name' $RES.results/opct-report.json | sort > kube-${RES}.failures.txt ; done
 
$ wc -l kube-ci-result_opct_external-aws*
   3 kube-ci-result_opct_external-aws_1757255745801293824.tar.gz.failures.txt
   3 kube-ci-result_opct_external-aws-ccm_1757132567846326272.tar.gz.failures.txt
   3 kube-ci-result_opct_external-aws-ccm_1757267257693573120.tar.gz.failures.txt
   3 kube-ci-result_opct_external-aws-ccm_1757495441294888960.tar.gz.failures.txt

$ cat kube-ci-result_opct_external-aws*.txt | sort | uniq -c | sort -rn
      4 [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching  [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]
      4 [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run  [Conformance] [Suite:openshift/conformance/serial/minimal] [Suite:k8s]
      4 [sig-cli] Kubectl client Kubectl diff should check if kubectl diff finds a difference for Deployments [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]

    No failures, or individual e2e failures addressed (without environment issue)

   - read the "Issue #3" in the comment https://issues.redhat.com/browse/SPLAT-1458?focusedId=24193649&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24193649