berops
Bug: Fail to unmarshal kubeadm config map after kube-eleven
Current Behaviour
Rarely in the e2e tests it happens that after the cluster is build in the kube-eleven step, kuber fails to unmarshal the kubeadm flag.
Expected Behaviour
This step should not fail, we should figure out what might be causing this, or we a simple retry does the trick.
Steps To Reproduce
Rarely happens on the e2e pipeline. Don't know how to reproduce.
Anything else to note
error-msg: 2025-03-11T15:40:13Z ERR claudie_test.go:138 > Error in test sets test-set2 error="error while monitoring manifest 1.yaml from test set test-set2: ----\nerror in cluster ts2-htz-cluster-test-set-no2\n----\nStage: KUBER \n State: ERROR\n Description: error in Kuber for cluster ts2-htz-cluster-test-set-no2 project claudie-715f514-3284-test-set2 : rpc error: code = Unknown desc = failed to unmarshal kubeadm-config cluster map, malformed yaml: yaml: mapping values are not allowed in this context" module=testing-framework
