In the case of a Manual upgrade (where the upgrade via the UI has failed). Please use the steps below:
The commands below will show the two versions required to be inputted in the command lines, Old and New. If you are unsure about running these commands, please contact the Cloudsphere Support team to confirm the versions required.
Please note, that the article documents the appliance upgrade from version 4.6.1852 to 4.6.2008. Versions will differ over time, so you will be required to change the versions in the commands accordingly.
Steps to upgrade manually:
- Open Terminal
- sudo docker images
This will give you versions that are already there. We expect you will see the two below.
Note: Change the version accordingly in the command below.
- sudo docker pull registry.cloudsphere.com/iqcloud/server-appliance:4.6.2008
This will download the latest version of the appliance.
NOTE: The CloudSphere appliance has the right certificate.
The firewall at the customer’s end might try a cert rewrite
(what happens is the firewall looks at cert and tries to replace it).
To resolve any cert issue, the whitelisting of root level <docker.io and docker.com>
at the firewall is needed and there should not be any change to the certificate.
NOTE: Please note that load balancer may be present and may require additional whitelisting.
- sudo docker images – you will now see that build here.
The next thing we need to do is “TAG” the appliance (Tagging points the install to use this Image)
- docker tag http://registry.cloudsphere.com/iqcloud/serverappliance:4.6.2008 harbor2.iqcloud.iquate.org/fishbowl/server-appliance:4.6.2008
- The next step is to check the YML file
sudo more /opt/docker/appliance-stack.yml
We need to modify the highlighted line.
sudo sed -i "s|server-appliance:4.6.1852|server-appliance:4.6.2008|g" /opt/docker/appliance-stack.yml
This will update the top line shown above. You can check that by running sudo more /opt/docker/appliance-stack.yml | grep "server-appliance:"
Now we just need to stop the appliance
sudo /opt/docker/stop-appliance-stack.sh true
and start the appliance