[alice@ose3-master beta4]$ osc new-app -l name=wordpress https://github.com/openshift/centos7-wordpress.git imageStreams/centos imageStreams/centos7-wordpress buildConfigs/centos7-wordpress deploymentConfigs/centos7-wordpress services/centos7-wordpress A build was created - you can run `osc start-build centos7-wordpress` to start it. Service "centos7-wordpress" created at 172.30.135.252 with port mappings 22. [alice@ose3-master beta4]$ [alice@ose3-master beta4]$ [alice@ose3-master beta4]$ [alice@ose3-master beta4]$ osc get pod POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE centos7-wordpress-1-rlg0q 10.1.2.23 ose3-node2.example.com/192.168.133.4 deployment=centos7-wordpress-1,deploymentconfig=centos7-wordpress,name=wordpress Pending 32 seconds centos7-wordpress library/centos7-wordpress:latest Waiting Error: image library/centos7-wordpress:latest not found [alice@ose3-master beta4]$ osc version osc v0.5.2.2-26-g701be15 kubernetes v0.17.1-804-g496be63
This is working as designed. The deployment config will try to deploy the image and won't succeed until one is available from the build.
So the design is to fail with an error by default? Doesn't that seem a bit... odd?
I was also concerned when I first saw this behavior. Is this decision/process documented somewhere in the Admin / Users's guide?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days