el96-y1@el96-lrel@lvms scenario is failing with the error below.

+ KUBECONFIG=/var/lib/microshift/resources/kubeadmin/kubeconfig
+ result=
+ ns=test-lvms
+ echo INFO: 'Delete deployment storage resource.......'
++ sudo oc --kubeconfig /var/lib/microshift/resources/kubeadmin/kubeconfig delete deployment mydep-lvms -n test-lvms
Error from server (NotFound): deployments.apps "mydep-lvms" not found
+ result=
+ [[ '' =~ deleted ]]
ERROR: Deployment resource not found.
INFO: Delete PVC storage resource.......
+ echo ERROR: 'Deployment resource not found.'
+ echo INFO: 'Delete PVC storage resource.......'
++ sudo oc --kubeconfig /var/lib/microshift/resources/kubeadmin/kubeconfig delete pvc mypvc-lvms -n test-lvms
Error from server (NotFound): persistentvolumeclaims "mypvc-lvms" not found
ERROR: PVC resource not found.
INFO: Delete test namepsace.......
+ result=
+ [[ '' =~ deleted ]]
+ echo ERROR: 'PVC resource not found.'
+ echo INFO: 'Delete test namepsace.......'
++ sudo oc --kubeconfig /var/lib/microshift/resources/kubeadmin/kubeconfig delete ns test-lvms
Error from server (NotFound): namespaces "test-lvms" not found
+ result=
+ [[ '' =~ deleted ]]
ERROR: Namespace resource not found.
+ echo ERROR: 'Namespace resource not found.'

1.
2.
3.

cleanupWorkload.sh script is failing, since the deployment is present after the upgrade and deletion may not be really necessary, can we remove this completely ? I am not sure if something in standard1 cleaning up this namespace already.

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_microshift/5996/pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release/2006252963512717312/artifacts/e2e-aws-tests-bootc-release/openshift-microshift-e2e-metal-tests/artifacts/scenario-info/el96-y1@el96-lrel@lvms/boot_and_run.log