The Rollup Patch installer is a cumulative patch, and is a step closer to the "continuous deployment" method of updating. The patch installer is intended to be used independent of Technical bulletins, though some Technical Bulletins may depend upon the Rollup Patch already having been applied, and some of the code we supplied in Technical bulletins originally may be superseded in a given version of the Rollup Patch. Generally, we recommend applying the rollup patch first, then looking at the Technical bulletins and applying them as needed. The rollup only includes code, not data or configuration, and does no scripted updates, so for some things you will still need the Technical Bulletins, as they can apply scripted updates and make configuration changes.
The rollup patch installer does make database schema updates, so you will need to have a valid postgres user password for the database (see Prerequisites, below). It is not necessary to run the patch installer on a database-server-only installation of GroundWork.
Since it is a cumulative patch, you need only install the latest version - there is no need to install each version of it sequentially. The Rollup Patch Installer is also reversible - it makes a backup of everything it changes, and you can use a simple process to reverse the updates it makes.
If you install two or more sequential rollups and need to roll them back, simply apply the rollback scripts in the reverse order of the rollup patches.
|If you installed patch 4111, there is an extra step. See below.|
- You will need a short downtime window, as the Rollup Patch Installer stops all GroundWork services for update.
- You will also need root user access to the GroundWork server.
- You will need to know the postgres user password for the database server, usually. Not all patch installers involve database changes, and so it's not always required, but be ready in case it is needed.
If you have several GroundWork servers in a parent-child configuration, you may run the rollup on any server in any order. Note that it will interrupt monitoring briefly when you apply or roll back.
|You MUST have the postgres user password available before running this patch!|
- Transfer the Rollup Patch installer to your GroundWork server, and place it in an empty directory.
- Log in to the command line on the GroundWork server and become root in that directory
The installer will stop GroundWork services, ask for the db user password, then patch and restart the groundwork services.
- Check to see that the patch got installed. If the run of the patch installer ends with lines similar these:
then the patch did not get installed. In a situation like this, the list of supposed GroundWork processes shown has blocked the installation of the patch, because the patch installer cannot be assured that there will be no interference from such processes. In the particular case shown, there is a user logged in as nagios, running the bash shell. This is not a GroundWork process per se, but the patch installer cannot tell the difference. To successfully install the patch, you must get rid of all the processes listed, and then re-run the patch installer.
- Once the patch installer has successfully run to completion, you should find lines like this at the end of the indicated file, showing that the patch has been applied:
Hopefully you will not need to roll the changes back. If you have any issue after the patch, please let GroundWork Support know as soon as you can. We do extensively test each change, and we do integration and system tests on each Rollup, but we recognize you may need to get back to where you were.
Note that no configuration files will be altered or rolled back, that is up to you to control. Also, when you install a patch, the previous patch state is saved in a directory under /usr/local/groundwork/backup-gwNNNN, where NNNN is the prior patch level. That's the directory you will use to roll back with this procedure.
- Log in to the command line on the GroundWork server and become root.
- Change to the /usr/local/groundwork directory, where you will see the directory named for the prior patch level, e.g. if rolling back to 4114:
- Execute the rollback script:
You must access the restore script from the parent directory, not the same directory as the script itself. You will once again need to provide the postgres user password.
If you have installed patch 4111, which was briefly available, it contains a flaw that must be addressed with a command to correct table ownership. This is only necessary if you installed patch 4111. You can do this step at any time including before or after applying 4118 or 4122.
The symptom that this is necessary is evident as failure to do backups and a similar error when you try to do a build instance:
So to fix in place, as root, and with the knowledge of the postgres user password at hand, type these two lines
You will be prompted for the postgres user password.
The details of what issues and features are changed in this version of the rollup patch are detailed here.
The details of all prior rollup patches are explained at https://kb.groundworkopensource.com/display/DOC721/GWME-7.2.1-00+version+4125+Rollup+Patch+Details and older sibling pages.