Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc status warning in case of automatic deployment rollbacks #8416

Open
0xmichalis opened this issue Apr 8, 2016 · 7 comments
Open

oc status warning in case of automatic deployment rollbacks #8416

0xmichalis opened this issue Apr 8, 2016 · 7 comments
Labels
component/apps component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2 sig/master

Comments

@0xmichalis
Copy link
Contributor

Having a deployment config running with its latest state being failed should be a warning in my opinion.
"dc/foo is running via an older deployment" and suggest to inspect the latest failure.

@0xmichalis
Copy link
Contributor Author

We should suggest oc logs pod/deployer

@0xmichalis
Copy link
Contributor Author

We should also start emitting events when an automatic rollback happens but that's probably a separate issue.

@0xmichalis 0xmichalis assigned tnozicka and unassigned 0xmichalis Jun 25, 2017
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 16, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@tnozicka
Copy link
Contributor

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 16, 2018
@0xmichalis 0xmichalis removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 25, 2018
@0xmichalis
Copy link
Contributor Author

/sig master

@tnozicka tnozicka removed their assignment Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apps component/cli lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2 sig/master
Projects
None yet
Development

No branches or pull requests

7 participants