On s390x, as part of the Descheduler e2e workflow, the descheduler Deployment is created in the kube-system namespace. However, the Deployment stays in a 0/1 unavailable state due to missing ServiceAccount descheduler-sa, resulting in the pod failing to start and the e2e test failure

    Everytime

    1.Install descheduler operator.
    2.Clone https://github.ibm.com/OpenShift-on-Z/ocp_test_automation -b madeel-pipes  branch
    3.Run the descheduler e2e test suit     

    When e2e tests are executed, descheduler deployment in kube-system namespace is in 0/1 state.

    When e2e tests are executed, descheduler deployment in kube-system namespace is expected to be in 1/1 state.

 Logs: https://drive.google.com/drive/folders/14FhIs1xj1Qmqan1HCpKslnN14QJJi2Cl?usp=sharing