Description of problem: Using the same DC, Deploy fails when using "Deploy" on web console, but succeed when using rollout latest Version-Release number of selected component (if applicable): kubernetes v1.4.0+776c994 Server https://api.ded-stg2-aws.openshift.com:443 openshift v3.4.1.10 How reproducible: Always Steps to Reproduce: 1.oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/application-template.json 2.oc start-build frontend 3.After build complete, "Deploy" on the web console; 4. oc rollout latest frontend Expected Result 3. Success in deployment; 4. Success in deployment; Actual Result: 3. failed It seemed that "deploy" on webconsole is not using the right command. please confirm , thanks. Additional info:
Can you please provide the error it fails with in webconsole? A deployer log, events, anything that can tell us why the deploy failed.
I guess the root is "automatic": false, on webconsole , the deploy still use 'oc deploy ... --latest' command , we should use 'oc rollout latest' .
We never switched to creating a DeploymentRequest and using deploymentconfigs/instantiate, will be fixing that in https://github.com/openshift/origin-web-console/pull/1434/files
also the CLI command we reference in the console in the DC Triggers section was already updated, in master it tells the user to run oc rollout latest
This has been merged into ocp and is in OCP v3.6.39 or newer.
Verify in OCP v3.6.39; Fixed!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1716