Closed mattf closed 5 years ago
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
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
@soltysh my best guess is that the error "timed out waiting for condition" is occurring while waiting for the pod to be created: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/run.go#L341
We could probably place the "remove" logic in a separate function, then do a defer call on it here: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/run.go#L299 after we have a list of created objects to delete. This way, we ensure we delete all objects beyond this point, should an error happen. Thoughts?
Yeah, that makes sense, go for it.
/remove-lifecycle rotten
Upstream PR: https://github.com/kubernetes/kubernetes/pull/62482
Upstream PR has merged, will be fixed in Origin in next rebase
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
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
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
@openshift-bot: Closing this issue.
dc, rc and po remain after 'oc run --rm' exits (via error)
Version
Steps To Reproduce
Current Result
Expected Result
'oc run --rm' isn't running, so no resources
Additional Information
some events on the pod...