may publish updates to the software release that you have currently installed. The
|D s item|
|item||Maintenance Release Updater|
can be run from the
to check for updates for the release of the platform that is currently installed on the node. If a maintenance release (e.g. Release x.y.1) is available, the script downloads the package and launches the update locally.
This script can only be used for maintenance patches for the current release. For example, you cannot upgrade from Release 5.1 to Release 6.0 or any later release using this script.
NOTE: This script is not available in the GA release of any major release, since no maintenance release is yet available.
Below are some example upgrade paths.
NOTE: These are example upgrade paths. Some of these releases may not exist yet.
|Release 6.0.1 → Release 6.0.2||Supported|
|Release 6.1.1 → Release 6.1.2||Supported|
|Release 6.1.1 → Release 7.0.0||Not Supported|
|Release 6.0.0 → Release 6.2||Not Supported|
|Release 6.0.1 Hot Fixes||Not Supported|
NOTE: You must acquire the script from the . Please use the credentials provided to you to connect to the download site.
NOTE: Before you begin, shut down the and perform backups of the deployment directory and .
- This script is supported by Centos/RHEL 6 or later. Ubuntu is not supported.
- This script must be run as the
root user on the node.
- The must be installed on the node and configured to run using the user.
- To enable downloads of updates, CURL must be installed on the node.
Prior to execution, the script should be placed somewhere other than the
/tmp are acceptable locations.
- The script must have execute permissions, if it doesn't already have them.
For each run of the script:
- It creates a unique working directory under
- The working directory is where downloaded artifacts, backup artifacts, and log files are stored during execution.
Download and Install:
The following command checks for an update. If one is detected, it downloads the update and launches the updating process:
| NOTE: The credentials asked by the script are only used to connect to the FTP site to check for and download installer artifacts. These credentials are not stored anywhere.|
The package is downloaded by default to the following location:
Install Downloaded Package:
If you have separately downloaded the update from
, the following performs the update from the local package, which is specified by parameter:
./trifacta-maintenance-release-upgrade.sh -i <path_to_downloaded_RPM>
Do not restart the platform at this time, in case there are necessary migrations for this update. See below.
Even between maintenance releases, it's possible for some configuration settings to be updated or migrated into the Workspace Admin page.
NOTE: For every upgrade or update, you should perform the steps to migrate any configurations that have changed. If there are no configurations to migrate, the process is harmless.
For more information, see Migrate Configurations.
After you have completed the update:
- Review any update documentation provided to you.
- Restart the platform. See Start and Stop the Platform.
- Verify operations. See Verify Operations.