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

Write event when admintools is deployed with a v24.2.0 server #714

Merged
merged 2 commits into from
Feb 22, 2024

Conversation

spilchen
Copy link
Collaborator

The v24.2.0 server image, when built for vclusterops, will not work if admintools deployment is selected. The container will fail to run. This will surface an event message if we detect this is the case. This is tied into the crashloop_reconciler.

Matt Spilchen added 2 commits February 20, 2024 19:10
The v24.2.0 server image, when built for vclusterops, will not work if
admintools deployment is selected. This will surface an event message if
we detect this is the case. This is important because the image will
fail to run if this is the case. This is tied into the crashloop_reconciler.
@spilchen spilchen self-assigned this Feb 20, 2024
Copy link
Collaborator

@roypaulin roypaulin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

func HasCreateContainerError(containerStatus *corev1.ContainerStatus) bool {
return containerStatus.State.Waiting != nil &&
containerStatus.State.Waiting.Reason == "CreateContainerError" &&
strings.Contains(containerStatus.State.Waiting.Message, "no command specified")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess there is no other reasons for CreateContainerError

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure. I was looking specifically for the 'no command specified' error. So, that should reduce the chance of this hitting other scenarios we hadn't considered.

@spilchen spilchen merged commit ee7af3a into main Feb 22, 2024
30 checks passed
@spilchen spilchen deleted the spilchen/vcluster-ops-on-24.2 branch February 22, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants