1OC ROLLOUT(1)                      June 2016                     OC ROLLOUT(1)
2
3
4

NAME

6       oc rollout retry - Retry the latest failed rollout
7
8
9

SYNOPSIS

11       oc rollout retry [OPTIONS]
12
13
14

DESCRIPTION

16       If  a  rollout  fails,  you may opt to retry it (if the error was tran‐
17       sient). Some rollouts may never successfully complete - in  which  case
18       you can use the rollout latest to force a redeployment. If a deployment
19       config has completed rolling out successfully  at  least  once  in  the
20       past,  it  would  be  automatically  rolled  back in the event of a new
21       failed rollout. Note that you would still need to update the  erroneous
22       deployment  config  in order to have its template persisted across your
23       application.
24
25
26

OPTIONS

28       --allow-missing-template-keys=true
29           If true, ignore any errors in templates when a field or map key  is
30       missing  in  the  template.  Only applies to golang and jsonpath output
31       formats.
32
33
34       -f, --filename=[]
35           Filename, directory, or URL to files Filename, directory, or URL to
36       a file identifying the resource to get from a server.
37
38
39       -o, --output=""
40           Output  format. One of: json|yaml|name|template|go-template|go-tem‐
41       plate-file|templatefile|jsonpath|jsonpath-file.
42
43
44       -R, --recursive=false
45           Process the directory used in -f,  --filename  recursively.  Useful
46       when  you  want  to  manage related manifests organized within the same
47       directory.
48
49
50       --template=""
51           Template string or path to template file  to  use  when  -o=go-tem‐
52       plate,  -o=go-template-file.  The template format is golang templates [
53http://golang.org/pkg/text/template/#pkg-overview⟩].
54
55
56

OPTIONS INHERITED FROM PARENT COMMANDS

58       --allow_verification_with_non_compliant_keys=false
59           Allow  a  SignatureVerifier  to  use  keys  which  are  technically
60       non-compliant with RFC6962.
61
62
63       --alsologtostderr=false
64           log to standard error as well as files
65
66
67       --application_metrics_count_limit=100
68           Max number of application metrics to store (per container)
69
70
71       --as=""
72           Username to impersonate for the operation
73
74
75       --as-group=[]
76           Group  to  impersonate for the operation, this flag can be repeated
77       to specify multiple groups.
78
79
80       --azure-container-registry-config=""
81           Path to the file containing Azure container registry  configuration
82       information.
83
84
85       --boot_id_file="/proc/sys/kernel/random/boot_id"
86           Comma-separated  list  of files to check for boot-id. Use the first
87       one that exists.
88
89
90       --cache-dir="/builddir/.kube/http-cache"
91           Default HTTP cache directory
92
93
94       --certificate-authority=""
95           Path to a cert file for the certificate authority
96
97
98       --client-certificate=""
99           Path to a client certificate file for TLS
100
101
102       --client-key=""
103           Path to a client key file for TLS
104
105
106       --cloud-provider-gce-lb-src-cidrs=130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16
107           CIDRs opened in GCE firewall for LB traffic proxy  health checks
108
109
110       --cluster=""
111           The name of the kubeconfig cluster to use
112
113
114       --container_hints="/etc/cadvisor/container_hints.json"
115           location of the container hints file
116
117
118       --containerd="unix:///var/run/containerd.sock"
119           containerd endpoint
120
121
122       --context=""
123           The name of the kubeconfig context to use
124
125
126       --default-not-ready-toleration-seconds=300
127           Indicates    the    tolerationSeconds   of   the   toleration   for
128       notReady:NoExecute that is added by default to every pod that does  not
129       already have such a toleration.
130
131
132       --default-unreachable-toleration-seconds=300
133           Indicates  the  tolerationSeconds  of  the  toleration for unreach‐
134       able:NoExecute that is added by default to  every  pod  that  does  not
135       already have such a toleration.
136
137
138       --docker="unix:///var/run/docker.sock"
139           docker endpoint
140
141
142       --docker-tls=false
143           use TLS to connect to docker
144
145
146       --docker-tls-ca="ca.pem"
147           path to trusted CA
148
149
150       --docker-tls-cert="cert.pem"
151           path to client certificate
152
153
154       --docker-tls-key="key.pem"
155           path to private key
156
157
158       --docker_env_metadata_whitelist=""
159           a  comma-separated  list of environment variable keys that needs to
160       be collected for docker containers
161
162
163       --docker_only=false
164           Only report docker containers in addition to root stats
165
166
167       --docker_root="/var/lib/docker"
168           DEPRECATED: docker root is read from docker info (this is  a  fall‐
169       back, default: /var/lib/docker)
170
171
172       --enable_load_reader=false
173           Whether to enable cpu load reader
174
175
176       --event_storage_age_limit="default=24h"
177           Max length of time for which to store events (per type). Value is a
178       comma separated list of key values, where  the  keys  are  event  types
179       (e.g.: creation, oom) or "default" and the value is a duration. Default
180       is applied to all non-specified event types
181
182
183       --event_storage_event_limit="default=100000"
184           Max number of events to store (per type). Value is  a  comma  sepa‐
185       rated  list  of  key values, where the keys are event types (e.g.: cre‐
186       ation, oom) or "default" and  the  value  is  an  integer.  Default  is
187       applied to all non-specified event types
188
189
190       --global_housekeeping_interval=0
191           Interval between global housekeepings
192
193
194       --housekeeping_interval=0
195           Interval between container housekeepings
196
197
198       --httptest.serve=""
199           if non-empty, httptest.NewServer serves on this address and blocks
200
201
202       --insecure-skip-tls-verify=false
203           If true, the server's certificate will not be checked for validity.
204       This will make your HTTPS connections insecure
205
206
207       --kubeconfig=""
208           Path to the kubeconfig file to use for CLI requests.
209
210
211       --log-flush-frequency=0
212           Maximum number of seconds between log flushes
213
214
215       --log_backtrace_at=:0
216           when logging hits line file:N, emit a stack trace
217
218
219       --log_cadvisor_usage=false
220           Whether to log the usage of the cAdvisor container
221
222
223       --log_dir=""
224           If non-empty, write log files in this directory
225
226
227       --logtostderr=true
228           log to standard error instead of files
229
230
231       --machine_id_file="/etc/machine-id,/var/lib/dbus/machine-id"
232           Comma-separated list of files to  check  for  machine-id.  Use  the
233       first one that exists.
234
235
236       --match-server-version=false
237           Require server version to match client version
238
239
240       -n, --namespace=""
241           If present, the namespace scope for this CLI request
242
243
244       --request-timeout="0"
245           The  length  of  time  to  wait before giving up on a single server
246       request. Non-zero values should contain a corresponding time unit (e.g.
247       1s, 2m, 3h). A value of zero means don't timeout requests.
248
249
250       -s, --server=""
251           The address and port of the Kubernetes API server
252
253
254       --stderrthreshold=2
255           logs at or above this threshold go to stderr
256
257
258       --storage_driver_buffer_duration=0
259           Writes  in  the  storage driver will be buffered for this duration,
260       and committed to the non memory backends as a single transaction
261
262
263       --storage_driver_db="cadvisor"
264           database name
265
266
267       --storage_driver_host="localhost:8086"
268           database host:port
269
270
271       --storage_driver_password="root"
272           database password
273
274
275       --storage_driver_secure=false
276           use secure connection with database
277
278
279       --storage_driver_table="stats"
280           table name
281
282
283       --storage_driver_user="root"
284           database username
285
286
287       --token=""
288           Bearer token for authentication to the API server
289
290
291       --user=""
292           The name of the kubeconfig user to use
293
294
295       -v, --v=0
296           log level for V logs
297
298
299       --version=false
300           Print version information and quit
301
302
303       --vmodule=
304           comma-separated list of pattern=N settings for  file-filtered  log‐
305       ging
306
307
308

EXAMPLE

310                # Retry the latest failed deployment based on 'frontend'
311                # The deployer pod and any hook pods are deleted for the latest failed deployment
312                oc rollout retry dc/frontend
313
314
315
316

SEE ALSO

318       oc-rollout(1),
319
320
321

HISTORY

323       June 2016, Ported from the Kubernetes man-doc generator
324
325
326
327Openshift                  Openshift CLI User Manuals            OC ROLLOUT(1)
Impressum