-
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
🐛 pass the cluster in to the get targets #4367
Conversation
/test ls |
@nader-ziada: The specified target(s) for
Use
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. |
/test pull-cluster-api-e2e-full-main |
var cluster clusterv1.Cluster | ||
if err := clusterClient.Get(ctx, client.ObjectKey{Namespace: mhc.Namespace, Name: mhc.Spec.ClusterName}, &cluster); err != nil { | ||
return nil, errors.Wrapf(err, "error getting Cluster %s/%s for MachineHealthCheck %s", mhc.Namespace, mhc.Spec.ClusterName, mhc.Name) | ||
} |
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.
Shouldn't this client be r.Client
and not the target Cluster client?
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.
Regardless of this, +1 passing the object in if we already have it
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.
Not sure if I got it correctly:
- the issue was that we were trying to get the cluster from the target cluster instead of the management cluster
- but we still need the clusterClient (as target cluster client) in l.211
/retest |
/test pull-cluster-api-e2e-full-main |
test/e2e/kcp_adoption.go
Outdated
@@ -52,7 +52,7 @@ type KCPAdoptionSpecInput struct { | |||
type ClusterProxy interface { | |||
framework.ClusterProxy | |||
|
|||
ApplyWithArgs(context.Context, []byte, ...string) error | |||
Apply(context.Context, []byte, ...string) error |
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.
This change seems to be unrelated, was it intended?
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.
a previous PR changed this, so was getting a panic, check Fabrizio comment above
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.
Ah I see it now, didn't see the the connection the first time.
the e2e tests all passed, once #4371 merges, will rebase and this will be good to go |
/test pull-cluster-api-e2e-full-main |
/lgtm |
failed on a time out, will try again /test pull-cluster-api-e2e-full-main |
Probably just stating the obvious but: E0324 20:21:46.852841 1 controller.go:302] controller-runtime/manager/controller/dockermachine "msg"="Reconciler error" "error"="failed to create worker DockerMachine: timed out waiting for the condition" "name"="k8s-conformance-nu20ky-md-0-njj9v" "namespace"="k8s-conformance-23gfsn" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="DockerMachine"
I0324 20:21:48.423611 1 machine.go:357] controller-runtime/manager/controller/dockermachine "msg"="Setting Kubernetes node providerID" "name"="machine-pool-3h8bin-control-plane-q6gcw" "namespace"="machine-pool-2t0lry" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="DockerMachine"
I0324 20:21:49.146323 1 machine.go:312] controller-runtime/manager/controller/dockermachine "msg"="Failed running command" "name"="k8s-conformance-nu20ky-md-0-njj9v" "namespace"="k8s-conformance-23gfsn" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="DockerMachine" "bootstrap data"="<user-data>==" "command"={"Cmd":"mkdir","Args":["-p","/run/kubeadm"],"Stdin":""} "stderr"="Error response from daemon: Container 317b0f95e3f6073f59a914837e124548924b45abd0545e909c2b68fc3f47318f is not running\n" "stdout"="" I'm not that familiar (yet) with CAPD and its e2e test but looks to me like we don't have enough logs (at the moment) to find out why we get those timeouts. /test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
@CecileRobertMichon ready for a a look |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4361