Bug 1506175

Could anybody help check? The issue still exists in today's free-int v3.7.0-0.191.0 (online version 3.6.0.38)

I did not do any operation that could be destructive to the project. Thus it is flaky to have the issue.

Not sure which Component it is close to, maybe Build/Upgrade? CC'ing Ben and Scott :)

It sounds to me like the broken project has a bad docker secret in it.  What docker secrets exist in the broken project?

Ah, thank you, you're right
$ oc get secret
mysecret                   kubernetes.io/dockercfg               1         21d
$ oc extract secret/mysecret
.dockercfg
$ cat .dockercfg
{"docker.io":{"username":"xxia","password":"abcd","email":"xxia","auth":"eHhpYTphYmNk"}}

After removing the secret, `oc new-app openshift/hello-openshift` works. It happens in OCP too (both v3.6.173.0.62 and v3.7.0-0.191.0 are checked)

The secret (user/password are fake) was created during case test. I didn't imagine it affects `oc new-app` for _public_ image. IMO tt is bug, the reasons are:
a) `oc run testdc --image=openshift/hello-openshift` is not affected
b) DC yaml has array spec.template.spec.imagePullSecrets, put above secret in DC that uses _public_ image, the DC deployment is not affected:
$ vi mydc.yaml
apiVersion: v1
kind: DeploymentConfig
metadata:
  labels:
    run: mydc
  name: mydc
spec:
  replicas: 1
  selector:
    run: mydc
  template:
    metadata:
      labels:
        run: mydc
    spec:
      containers:
      - image: openshift/hello-openshift
        name: mydc
      imagePullSecrets:
      - name: mysecret # above fake secret
$ oc create -f mydc.yaml
$ oc get pod
NAME           READY     STATUS    RESTARTS   AGE
mydc-1-hv953   1/1       Running   0          8m

Thus, `oc new-app` with public image should be not affected by the fake secret

Agreed, if the image is public, new-app should be able to access it despite the bad secret.  Severity is low though since it is still a bad secret and the fix is to delete the secret or correct it.

Given the cause in comment 4, in "Description" step 3, web console shows same error. Not sure if your fix would automatically solve the error in web. If not, web separate fix may be needed, CC'ing Samuel fyi :)

https://github.com/openshift/origin/pull/18012

Do we need QA for this one? Automated tests was included,

> Do we need QA for this one? Automated tests was included,

yes, all bugs that resulted in a code fix go back through QE so they can verify the fix+update their test cases if necessary.

Verified in v3.9.0-0.53.0
$ cat .dockercfg
{"docker.io":{"username":"xxia","password":"abcd","email":"xxia","auth":"eHhpYTphYmNk"}}
$ oc secrets new mysecret .dockercfg=.dockercfg
$ oc get secret mysecret
mysecret                   kubernetes.io/dockercfg               1         2s

$ oc new-app openshift/hello-openshift
--> Found Docker image b94da9e (4 hours old) from Docker Hub for "openshift/hello-openshift"
...


Web console "Deploy Image" page also has no the reported error now

Is something missing from my side on this?

If you're getting emails about it, it's probably to fill in the doc text.

Choose the doc type in the upper right (probably "Bug Fix") and then fill in the template for the doc text in the next field.