We are facing the same problem. Pipelines that worked minutes before stopped running with exactly the error that @yawei described.
Last time this error disappeared over night without changing anything.
I have a suspicion, that it depends on the runner. The failing pipelines/ jobs ran on x-blue.shared.runners-manager.gitlab.com
As of 17-Mar-2022, the issue magically auto recovered, maybe Gitlab found some issue in their server. But I noticed, if your runner tag is gitlab-org, which using green* server, still failing, without tag, will default use blue* server, which is fine now
Hi Vignesh,
Good day! Thanks for the feedback and we are also facing same challenge. Shall we connect to discuss on this upgradation? Let me know your availability.