Bug 1393003

Summary: Provide the namespace of the image stream tags not found
Product: OKD Reporter: Aurélien Pupier <apupier>
Component: BuildAssignee: Corey Daley <cdaley>
Status: CLOSED CURRENTRELEASE QA Contact: Wang Haoran <haowang>
Severity: low Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, apupier, bparees, dyan, mmccomas, wzheng
Target Milestone: ---   
Target Release: ---   
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: 2017-05-30 12:48:36 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:
Attachments:
Description Flags
Error Message without namespace specified
none
BuildConfig used to reproduce the issue none

Description Aurélien Pupier 2016-11-08 16:39:23 UTC
Created attachment 1218612 [details]
Error Message without namespace specified

Description of problem:
I had the wrong imagestream namespace specified in the build config, when i kick a build it says that the <myImageStreamName> is not found but I was able to see it.
The issue was just the namespace.
The error message can be improved by providing the namespace.


Version-Release number of selected component (if applicable):
OpenShift Master:
v3.3.0.32
Kubernetes Master:
v1.3.0+52492b4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jessica Forrester 2016-11-08 17:25:29 UTC
The error message is coming from the server.

Comment 2 Martin Milata 2016-11-14 19:01:39 UTC
Aurélien, do you refer to the ImageStream in the "from" section? I.e. does it contain your base image or do you want to push to that ImageStream when built?

The former case is probably already fixed in master, 3.4 should contain the fix: https://github.com/openshift/origin/pull/10868

Comment 3 Aurélien Pupier 2016-11-15 07:46:07 UTC
I'm talking about the message which is displayed in the UI when trying to launch the build in the web UI.
You can see it in the attachment.

So I don't know if it the place that is targeted by the PR https://github.com/openshift/origin/pull/10868

Comment 4 Martin Milata 2016-11-15 11:51:13 UTC
I think the UI just displays what's sent by the server which should be fixed in the PR. Can you please share the BuildConfig so I can verify?

Comment 5 openshift-github-bot 2016-11-17 05:54:00 UTC
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/b94313c00c053eaebf3f2183f15bd61b6516a7fd
newapp: do not fail when file exists with same name as image

When "oc new-app foo/bar" was run in a directory with regular file named
"foo" it failed with:

  error: unable to load template file "foo/bar": the path "foo/bar"
  cannot be accessed: stat foo/bar: not a directory

Fixes bug 1393003.

Comment 6 Martin Milata 2016-11-21 15:41:28 UTC
Apologies, the comment above is not related, I have entered the wrong bug number in commit message:/

Aurélien, can you please share your BuildConfig if it doesn't contain any nonpublic information? With it I should be able to determine if further fix is needed.

Comment 7 Aurélien Pupier 2016-11-21 16:34:35 UTC
@Martin Unfortunately, currently i'm not able to start anymore my CDK instance (and so OpenShift instance)
I'm not sure when I will have time to work again on this subject and resetup eveyrthing.

Comment 8 Corey Daley 2017-01-25 23:55:05 UTC
@Aurélien, 
Can you please provide the build config that you were using?  And did you edit the buildconfig in the web editor or manually specify it on the command line?

Comment 9 Corey Daley 2017-01-27 21:08:06 UTC
From what I can tell this has already been fixed and is now showing the namespace in the error message when i start a build and the imagestreamtag is not available.  If you can provide a copy of your buildconfig and show what field you had changed, it would be helpful.

Comment 10 Aurélien Pupier 2017-02-02 13:27:41 UTC
Created attachment 1247125 [details]
BuildConfig used to reproduce the issue

Comment 11 Aurélien Pupier 2017-02-02 13:28:02 UTC
sorry for the long time to provide the buildconfig

Comment 12 Corey Daley 2017-02-03 16:01:34 UTC
Using the following OpenShift Version:
oc v1.5.0-alpha.2+ed1d332-279
kubernetes v1.5.2+43a9be4
features: Basic-Auth

Server https://192.168.50.43:8443
openshift v1.5.0-alpha.2+ed1d332-279
kubernetes v1.5.2+43a9be4

I was not able to duplicate this issue.

The error message that I received starting a new build with an invalid imagestream namespace was:

An error occurred while starting the build.Error resolving ImageStreamTag fis-java-openshift:2.0 in namespace testingblah: imagestreams "fis-java-openshift" not found

Which does include the namespace in the error message.

Comment 13 Dongbo Yan 2017-02-05 13:23:58 UTC
Verified
openshift v3.5.0.16+a26133a
kubernetes v1.5.2+43a9be4
etcd 3.1.0

# oc start-build nodejs-mongodb-example 
The ImageStreamTag "nodejs:4" is invalid: from: Error resolving ImageStreamTag nodejs:4 in namespace newopenshift: imagestreams "nodejs" not found