Update "Stack" failed about stack-lifecycle-deployment HOT 16 CLOSED

@ramazulay
I have released a fix, please update to d10s0vsky/sld-dashboard:tagname:2.4.1
regards

from stack-lifecycle-deployment.

Hi @ramazulay ,
Please, could you tell me what version of SLD are you using?
Regards,

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS,
The version is d10s0vsky/sld-dashboard:2.3.0 and d10s0vsky/sld-api:2.3.0.
After your updated the tfvar_file here.https://github.com/D10S0VSkY-OSS/Stack-Lifecycle-Deployment/discussions/62

from stack-lifecycle-deployment.

Hi @ramazulay
please try to update to version d10s0vsky/sld-api:2.5.0 and d10s0vsky/sld-dashboard:2.4.0.
Just note that there is a bracking change that adds another field to the "stack_branch" database that allows you to specify an individual branch for each deploy.
Try add the field

ALTER TABLE deploy ADD stack_branch varchar(100) NULL AFTER stack_name;

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS,
I have updated as you requested.(of course i did rollout restart)
I run the ALTER command also.(of course i did rollout restart)
The Sync still failed.

Log from sld-dashboard:
[2022-07-11 10:23:31 +0200] [1] [CRITICAL] WORKER TIMEOUT (pid:11)
[2022-07-11 10:23:31 +0200] [11] [INFO] Worker exiting (pid: 11)
[2022-07-11 10:23:31 +0200] [1] [CRITICAL] WORKER TIMEOUT (pid:13)
[2022-07-11 10:23:31 +0200] [13] [INFO] Worker exiting (pid: 13)
[2022-07-11 10:23:31 +0200] [14] [INFO] Booting worker with pid: 14
[2022-07-11 10:23:31 +0200] [1] [WARNING] Worker with pid 13 was terminated due to signal 9
[2022-07-11 10:23:31 +0200] [15] [INFO] Booting worker with pid: 15
[2022-07-11 10:24:02 +0200] [1] [CRITICAL] WORKER TIMEOUT (pid:12)

from stack-lifecycle-deployment.

Hi @ramazulay
please, check that the workers use the docker image d10s0vsky/sld-api:2.5.0 too.
Regards

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS ,
Didn't help.
Do you have any idea?

Thanks.

from stack-lifecycle-deployment.

When I edit the deploy I got:

Very strange.

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS,
I reinstalled the sld on another ns and I have seeing the same issue(Update/create/sync stuck "Stack")
Thanks.

from stack-lifecycle-deployment.

Hi @ramazulay ,
please, Coud you send me the output next command:

kubectl get pods --all-namespaces -o jsonpath="{.items[*].spec.containers[*].image}" |\
tr -s '[[:space:]]' '\n' |\
sort |\
uniq -c|grep d10s

from stack-lifecycle-deployment.

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS,
Thanks for your replay.
The output command:

tr -s '[[:space:]]' '\n' |
sort |
uniq -c|grep d10s
2 d10s0vsky/sld-api:2.5.0
1 d10s0vsky/sld-dashboard:2.4.1
1 d10s0vsky/sld-remote-state:1.0.2
1 d10s0vsky/sld-schedule:latest

Thanks.

from stack-lifecycle-deployment.

@ramazulay
apparently you have everything correct, unfortunately I am not able to reproduce your problem.
Have you tried with a completely new database?
Regards,

from stack-lifecycle-deployment.

Hi @D10S0VSkY-OSS,
Yes, I`ve deleted the PVC and redeployed the DB.
I also reverted to the latest version, but without success.

What do you recommend to do?

from stack-lifecycle-deployment.

@ramazulay,
If you can, send me a schedule meet to my email and we try to solve it in a meet.
please, remember that I live in Spain Central European Time (CET), UTC +1
Regars

from stack-lifecycle-deployment.

After having a meet with @ramazulay we have been able to see that the worker default was missing, in charge of generating the stack

from stack-lifecycle-deployment.