Red Hat Bugzilla – Bug 1303938
[RFE] ability to deploy newest image without triggers
Last modified: 2017-03-08 13:43 EST
Description of request: Currently it's impossible to specify when to start a deployment with the latest image. Triggers will cause each build to cause a deploy. To overcome that triggers have to be disabled, and enabled once a deploy is desired. This Request is to add possibility to deploy the newest image manually without enabling triggers. Upstream RFE: https://trello.com/c/uQP2AxXy/508-deploy-most-recently-available-image Version-Release number of selected component (if applicable): 3.1.1
*** Bug 1303963 has been marked as a duplicate of this bug. ***
*** Bug 1379563 has been marked as a duplicate of this bug. ***
Confirmed with latest OCP 3.4, use 'oc rollout latest' command can deploy with the latest image: openshift version openshift v3.4.0.11 kubernetes v1.4.0+776c994 etcd 3.1.0-alpha.1 [root@dhcp-141-156 testjson]# oc describe is ruby-ex Name: ruby-ex Namespace: testzy Created: 10 minutes ago Labels: app=ruby-ex Annotations: openshift.io/generated-by=OpenShiftNewApp Docker Pull Spec: 172.30.42.137:5000/testzy/ruby-ex Unique Images: 1 Tags: 1 latest pushed image * 172.30.42.137:5000/testzy/ruby-ex@sha256:6668749007147d3084cabb28086e4bdd1cc8c58d312fe8deae60b46c8e91ca90 7 minutes ago [root@dhcp-141-156 testjson]# oc describe po ruby-ex-1-omnsj Name: ruby-ex-1-omnsj Namespace: testzy Security Policy: restricted ...... Containers: ruby-ex: Container ID: docker://da1a65d7379625480619e6d90854f04f69a01e914b29c16a27f69e68f696d716 Image: 172.30.42.137:5000/testzy/ruby-ex@sha256:6668749007147d3084cabb28086e4bdd1cc8c58d312fe8deae60b46c8e91ca90 Image ID: docker://sha256:49812e877aa890a31ed4b552f3c15d1b588f0007aafc1c226be98377a49cde53 Port: 8080/TCP
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/RHBA-2017:0066