summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging/meta
diff options
context:
space:
mode:
authorSteve Kuznetsov <skuznets@redhat.com>2017-06-12 10:36:41 -0700
committerSteve Kuznetsov <skuznets@redhat.com>2017-06-13 11:50:47 -0700
commitacb78312d18c27f607ad71898fcc6bacab4b5cb6 (patch)
treef92ec238ccef4c83c93c15f3127e544aa4081ee3 /roles/openshift_logging/meta
parent9ba4195cb4c70705c4cec2543617738b8e114148 (diff)
downloadopenshift-acb78312d18c27f607ad71898fcc6bacab4b5cb6.tar.gz
openshift-acb78312d18c27f607ad71898fcc6bacab4b5cb6.tar.bz2
openshift-acb78312d18c27f607ad71898fcc6bacab4b5cb6.tar.xz
openshift-acb78312d18c27f607ad71898fcc6bacab4b5cb6.zip
Make rollout status check best-effort, add poll
We cannot rely on the `watch.Until` call in the `rollout status` subcommand for the time being, so we need to ignore the result of this call. This will make the rollout status check best-effort, so we need to follow it with a poll for the actual status of the rollout, which we can extract from the `openshift.io/deployment.phase` annotation on the ReplicationControllers. This annotation can have only three values -- `Running`, `Complete` and `Failed`. If we poll on this attribute until we stop seeing `Running`, we can then inspect the last result for `Failed`; if it's present, we have failed the deployment. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Diffstat (limited to 'roles/openshift_logging/meta')
0 files changed, 0 insertions, 0 deletions