Install the HVP patch

• Copy the Holly patch file to /export/home/holly-ivg on the IVG server.

File names for different versions are listed below.

IVG 5.3.2

• For RHEL 7.9/CentOS 7.9, use HVP-7.2.19-3217-b899dfd-rh7.install
• For RHEL 8.6, use HVP-7.2.19-3218-b899dfd-rh8.install

IVG 5.3.3

• For RHEL 7.9/CentOS 7.9 use HVP-7.2.20-3247-45e6c41-rh7.install
• For RHEL 8.6 use HVP-7.2.20-3248-45e6c41-rh8.install

In this document, the commands will reference the RHEL 8.6 patch file HVP-7.2.19-3218-b899dfd-rh8.install. Update the filename based on your OS, if needed.

• Change the permissions of the patch file to be owned by the holly-ivg user with execute permissions.

For IVG 5.3.2:

chmod a+x /export/home/holly-ivg/HVP-7.2.19-3218-b899dfd-rh8.installchown holly-ivg:holly-ivg /export/home/holly-ivg/HVP-7.2.19-3218-b899dfd-rh8.install

For IVG 5.3.3:

chmod a+x /export/home/holly-ivg/HVP-7.2.20-3248-45e6c41-rh8.installchown holly-ivg:holly-ivg /export/home/holly-ivg/HVP-7.2. 20-3248-45e6c41-rh8.install

• Log in as the holly-ivg user.

su - holly-ivg

You will be taken to the user's home path /export/home/holly-ivg. The HVP patch should already be there. The next few steps must be taken as the holly-ivg user.

• Stop the hmsweb worker.

fm stop hmsweb

• Run the Holly patch file to upgrade Holly.

For IVG 5.3.2:

./export/home/holly-ivg/HVP-7.2.19-3218-b899dfd-rh8.install

For IVG 5.3.3:

./export/home/holly-ivg/HVP-20-3248-45e6c41-rh8.install

Warnings related to .tar files are expected. You may see many warnings similar to the following examples, and they can be ignored.

tar: ./web/hmsrails/public/assets/v1/.sprockets-manifest-70dee2d68d042ccbf4fede090befd12e.json: Cannot stat:
No such file or directory

tar: ./web/hmsrails/public/assets/v1/application-71c108703dcaa09c7af225f04cbe0742d780bcf9e7b10617d2b1434881143943.css:
Cannot stat: No such file or directory

If successful, the last few lines of the output should appear as follows:

Update config (factory settings)
  browser
  callcontrol
  hmsweb
  openssl
  sip_ap
Release applied

• Start the hmsweb worker.

fm start hmsweb

• Restart Holly services

hvpctl restart

• Run foreman to verify that all workers are running and that the holly version has been updated.

fm

Following is example output from foreman showing all Holly workers:

Fri Dec 16 08:58:33   installhvp04+holly-ivg   (HVP-7.2.19-3218-b899dfd)
Holly Foreman (2432984): up 2 h 36 min
  NAME                 OP           TIME   PID    MEM   CPU%  THR   FD  FAIL
  browser              ok        2:36:48 2433112 586.6M   0.00  427  418     0
  callcontrol          ok        2:36:48 2433010  86.2M   0.00   55   16     0
  configserver         /ok       2:36:53 2432942  46.4M   0.00   39   25     0
  ctieventconsumer     ok        2:36:48 2433060 109.9M   0.00   18   31     0
  foreman              /ok       2:36:48 2432984  10.0M   0.00   15   34     0
  hlm                  ok        2:36:48 2433012  16.8M   0.00   17   15     0
  hmspageserver        ok        2:36:48 2433013  17.6M   0.00    9    9     0
  hmsweb               ok        2:36:48 2433106  11.2M   0.00    1   20     0
  hvg                  ok        2:36:48 2433015  61.5M   0.50  835  429     0
  hvss                 ok        2:36:48 2433016  15.7M   0.00   15   13     0
  logmgr               ok        2:36:48 2433017  22.3M   0.00   24   18     0

• Run the holly-version command to verify the Holly version is now HVP-7.2.19 (for IVG 5.3.2) or HVP-7.2.20 (for IVG 5.3.3).

holly-version

Update version information

After patching, the final step is to update version information for IVG and Holly in the version.txt file (/etc/VirtualHold/version.txt). You will need sudo/root user access to make the following changes.

For IVG 5.3.2:

• Update the Holly Version to 7.2.19
• Update the IVG version to 5.3.2

For IVG 5.3.3:

• Update the Holly Version to 7.2.20
• Update the IVG version to 5.3.3

Below is an example showing the two updates for version 5.3.2: