The gcc log shows the below:
It is implying a no version difference. But also that the Upgrade is not available.
Thoughts?
I faced this issue recently, all the source connections were failing.
We did VA reboot, then it completed the upgrade. See if that helps.
Thanks
Krish
1 Like
Hi @ts_fpatterson,
I have a case currently open with support on a similar issue.
The issue started when we noticed that the IQService in our two non-production tenants was not automatically updating. After working with support, we found that the newest IQService build zip file wasn’t available on either VA, which is how the update service on the IQService box knows whether or not to upgrade.
I noticed in the CLI documentation that there is a sail va update command available. I’m not exactly sure what all this update encompasses, but this updated the CCG version on the VA, and we then noticed the newest IQService build was then on the VA box.
The update service on the IQService box eventually picked this up, and updated to the latest version.
Now, as to what is supposed to prompt VAs to update, what is the latest available version, or what even is the difference between a VA CCG version or a cluster CCG version? I have no idea.
2 Likes
According to sailpoint-cli/cmd/va/commands.go at af27e79a61087635b07ff1e8f9dfdd37cdf47733 · sailpoint-oss/sailpoint-cli · GitHub the update command is
sudo update_engine_client -check_for_update
The question is why this wasn’t triggered automatically.
And even if it is not updated, the question is, which updates will be received in the future without manual intervention?
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.