Add support for installing the latest version of OMI package.
Where should the reviewer start?
A bug was found related to the crontab entry recently, and a hot fix, omi-1.4.1-1, was released. The fix is also available in most recent release, omi-1.4.2-1. This bug occurred on systems that don’t have Kerberos installed, and caused an error email to be generated every minute.
How can this be manually tested? (brief repro steps and corpnet-URL with change)
The updated utilities.sh library file and how it is integrated with the installation process via the install-tools function.
What are the relevant TFS items? (list id numbers)
source utilities.sh
install-omi
Definition of done:
[x] Title of the pull request is clear and informative
[x] Add pull request hyperlink to relevant TFS items
[ ] For large or complex change: schedule an in-person review session
[ ] This change has appropriate test coverage
[x] Get at least two approvals
Reminders DURING merge
If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.
What does this PR do? Please provide some context
Add support for installing the latest version of OMI package.
Where should the reviewer start?
A bug was found related to the crontab entry recently, and a hot fix, omi-1.4.1-1, was released. The fix is also available in most recent release, omi-1.4.2-1. This bug occurred on systems that don’t have Kerberos installed, and caused an error email to be generated every minute.
How can this be manually tested? (brief repro steps and corpnet-URL with change)
The updated utilities.sh library file and how it is integrated with the installation process via the install-tools function.
What are the relevant TFS items? (list id numbers)
source utilities.sh install-omi
Definition of done:
Reminders DURING merge