Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

TestReconcile_LicenseRotationUploadsNewSecretValue fails at -count=3 (reuses a control plane name)

Open Beginner friendly
  • Is something wrong?
#320 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, kubernetes
Domain
testing

Research direction

The failing test is TestReconcile_LicenseRotationUploadsNewSecretValue at line 895 of internal/controller/codercontrolplane_controller_test.go. Start by reading how it names its CoderControlPlane and how its cleanup removes that object in envtest. Reproduce with GOFLAGS=-mod=vendor go test ./internal/controller/ -run 'TestReconcile_LicenseRotationUploadsNewSecretValue$' -count=3. Done means the repeated run passes, and the name or wait-for-deletion fix should not change the test's assertions.

Written by the indexing model from the issue text.

Description

Summary

TestReconcile_LicenseRotationUploadsNewSecretValue (internal/controller/codercontrolplane_controller_test.go:895) fails when run with -count=3. It reuses a fixed CoderControlPlane name, and a later run starts before envtest has removed the object from the earlier run.

Reproduce

GOFLAGS=-mod=vendor go test ./internal/controller/ -run 'TestReconcile_LicenseRotationUploadsNewSecretValue$' -count=3

The #156 worker reported this while it ran repeated tests for #316. I did not reproduce it myself.

Fix

Give each run a unique name (for example a suffix from t.Name() plus a counter or random string), or wait until the object is gone in cleanup. CI runs each test once, so CI is not affected today.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: medium

Dominant language
Go
Stars
5
Forks
3
Avg merge
2h 56m
Merged PRs (30d)
163

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/coder-k8s

All issues in coder/coder-k8s

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.