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
When running kas-installer.sh installation is stuck in the step Waiting until KAS Fleet Manager Deployment is available... with kas-fleet-manager pod on CrashLoopBackOff state. This is the error logs from the pod:
I1210 14:17:23.280718 1 environment.go:108] Initializing development environment
E1210 14:17:23.281175 1 environment.go:119] unable to read configuration files: yaml: unmarshal errors:
line 1: cannot unmarshal !!seq into config.InstanceTypeMap
F1210 14:17:23.281191 1 cmd.go:21] Unable to initialize environment: unable to read configuration files: yaml: unmarshal errors:
line 1: cannot unmarshal !!seq into config.InstanceTypeMap
@MikeEdgar Also seeing this error during performance test pipeline run 13th December. I1213 11:18:54.261404 1 environment.go:108] Initializing development environment E1213 11:18:54.261888 1 environment.go:119] unable to read configuration files: yaml: unmarshal errors: line 1: cannot unmarshal !!seq into config.InstanceTypeMap F1213 11:18:54.261904 1 cmd.go:21] Unable to initialize environment: unable to read configuration files: yaml: unmarshal errors: line 1: cannot unmarshal !!seq into config.InstanceTypeMap
When running
kas-installer.sh
installation is stuck in the stepWaiting until KAS Fleet Manager Deployment is available...
withkas-fleet-manager
pod onCrashLoopBackOff
state. This is the error logs from the pod:Tested with the latest commit on december 8th.
kas-installer execution log from Jenkins: https://ci.int.devshift.net/job/managed-kafka-fault-tests-nightly/78/console
The text was updated successfully, but these errors were encountered: