Bug 1500225

Summary: [online-stg] `oc describe imagestreams -n openshift` and `oc new-app` with IS from `-n openshift` fail when using oc 3.7/3.8 VS 3.6 online-stg
Product: OpenShift Online Reporter: Bing Li <bingli>
Component: ocAssignee: Juan Vallejo <jvallejo>
Status: CLOSED CURRENTRELEASE QA Contact: Xingxing Xia <xxia>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.xCC: abhgupta, aos-bugs, ffranz, jokerman, jvallejo, mkhan, mmccomas, smunilla, wzheng, xiuwang, xxia, yasun
Target Milestone: ---Keywords: OnlinePro, Reopened
Target Release: 3.x   
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: 2018-03-05 18:17:19 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:

Comment 2 Mo 2017-10-10 20:20:08 UTC
This is a duplicate of 1493213 which will be fixed by the force role reconciliation using ansible via https://github.com/openshift/openshift-ansible/pull/5617

*** This bug has been marked as a duplicate of bug 1493213 ***

Comment 3 Xingxing Xia 2017-11-22 02:03:54 UTC
The bug 1493213 is VERIFIED for a month, online-stg still has the issue due to no update to online-stg so far. This bug seems to also cause new app with imagestream from "openshift" project to fail:
$ oc new-app --image-stream=openshift/python:latest --code=https://github.com/openshift/django-ex --name=python-sample
error: no match for "openshift/python:latest"

The 'oc new-app' command will match arguments to the following types:

  1. Images tagged into image streams in the current project or the 'openshift' project
     - if you don't specify a tag, we'll add ':latest'
  2. Images in the Docker Hub, on remote registries, or on the local Docker engine
  3. Templates in the current project or the 'openshift' project
  4. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to point to an image that does not exist yet.

See 'oc new-app -h' for examples

$ oc describe is python -n openshift
Error from server (Forbidden): User "xxia-5" cannot get imagestreams.image.openshift.io in project "openshift"

Thus let me reopen this bug in order to just TRACK the solving for online-stg

Comment 4 XiuJuan Wang 2017-12-11 08:17:23 UTC
oc v3.8.11 vs online-stg(v3.6.173.0.21)
$oc new-app -S --template=jenkins --loglevel=5
I1211 15:42:22.390702   12499 newapp.go:548] Docker client did not respond to a ping: Get http://unix.sock/_ping: dial unix /var/run/docker.sock: connect: permission denied
I1211 15:42:23.897826   12499 newapp.go:687] Code 
I1211 15:42:23.897856   12499 newapp.go:688] Components jenkins
F1211 15:42:23.912152   12499 helpers.go:120] error: no matches found

Comment 6 Bing Li 2018-01-03 03:33:59 UTC
This issue still exists on online-stg, I will verify this bug after upgrading.

Server https://api.online-stg.openshift.com:443
openshift v3.6.173.0.21
kubernetes v1.6.1+5115d708d7

Comment 7 Xingxing Xia 2018-01-03 07:26:47 UTC
Could you help drop this bug from the errata advisory? As comment 3 said, this bug is only used for tracking the issue in online-stg. Thanks

Comment 8 Abhishek Gupta 2018-01-18 17:36:15 UTC
online-int has been upgraded to OCP 3.7.x - can you please confirm that this issue does not exist there? If so, then this should be addressed with the upcoming Pro tier release.

Comment 9 Xingxing Xia 2018-01-19 06:40:08 UTC
online-int v3.7 has not this problem:
$ versions/ose/v3.8.26/oc describe is ruby -n openshift
Name:			ruby
Namespace:		openshift
<snipped>

$ versions/ose/v3.8.26/oc new-app --image-stream=openshift/python:latest --code=https://github.com/openshift/django-ex --name=python-sample
--> Found image 42d60f5 (8 weeks old) in image stream "openshift/python" under tag "latest" for "openshift/python:latest"
<snipped>

It should be addressed in upcoming online-stg upgrade to v3.7. After thinking a while, it is viable to change bug status to VERIFIED for comment 7. Thx