Overview
We are introducing checking the logs to confirm whether it is successfully completed to upgrade the Server 4.3.x;
Ensure that your CircleCI server v4.3 installation is left running until after the migration has completed. You can confirm that the migration has completed by checking the logs of workflows-conductor-event-consumer. There will be a starting next-build-seq-migration log message with project_count=0
Steps to check
You can check the logs from the workflows-conductor-event-consumer pods by running the following command:
kubectl logs workflows-conductor-event-consumer-<hash-id> -c dbcreator -n <namespace>
The sample log looks like below:
2024-06-05T22:01:21.104+0000 [] [pool-27-thread-2] INFO workflows-conductor.background-jobs.ensure-job-numbers-migrated starting next-build-seq-migration; batch-size=1000; canary=false; deploy-environment=production; hostname=workflows-conductor-event-consumer-769fcbf796-p8465; k8s-pod-name=workflows-conductor-event-consumer-769fcbf796-p8465; k8s-pod-namespace=circleci-server; k8s-replicaset=workflows-conductor-event-consumer-769fcbf796; project-count=0; revision=xxx; service=workflows-conductor; span-id=xxx; started-at=2024-06-05T22:01:21.104Z; trace-id=xxx; version=1.0.19762-9c3b994