-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[WIP] 🌱 capd: inspect container when container bootstrap fails #4416
[WIP] 🌱 capd: inspect container when container bootstrap fails #4416
Conversation
Let's try to hit the issue and find out if the docker inspect works and helps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this within the PR for adding more info to the logs, so we can cross check the problem in logs as well
@@ -431,3 +435,12 @@ func (m *Machine) machineImage(version *string) string { | |||
|
|||
return fmt.Sprintf("%s:%s", defaultImageName, versionString) | |||
} | |||
|
|||
func logInspectContainer(ctx context.Context, log logr.Logger, name string) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit
If you passing ctx you can use log := ctrl.LoggerFrom(ctx)
(no need to pass the logger)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Is the pattern in general to just pass the context and always get the logger from there? (in cases where we have to pass the context anyway, which is probably almost everywhere)
How do you mean this? The logger itself should have and print the name and namespace of the machine afaik. But I think you're referring to something else. Of course open to all suggestions I'm not familiar with the code at all :) |
That wasn't the error I was looking for :) (will be fixed in #4415) |
/test pull-cluster-api-e2e-full-main |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I hit the issue, unfortunately there was nothing conclusive in the docker inspect output: https://gist.github.com/sbueringer/581a793084fd129d97816b8529ecdc81 Cherry-picked #4414 for now, maybe that helps /test pull-cluster-api-e2e-full-main |
Just realized that I can also just find the root cause on this PR with a few test runs. I'll play around a bit, let's discuss afterwards which of the changes we consider merging into the main branch. For now: added docker logs /test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
7 similar comments
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
1 similar comment
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
1 similar comment
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
3 similar comments
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
Now with a new kind image which uses /test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
f0e7a5a
to
0d74d6d
Compare
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-main |
@sbueringer: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
I'll close this PR as it served it's purpose (and found an issue in kind). I'll open a new (clean) one for the addition of docker inspect/logs. |
@sbueringer: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
Adds more debug information in case the container creation does not work. For context, please see #4405 (comment)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Improves observability to debug #4405