Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1303938

Summary: [RFE] ability to deploy newest image without triggers
Product: OpenShift Container Platform Reporter: Evgheni Dereveanchin <ederevea>
Component: RFEAssignee: Michail Kargakis <mkargaki>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact:
Priority: high    
Version: 3.1.0CC: aos-bugs, erich, jkaur, jokerman, misalunk, mkargaki, mmccomas, pep, tdawson, wsun, xxia
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
A new endpoint and 'oc rollout latest' that uses the endpoint and supersedes 'oc deploy --latest' are added in 3.4 to enable manual deployments without the need to enable triggers.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:39:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1267746    

Description Evgheni Dereveanchin 2016-02-02 13:05:14 UTC 
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
Comment 1 Josep 'Pep' Turro Mauri 2016-02-03 12:27:35 UTC 
*** Bug 1303963 has been marked as a duplicate of this bug. ***
Comment 2 Michail Kargakis 2016-09-27 09:19:35 UTC 
*** Bug 1379563 has been marked as a duplicate of this bug. ***
Comment 6 zhou ying 2016-10-17 05:55:48 UTC 
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
Comment 8 errata-xmlrpc 2017-01-18 12:39:12 UTC 
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