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

  1. Fail out the node by lowering its priority (if using VRRP) or retracting its advertisement (if using BGP/OSPF).

  2. Follow the procedure to install hapee-1.7

  3. Copy /etc/hapee-[previousversion]/hapee-lb.cfg over to /etc/hapee-1.7/hapee-lb.cfg and any associated files (maps/certificates/etc)

  4. Test HAPEE to stop the old version and start the new one.

  5. Undo the change made in step 1 and proceed to the next node if everything continues smoothly. (If anything goes wrong, you can stop hapee-1.7-lb and restart hapee-<previousversion>-lb again.)

  6. Remove the repository URLs of the previous version and uninstall the old packages, after you are certain that you do not need to revert.

  7. Save the current configuration (i.e. 1.x):

    cp -rp /etc/hapee-1.x /etc/hapee-1.x.save

  8. Remove the old packages:

    yum remove "hapee-*"

  9. Install the new packages:

    yum install "hapee-1.7r2-*"

  10. Copy the saved configuration:

    cp -rpf /etc/hapee-1.x.save /etc/hapee-1.x

  11. Restart HAPEE services using init scripts or systemd.

    Warning

    You must run this procedure on the slave load-balancer.

Test HAPEE

After the upgrade, test HAPEE to make sure it runs correctly:

  1. Disable the old HAPEE branch from starting with the system, as follows:

    disable hapee-<previousversion>-lb

  2. Ensure that the new HAPEE branch starts with the system, as follows:

    systemctl enable hapee-1.7-lb

  3. Stop the old HAPEE daemon and start the new daemon:

    service hapee-<previousversion>-lb stop
service hapee-1.7r2-lb start

  4. Run tail -f /var/log/syslog (or distribution equivalent) to check for warnings or errors.

  5. Run wget localhost to ensure that HAProxy is responding. Adjust address/port as needed, and use a local address that is currently active on the box and not a VRRP IP.

  6. Put HAPEE back into the cluster.

  7. 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 revert to the old version.

Upgrade HAPEE within the 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.7r2 cannot be installed together on the same server

  • HAPEE repositories, GPG key, and customer subscription key remain the same

  1. Save the current configuration (i.e. 1.x):

    cp -rp /etc/hapee-1.x /etc/hapee-1.x.save

  2. Remove the old packages:

    yum remove "hapee-*"

  3. Install the new packages:

    yum install "hapee-1.7r2-*"

  4. Copy the saved configuration:

    cp -rpf /etc/hapee-1.x.save /etc/hapee-1.x

  5. Restart HAPEE services using init scripts or systemd.

  6. Test HAPEE to make sure that it runs correctly.

Warning

You must run this procedure on the slave load-balancer.