Closed andrijaperovic closed 2 years ago
@ichi0915 @dogonthehorizon filing a ticket in this repo as well in case it needs to be tracked independently: https://github.com/spinnaker/spinnaker/issues/6679
Once I set clouddriver.sql.taskRepository
to enabled: false
the error seems to go away.
Also, looks like the CrashLoopBackOff
itself might have been linked to lack of compatibility of startupProbe
and readinessProbe
in the deployments of clouddriver & orca to k8s v1.22 (have removed those for now, I believe Armory team is looking at how these need to be addressed).
Issue Summary:
Spinnaker clouddriver fails on startup:
2022-06-23 21:43:19.462 WARN 1 --- [extShutdownHook] .s.c.a.CommonAnnotationBeanPostProcessor : Destroy method on bean with name 'operationsController' threw an exception: java.lang.IllegalArgumentException: Field (null) is not contained in Row ("task_states"."id", "task_states"."task_id", "task_states"."created_at", "task_states"."state", "task_states"."phase", "task_states"."status", "task_states"."task_id", "task_states"."created", "tasks"."id", "tasks"."request_id", "tasks"."owner_id", "tasks"."created_at", "tasks"."saga_ids")
Cloud Provider(s):
Azure (AKS v1.22.6)
Environment:
Running Spinnaker on top of AKS using OSS spinnaker operator: https://github.com/armory/spinnaker-operator/releases/tag/v1.3.0-rc.19
Feature Area:
Clouddriver
Description:
Clouddriver should boot up successfully instead of going into CrashLoopBackOff.
Steps to Reproduce:
Install
armory/spinnaker-operator
and applySpinnakerService
CRD:Additional Details:
orca also goes into CrashLoopBackOff and fiat fails because it cannot connect to clouddriver.