The upgrading procedure varies depending on whether you are going to a newer version:
- From another major branch: for example, from 1.7r2 to 1.8r1
- On the same branch: for example, from 1.6r1 to 1.6r2
Upgrade HAPEE from another major branch
Fail out the node by lowering its priority (if using VRRP) or retracting its advertisement (if using BGP/OSPF)
Follow the installation procedure for your platform.
Modify the repository URLs (instead of adding new ones).
Copy the configuration file to
Stop the old version of HAPEE.
service hapee-1.6-lb start
After the upgrade, test HAPEE to make sure it runs correctly:
Disable the old HAPEE branch from starting with the system, as follows:
Ensure that the new HAPEE branch starts with the system, as follows:
systemctl enable hapee-1.6-lb
Put HAPEE back into the cluster.
After the new HAPEE branch has been running for a while, you can uninstall the old HAPEE branch. If there are problems, you can stop the new version and start the old version to revert.
Upgrade HAPEE on same branch
Before you upgrade HAPEE to a newer version, check that the following conditions apply:
- The directory names do not change
- The configuration files are located in the same place
- The init scripts keep the same names
- Each version in a branch is mutually exclusive, which means that another HAPEE version and HAPEE 1.6r2 cannot be installed together on the same server
- HAPEE repositories, GPG key, and customer subscription key remain the same
Remove the old packages and install the new ones:
yum swap -- remove "hapee-*" -- install "hapee-1.6r2-*"
You must run this procedure on the slave load-balancer.