search

medic / upgrade-service-kubernetes

Upgrade service for k8s
0 stars 0 forks source link

Cannot install a new build of the same branch #17

Open dianabarsan opened 2 days ago

dianabarsan commented 2 days ago

We have an ESK instance with a branch deployed. This instance can upgrade between releases 4.X.X, and between different branches without a problem.

When upgrading to the same branch but a different build, it keeps installing the old build and shows no errors

https://care-teams-demo.dev.medicmobile.org/admin/#/upgrade is in 4.11.0-9327-update-nav.10714293548 (old build)

The CI published the new branch:

Publishing doc...
medic:medic:9327-update-nav published!
regctl image copy 720541322708.dkr.ecr.eu-west-2.amazonaws.com/medic/cht-api:4.11.0-9327-update-nav.10815901430 public.ecr.aws/medic/cht-api:4.11.0-9327-update-nav
public.ecr.aws/medic/cht-api:4.11.0-9327-update-nav

This build is in the staging server: Screenshot 2024-09-12 at 4 45 24 PM

Originally submitted on https://github.com/medic/cht-upgrade-service/issues/44

dianabarsan commented 2 days ago

I'm suspecting that K8s is not pulling the image, when the tag is the same. Some discussions here: https://stackoverflow.com/questions/33112789/how-do-i-force-kubernetes-to-re-pull-an-image