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.

Sign up for GitHub

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

Jump to bottom

iamauth controller failing to reconcile due to informer issue #5128

Open
alam0rt opened this issue Sep 25, 2024 · 2 comments · May be fixed by #5200
Open

iamauth controller failing to reconcile due to informer issue #5128

alam0rt opened this issue Sep 25, 2024 · 2 comments · May be fixed by #5200
Assignees
@aniruddha2000
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@alam0rt
Copy link
Contributor

alam0rt commented Sep 25, 2024

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

The capa client-go is failing to list v1beta1.MachineDeployments which is in turn causing the iamauth controller to error out before it can reconcile.

  - lastTransitionTime: "2024-09-06T04:09:56Z"
    message: 'getting roles for remote workers: failed to get roles from machine deployments
      failed to list machine deployments for cluster default/manager: Timeout: failed
      waiting for *v1beta1.MachineDeployment Informer to sync'
    reason: IAMAuthenticatorConfigurationFailed

The cluster in question does not use any machine deployments (its an EKS fargate cluster).

What did you expect to happen:

For the iamauth controller to get an empty list of machine deployments and continue reconciliation.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Appears to be occurring here:

cluster-api-provider-aws/pkg/cloud/services/iamauth/reconcile.go

Lines 125 to 128 in c2c96dd

err := s.client.List(ctx, deploymentList, selectors...)
if err != nil {
return fmt.Errorf("failed to list machine deployments for cluster %s/%s: %w", s.scope.Namespace(), s.scope.Name(), err)
}

Environment:

  • Cluster-api-provider-aws version: v2.5.0
  • Kubernetes version: (use kubectl version): v1.30.3-eks-a18cd3a
  • OS (e.g. from /etc/os-release): Fargate / bottlerocket
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 25, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

@aniruddha2000
Copy link

/assign

@aniruddha2000 aniruddha2000 linked a pull request Nov 3, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aniruddha2000 aniruddha2000

Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🐛 Ignore informer sync error aniruddha2000/cluster-api-provider-aws
3 participants
@k8s-ci-robot @alam0rt @aniruddha2000