LSF Version 7.3 - Administering Platform LSF

Cluster rollback behavior table
222 Administering Platform LSF
Cluster rollback behavior table
Version management files
Logs
When … Actions... The result …
Normal behavior. The installer replaces current files
with previous backup.
◆ Success, cluster reverts to
previous state.
The patch history is missing (files are
not found in the directory defined
by the parameter
PATCH_HISTORY_DIR in patch.conf)
Without the history, the installer
cannot determine which backups to
use. Since there is nothing to replace
them with, the installer does not
remove the current files.
◆ No rollback, cluster remains in
same state.
◆ Error presented on screen and
logged
You did not specify the most recent
patch.
The history indicates that the patch
is not the newest backup. The
installer must use the most recent
backup to roll back.
◆ No rollback, cluster remains in
same state.
◆ Error presented on screen and
logged
The backups are missing (expected
files are not found in the directory
defined by the parameter
PATCH_BACKUP_DIR in patch.conf).
Since there is nothing to replace
them with, the installer does not
remove the current files.
◆ No rollback, cluster remains in
same state.
◆ Error presented on screen and
logged
The installer is partway through the
roll back when there is a problem.
The cluster contains some older files
and some newer files.
If the installer cannot complete, it
reverses the rollback actions,
removing the older files and
returning the newer ones.
◆ No rollback, cluster remains in
same state.
◆ Error presented on screen and
logged
File Description
patch.log This file:
◆ Created by the patch installer (not created if you use lsfinstall)
◆ Created when you install a patch or update release
◆ Created in current working directory (or if you do not have write
permission there, logs to
/tmp)
◆ Logs installation steps
precheck.log This file:
◆ Created by the patch installer
◆ Created when you install or check a patch
◆ Created in current working directory (or if you do not have write
permission there, logs to
/tmp)
◆ Logs precheck steps
Install.log This file:
◆ Created by the LSF installer (not created if you use patchinstall)
◆ Created when you install a new cluster or update release
◆ Created in current working directory (or if you do not have write
permission there, logs to
/tmp)
◆ Logs installation steps