Hide Forgot
Description of problem: Hi, when you create new app and you will: - Disable "Automatically build a new image when the builder image changes" - Disable "Launch the first build when the build configuration is created" - Disable "Autodeploy when: New image is available" - Disable "Autodeploy when: Deployment configuration changes" and manually run, oc start-build <bc> and then oc deploy --latest, then the deploy will fail with message "image can't be pulled". The issue is within the dc. After adding the address of registry and namespace before the image setting it will work: From containers: name: <NAME> image: '<IMAGE>:latest' To: containers: name: <NAME> image: '<IP_REGISTRY>:5000/<NAMESPACE>/<IMAGE>:latest' I did the test with both, it doesn't work as mentioned above. Version-Release number of selected component (if applicable): OpenShift Container Platform 3.3.0 How reproducible: Create 2 projects, one as above, one normally. Build the app, deploy the app. Steps to Reproduce: 1. create project with settings above 2. start build 3. start deploy Actual results: the deploy fails if set above, the dc must be edited manually Expected results: with the settings above, the deploy should be fine Additional info:
This is fixed in 3.4 for the web console (removing the ability to "Autodeploy when: New image is available" does not remove the image change trigger anymore, just sets Automatic to False). https://github.com/openshift/origin-web-console/pull/810 Vladislav, do we need to backport the fix to 3.3?
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1383804 with target release 3.4.0. *** This bug has been marked as a duplicate of bug 1383804 ***