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.

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

fix flaky lib/auth cache-enabled tests #36216

Merged
merged 3 commits into from
Jan 3, 2024
Merged

Conversation

GavinFrazar
Copy link
Contributor

Fixes flaky cache-enabled lib/auth tests, namely the TestListUnifiedResources_* tests (those are the only ones with cache enabled).

I was debugging an unrelated change locally and noticed sporadic failures in these test cases, for example:

=== Failed
=== FAIL: lib/auth TestListUnifiedResources_WithSearch (0.03s)
    tls_test.go:4610: 
                Error Trace:    /Users/gavin/work/teleport/lib/auth/tls_test.go:461
0
                                                        /Users/gavin/work/teleport/
lib/auth/auth_with_roles_test.go:4451
                Error:          Received unexpected error:
                                cluster name not found
                Test:           TestListUnifiedResources_WithSearch

The fix is to start the test auth server's cache after config resources like cluster name are all initialized, the same as we do in lib/service/service.go:initAuthService for the real implementation.

We only enabled cache in these tests since v14 in this PR, so that's as far as I'll backport.

@GavinFrazar GavinFrazar added flaky tests backport/branch/v14 no-changelog Indicates that a PR does not require a changelog entry labels Jan 2, 2024
@GavinFrazar GavinFrazar changed the title fix flaky lib/auth cache-enabled tests fix flaky lib/auth cache-enabled tests Jan 2, 2024
GavinFrazar added a commit that referenced this pull request Jan 2, 2024
@GavinFrazar GavinFrazar added this pull request to the merge queue Jan 3, 2024
Merged via the queue into master with commit 14bada2 Jan 3, 2024
33 checks passed
@GavinFrazar GavinFrazar deleted the gavinfrazar/fix-flaky-tests branch January 3, 2024 20:37
@public-teleport-github-review-bot

@GavinFrazar See the table below for backport results.

Branch Result
branch/v14 Create PR

Envek added a commit to Envek/teleport that referenced this pull request Jan 4, 2024
…se-anon-key

* origin/master: (344 commits)
  Undelete CreateHostUserMode_HOST_USER_MODE_DROP (gravitational#36273)
  allow cwd to be changed in difftest (gravitational#35946)
  Auth device list component (gravitational#36235)
  make unified resources responsive (gravitational#35961)
  Support running Teleport in a "hot reload" mode (gravitational#35040)
  Prevent deleting enum values, allow deleting enum reservations in types.proto (gravitational#36248)
  Remove support for legacy (Amazon Linux 2) AMIs (gravitational#36153)
  Bump version(s) used for teleport-lab and teleport-quickstart (gravitational#36167)
  Allow Reconciler update handler to examine old value during update (gravitational#36171)
  Validate the user still exists during account reset (gravitational#35676)
  ButtonTextWithAddIcon shared component (gravitational#36103)
  Refactor hostname resolution for SSH connections via the WebUI (gravitational#35773)
  add structuredClone to jest JSDOMEnvironment (gravitational#36213)
  fix flaky `lib/auth` cache-enabled tests (gravitational#36216)
  Report resource usage counts by handling heartbeat events (gravitational#35968)
  Reviewer bot should use the stable version of Go (gravitational#36242)
  RFD 0153 Resource Guidelines (gravitational#34103)
  Use cmp and cmpots properly in operator tests (gravitational#36215)
  Relax Kubernetes CRD discovery when building cache (gravitational#36214)
  Add Access List messages to TAG protobuf (gravitational#36176)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/branch/v14 flaky tests no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants