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

Successful containers should not overwrite Failed phase set by former containers #303

Open
landerlini opened this issue Oct 17, 2024 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@landerlini
Copy link

landerlini commented Oct 17, 2024

case podCompleted && podRefInCluster.Status.Phase != v1.PodSucceeded:
podRefInCluster.Status.Conditions = append(podRefInCluster.Status.Conditions, v1.PodCondition{Type: v1.PodReady, Status: v1.ConditionFalse})
podRefInCluster.Status.Phase = v1.PodSucceeded
podRefInCluster.Status.Reason = "Completed"

In multicontainer pods, if a container fails, the pod phase should be set to "Failed".

Instead, the last container in the container status is granted the right to revert a "Failed" status to "Succeeded".

landerlini pushed a commit to landerlini/interlink-condorce-plugin that referenced this issue Oct 17, 2024
@dciangot dciangot added the bug Something isn't working label Nov 12, 2024
@dciangot dciangot added this to the 0.4.x milestone Nov 12, 2024
@dciangot dciangot self-assigned this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants