This morning I upgraded gitlab ce from version 17.3.3 to 17.4.1 (upgrade done with helm chart 8.4.1) but after the upgrade 17.4.1 (latest release released) gives me the message “upgrade Asap”. I ask if it is a bug?
1 Like
I think I’m in the same case. After upgrade gitlab-ce from 17.3.4 to 17.4.1 I see the message “Components updateASAP”, but there are no remaining updates. ¿It’s a bug? ¿Can I ignore It?
Regards
1 Like
I got three Gitlab servers, one on RHEL distro, two on Debian. RHEL one shows the same as you, and also one of my Debian ones does too. The other Debian does not show it.
I have tried refreshing Redis, and browser cache, so it does seem to be an issue somewhere where it’s cached and not refreshed. It could well be that another update 17.4.2 is due if it doesn’t clear, so just have to wait and see.
Temporarily using:
gitlab-rake clear:cache
will remove it, but it then most likely connects to Gitlab servers and then displays it again. Would suggest a new update is coming.
Thanks for your comments. I think I’ll wait for the next upgrade too (I think it’ll come soon) 
I had this same problem when my container wasn’t being rebuilt with the new upgraded image. Maybe something to check out but from other responses could also be a bug / update pending soon.
gitlab-rake not installed in my company, self-hosted free edition
https://gitlab.COMPANY.es/MYGROUP/devops/resources/test-netcore/-/pipelines
Same here on a self-hosted debian 12, upgrade was from 17.4 to 17.4.1 .
Pierre.
I just re-ran this now:
it now shows correctly instead of showing Upgrade ASAP. Seems they refreshed something with the server our instances connect to, to check/verify update information.
Might be unrelated, but if anyone finds this thread down the line, i had this in my values.yaml
gitlabVersion: 17.3.1
Removing it makes helm release to use chart version for proper update.
I am getting the same “upgrade asap” message. But I want to know the real reason on via an upgrade is required. I need to ensure minimum disruption to the development team, and hence have to reschedule upgrades to after hour times, which screws up my personal work-life balance. I cannot be performing upgrades every week. Is there a way to find out the criticality of an upgrade from current version to latest version?
Yeah, read the info here: Releases | GitLab