OS security updates can signal completion too early
Details
| Detail name | Value |
|---|---|
| Changelog Number | 9051 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.0 |
| Fix Versions | Exasol 7.0.0, Exasol 6.2.4, Exasol 6.1.9 |
| Resolution Date | 2020-01-08 |
Problem
In some cases, the OS security/Patchlevel updates can show "Kernel has been updated. Please shutdown databases, Storage, nodes and restart license server to finish update" in EXAoperation while the update is actually still ongoing. This can especially happen if EXAoperation is not running on the license server node when the update is applied.
Workaround
- Ensure that EXAoperation is running on the license server when uploading an update.
- Update packages with a patchlevel newer than 2019-11-12 create a notice log message in the EXAoperation category for each node that was successfully updated:
Update to CentOS-7.5.1804_Patchlevel-OS-201911139999 finished on n0010
These can be checked to ensure that the updates on all running nodes correctly finished
