faint-smartphone-23356
07/18/2023, 6:22 PMflyte [1.218ms] [rows:1] SELECT count(*) FROM pg_indexes WHERE tablename = 'artifacts' AND indexname = 'artifacts_dataset_uuid_idx' AND schemaname = CURRENT_SCHEMA() flyte 2023/07/18 18:19:44 /go/pkg/mod/gorm.io/gorm@v1.24.1-0.20221019064659-5dd2bb482755/callbacks.go:134 ERROR: duplicate key value violates unique constraint "executions_pkey" (SQLSTATE 23505)
any suggestions on how to fix this? A failed update to flyte-binary 1.8.0 and a rollback to flyte-binary 1.6.2 seems to have left our system in a broken state.microscopic-furniture-57275
07/18/2023, 7:08 PM~ kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> informatics-001-install updating (6s) [diff: ~resourceNames,version]; error: 1 error occurred:
~ kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> informatics-001-install **updating failed** [diff: ~resourceNames,version]; error: 1 error occurred:
pulumi:pulumi:Stack flyte-informatics-001 running error: update failed
pulumi:pulumi:Stack flyte-informatics-001 **failed** 1 error
Diagnostics:
kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (informatics-001-install):
error: 1 error occurred:
* Helm release "flyte/flyte" failed to initialize completely. Use Helm CLI to investigate.: failed to become available within allocated timeout. Error: Helm Release flyte/flyte: cannot patch "flyte-flyte-binary" with kind Deployment: Deployment.apps "flyte-flyte-binary" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"<http://app.kubernetes.io/component|app.kubernetes.io/component>":"flyte-binary", "<http://app.kubernetes.io/instance|app.kubernetes.io/instance>":"flyte", "<http://app.kubernetes.io/name|app.kubernetes.io/name>":"flyte-binary"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
pulumi:pulumi:Stack (flyte-informatics-001):
error: update failed
faint-smartphone-23356
07/18/2023, 8:36 PMfaint-smartphone-23356
07/18/2023, 8:36 PMthankful-minister-83577
executions_pkey
is the primary key of the executions table. the constraint is (execution_project, execution_domain, execution_name)thankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:41 PMfaint-smartphone-23356
07/18/2023, 9:42 PMfaint-smartphone-23356
07/18/2023, 9:42 PMthankful-minister-83577
thankful-minister-83577
thankful-minister-83577
thankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:43 PMfaint-smartphone-23356
07/18/2023, 9:43 PMthankful-minister-83577
thankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:46 PMfaint-smartphone-23356
07/18/2023, 9:46 PMthankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:46 PMthankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:48 PM[]
=> nil
for some reason? or vis-a-versa ?faint-smartphone-23356
07/18/2023, 9:51 PMthankful-minister-83577
faint-smartphone-23356
07/18/2023, 9:52 PMfaint-smartphone-23356
07/18/2023, 9:53 PMfaint-smartphone-23356
07/18/2023, 9:55 PMfreezing-boots-56761
freezing-boots-56761
freezing-boots-56761
microscopic-furniture-57275
07/19/2023, 1:41 PMfaint-smartphone-23356
07/19/2023, 4:09 PMmillions-table-8574
10/03/2023, 9:40 AMhelm upgrade
again but we’re still seeing issues with the readiness probe failingfreezing-boots-56761
helm upgrade
and the deployment came up with the correct selectors, its a different issue i thinkfreezing-boots-56761