Technical Support Advisory: Updating the Vertica AMI
Some Vertica AMI users have reported connectivity issues immediately after running yum update, when updating their instance without testing all possible updates that can be applied. If a problem occurs, this practice can cause "Instance Status Checks" to fail. It can also make it impossible to connect to the AMI over the network.
Hewlett Packard Enterprise recommends taking the following approach:
- Do not update all packages at the same time; rather, update only those packages you have a reason to update
- Validate any changes to production systems in a test or staging environment before applying them to production systems.
- Create a backup before updating or changing a production system.
How to Exclude Packages From an Update
If you encounter issues with any particular package, you can exclude it from an update using Yum. See https://access.redhat.com/solutions/10185 for details.
Known issues with Vertica 7.2.x and 7.1.x AMI updates
Updates to the following package(s) are known to cause problems with updates to the Vertica 7.2.x and 7.1.X AMIs:
Package | Action |
---|---|
microcode_ctl |
Exclude this package from your update:
|