Hide Forgot
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:
The error message is coming from the server.
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
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
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?
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.
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.
@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.
@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?
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.
Created attachment 1247125 [details] BuildConfig used to reproduce the issue
sorry for the long time to provide the buildconfig
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.
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