Bug 2080679

Summary: [rebase v1.24] [sig-cli] test failure
Product: OpenShift Container Platform Reporter: Abu Kashem <akashem>
Component: ocAssignee: Maciej Szulik <maszulik>
oc sub component: oc QA Contact: zhou ying <yinzhou>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: mfojtik
Version: 4.11   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:09:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Abu Kashem 2022-04-30 22:16:38 UTC
The following sig-cli tests are failing:
- [sig-cli][Feature:LegacyCommandTests][Disruptive][Serial] test-cmd: test/cmd/secrets.sh

```
{  fail [github.com/openshift/origin/test/extended/cmd/cmd.go:118]: Expected
    <[]error | len:1, cap:1>: [
        {
            s: "error waiting for the pod 'test-cmd' to complete: md/secrets.sh:142: executing 'oc secret --help' expecting success\nRunning test/cmd/secrets.sh:143: executing 'oc secret new --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:143: executing 'oc secret new --help' expecting success\nRunning test/cmd/secrets.sh:144: executing 'oc secret new-dockercfg --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:144: executing 'oc secret new-dockercfg --help' expecting success\nRunning test/cmd/secrets.sh:145: executing 'oc secret new-basicauth --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:145: executing 'oc secret new-basicauth --help' expecting success\nRunning test/cmd/secrets.sh:146: executing 'oc secret new-sshauth --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:146: executing 'oc secret new-sshauth --help' expecting success\nRunning test/cmd/secrets.sh:147: executing 'oc secret add --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:147: executing 'oc secret add --help' expecting success\nRunning test/cmd/secrets.sh:148: executing 'oc secret link --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:148: executing 'oc secret link --help' expecting success\nRunning test/cmd/secrets.sh:149: executing 'oc secret unlink --help' expecting success...\nSUCCESS after 0.000s: test/cmd/secrets.sh:149: executing 'oc secret unlink --help' expecting success\nsecrets: ok\nRunning test/cmd/secrets.sh:155: executing 'oc serviceaccounts create-kubeconfig default > '/tmp/openshift/secrets/generated_default.kubeconfig'' expecting success...\nFAILURE after 0.000s: test/cmd/secrets.sh:155: executing 'oc serviceaccounts create-kubeconfig default > '/tmp/openshift/secrets/generated_default.kubeconfig'' expecting success: the command returned the wrong error code\nThere was no output from the command.\nStandard error from the command:\nerror: could not find a service account token for service account \"default\"\n[ERROR] hack/lib/cmd.sh:10: `return \"${return_code}\"` exited with status 1.\n",
        },
    ]
to have length 0}
```


- [sig-cli][Feature:LegacyCommandTests][Disruptive][Serial] test-cmd: test/cmd/quota.sh 

```
{  fail [github.com/openshift/origin/test/extended/cmd/cmd.go:118]: Expected
    <[]error | len:1, cap:1>: [
        {
            s: "error waiting for the pod 'test-cmd' to complete: Now using project \"cmd-quota\" on server \"https://api.ci-op-tm7ch049-fc795.ci.azure.devcluster.openshift.com:6443\".\n\nYou can add applications to this project with the 'new-app' command. For example, try:\n\n    oc new-app rails-postgresql-example\n\nto build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application:\n\n    kubectl create deployment hello-node --image=k8s.gcr.io/e2e-test-images/agnhost:2.33 -- /agnhost serve-hostname\n\nRunning test/cmd/quota.sh:22: executing 'oc new-project quota-foo --as=deads --as-group=system:authenticated --as-group=system:authenticated:oauth' expecting success...\nSUCCESS after 0.000s: test/cmd/quota.sh:22: executing 'oc new-project quota-foo --as=deads --as-group=system:authenticated --as-group=system:authenticated:oauth' expecting success\nRunning test/cmd/quota.sh:23: executing 'oc label namespace/quota-foo owner=deads' expecting success...\nSUCCESS after 1.000s: test/cmd/quota.sh:23: executing 'oc label namespace/quota-foo owner=deads' expecting success\nRunning test/cmd/quota.sh:24: executing 'oc get secrets -o name -n quota-foo | wc -l' expecting any result and text '9'; re-trying every 0.2s until completion or 60.000s...\nFAILURE after 60.000s: test/cmd/quota.sh:24: executing 'oc get secrets -o name -n quota-foo | wc -l' expecting any result and text '9'; re-trying every 0.2s until completion or 60.000s: the command timed out\nStandard output from the command:\n6\n... repeated 165 times\nStandard error from the command:\n[ERROR] hack/lib/cmd.sh:139: `return \"${return_code}\"` exited with status 1.\n",
        },
    ]
to have length 0}
```


https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/1248/pull-ci-openshift-kubernetes-master-e2e-agnostic-cmd/1520465065659076608

Comment 6 errata-xmlrpc 2022-08-10 11:09:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069