"

GNS3 controller version 2.1.10 is not the same as compute server GNS3 VM (GNS3 VM) version 2.1.9"
Yeah, the upgrade procedure of the GNS3 VM is quite flaky. Here my experiences with upgrading a pristine v2.1.9 GNS3 VM.
open-vm-tools package is not updated correctly
With the first upgrade the open-vm-tools package is not installed correctly, no matter if you answer Y(es) or N(o) to the question about using the updated tools.conf. Re-doing the upgrade solves this issue.

GNS3 version stays at v2.1.9
The reason is, that the upgrade procedure uses the last line of git tag -l 'v2.1*' to get the latest version. But git tag sorts alphabetically, so the last line is v2.1.9. Adding the option --sort=version:refname v2.1.10 will be on the last line.
gns3@gns3vm:~/gns3-server$ git tag -l 'v2.1*' | grep -v '[abr]' | tail -n 1
v2.1.9
gns3@gns3vm:~/gns3-server$ git tag -l 'v2.1*' | grep -v '[abr]'
v2.1.0
v2.1.1
v2.1.10
v2.1.2
v2.1.3
v2.1.4
v2.1.5
v2.1.6
v2.1.7
v2.1.8
v2.1.9
gns3@gns3vm:~/gns3-server$ git tag -l --sort=version:refname 'v2.1*' | grep -v '[abr]' | tail -n 1
v2.1.10
Workaround until this gets fixed: update the gns3server manually
Start a shell and enter the following commands:
cd ~/gns3-server/
git checkout v2.1.10
sudo pip3 install -U -r requirements.txt
sudo python3 setup.py install
sudo reboot
I just fixed with a more complicated command line ;) Please try again.
Solved and working properly, thanks to the instructions provided by ehlers (https://github.com/ehlers).
Thank you very much for responding and also make it so fast.
Your updated upgrade_2.1.sh works on the third update, starting from a pristine v2.1.9 VM
I did this procedure two times, both with the same results.
BTW: Your command line is really complicated. Why not using git tag -l 'v2.1*' | grep -v '[abr]' | sort -V | tail -n 1 or git tag -l --sort=version:refname 'v2.1*' | grep -v '[abr]' | tail -n 1 ?
Edit: Just saw, that you choose sort -V.
Edit 2: Just did the test again, same results. I verified, that on the second update it uses the old update procedure, on the third update it uses the current (and correct) procedure from github.
@ehlers I am going to check how I can fix the open-vm-tools issues and investigate why the old procedure is used on second update.
I've fixed all the upgrade issues. Everything should work on first upgrade. That being said there are still some inconsistencies that we should aim to fix when we migrate the GNS3 VM to the latest Ubuntu LTS.