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
During successful e2e tests there should be no errors in caph logs. Otherwise debugging failing e2e tests is harder, because you need to check if an error is a common error or a real error.
For example this is common, and should not be an error:
level: ERRORtime: "2025-04-02T14:15:09.777Z"file: controller/controller.go:324message: Reconciler errorcontroller: hetznerbaremetalhostcontrollerGroup: infrastructure.cluster.x-k8s.iocontrollerKind: HetznerBareMetalHostHetznerBareMetalHost:
name: bm-e2e-1670788namespace: ci14221626200-6nzn0mnamespace: ci14221626200-6nzn0mname: bm-e2e-1670788reconcileID: 4bac613e-5303-40dd-b5c3-d8ebed6b708eerror: 'failed to reconcile HetznerBareMetalHost ci14221626200-6nzn0m/bm-e2e-1670788: action "ensure-provisioned" failed: failed to get cloud init output: failed to dial ssh. Error message: dial tcp 136.243.69.167:22: connect: connection refused. DialErr: failed to dial ssh, while handling: failed to get cloud init status: failed to dial ssh. Error message: dial tcp 136.243.69.167:22: connect: connection refused. DialErr: failed to dial ssh'stacktrace: |- sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:324 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:261 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:222
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
/kind feature
During successful e2e tests there should be no errors in caph logs. Otherwise debugging failing e2e tests is harder, because you need to check if an error is a common error or a real error.
For example this is common, and should not be an error:
The text was updated successfully, but these errors were encountered: