You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
=== NAME TestHarnessRunIntegrationWithConfig/harness/crd-in-step
logger.go:42: 07:33:41 | crd-in-step/0-crd | test step completed 0-crd
logger.go:42: 07:33:41 | crd-in-step/1-create-mycrd | starting test step 1-create-mycrd
=== NAME TestHarnessRunIntegrationWithConfig/harness/teststep-assert
logger.go:42: 07:33:41 | teststep-assert/0-create | starting test step 0-create
=== NAME TestHarnessRunIntegrationWithConfig/harness/crd-in-step
case.go:366: failed in step 1-create-mycrd
case.go:368: retrieving API resource for mycrd.example.com/v1beta1, Kind=MyCRD failed: the server could not find the requested resource
logger.go:42: 07:33:41 | crd-in-step | crd-in-step events from ns kuttl-test-civil-barnacle:
What you expected to happen:
Since step 0-crd does wait for the CRD to be established, and kuttl does not seem to be using a cached discovery client, the error from API server when trying to create a CR is unexpected, especially in an unreplicated API server environment.
It would be useful to see API server audit log to know what exactly happened.
How to reproduce it (as minimally and precisely as possible):
What happened:
https://github.com/kudobuilder/kuttl/actions/runs/8277018028/job/22646568404
What you expected to happen:
Since step
0-crd
does wait for the CRD to be established, and kuttl does not seem to be using a cached discovery client, the error from API server when trying to create a CR is unexpected, especially in an unreplicated API server environment.It would be useful to see API server audit log to know what exactly happened.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
This was in CI on this commit.
The text was updated successfully, but these errors were encountered: