Skip to content

Conversation

@dlipovetsky
Copy link
Contributor

What type of PR is this?
/kind bug

What this PR does / why we need it:

This fixes a nil dereference that causes the controller to panic.

The PR has two commits. The first commit adds a (failing) test that reproduces the issue. The second commit fixes the issue.

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 #

Special notes for your reviewer:

Checklist:

  • squashed commits
  • includes documentation
  • includes emoji in title
  • adds unit tests
  • adds or updates e2e tests

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. labels Dec 8, 2025
@k8s-ci-robot k8s-ci-robot requested a review from AndiDog December 8, 2025 18:02
@k8s-ci-robot k8s-ci-robot requested a review from faiq December 8, 2025 18:02
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 8, 2025
@faiq
Copy link
Contributor

faiq commented Dec 8, 2025

/lgtm

im not sure what the lint error is about. thanks for adding unit tests too!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 8, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 154ea1edcd84dbdbc0a733d218c38a67985dbf87

@dlipovetsky
Copy link
Contributor Author

/lgtm

im not sure what the lint error is about. thanks for adding unit tests too!

Last time lint check passed was https://github.com/kubernetes-sigs/cluster-api-provider-aws/actions/runs/19889397833/job/57004172122#step:6:10. It's been failing with the same error since:

Error: build process: clone golangci-lint: git clone --branch v2.1.0 --single-branch --depth 1 -c advice.detachedHead=false -q https://github.com/golangci/golangci-lint.git: exit status 128
Failed executing command with error: build process: clone golangci-lint: git clone --branch v2.1.0 --single-branch --depth 1 -c advice.detachedHead=false -q https://github.com/golangci/golangci-lint.git: exit status 128
make: *** [Makefile:310: /home/runner/work/cluster-api-provider-aws/cluster-api-provider-aws/hack/tools/bin/golangci-lint-kube-api-linter] Error 3

@dlipovetsky
Copy link
Contributor Author

dlipovetsky commented Dec 8, 2025

I've identified the lint problem. It's golangci/golangci-lint#5641. We bumped Go version ahead of the Go version used to build golangci-lint in #5782.

We'll need to bump golangci-lint to one built with Go 1.24.x. I'll file a PR.

(At least this is my working theory--I'll need to confirm it 😅 )

Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

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

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 9, 2025
@damdo
Copy link
Member

damdo commented Dec 9, 2025

/hold

Until linitng is fixed

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants