-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Labels
Description
Problem statement
TestEnvironmentWithRegistryAddon
is failing in CI
This task tracks fixing it
registry_test.go:27: configuring the testing environment
registry_test.go:35: building the testing environment and Kubernetes cluster
W0805 14:50:06.608074 2951 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
W0805 14:50:47.201088 2951 warnings.go:70] spec.privateKey.rotationPolicy: In cert-manager >= v1.18.0, the default value changed from `Never` to `Always`.
registry_test.go:39: setting up the environment cleanup for environment 9c0e38f5-f0dd-45cf-a5fb-948ab2b9fc5c and cluster 9c0e38f5-f0dd-45cf-a5fb-948ab2b9fc5c
registry_test.go:45: verifying that addons have been loaded into the environment
registry_test.go:48: waiting for the test environment to be ready for use
registry_test.go:51: verifying the test environment becomes ready for use
registry_test.go:57: verifying that the addon was set up properly
registry_test.go:61: creating a job to push an httpbin image to the registry
registry_test.go:68: starting the podman image push job
registry_test.go:74: waiting for podman image push job to complete
registry_test.go:81: creating a deployment using the image from the custom registry
registry_test.go:95: verify that the container image can be pulled and the pod starts
registry_test.go:96:
Error Trace: /home/runner/work/kubernetes-testing-framework/kubernetes-testing-framework/test/integration/registry_test.go:96
Error: Condition never satisfied
Test: TestEnvironmentWithRegistryAddon
registry_test.go:41: cleaning up environment 9c0e38f5-f0dd-45cf-a5fb-948ab2b9fc5c and cluster 9c0e38f5-f0dd-45cf-a5fb-948ab2b9fc5c
--- FAIL: TestEnvironmentWithRegistryAddon (309.20s)
FAIL
coverage: 26.3% of statements in ./pkg/..., ./internal/...