Ksplice Updates Aren't Applied
If Ksplice updates aren't being applied to an instance, there could be an issue with the Ksplice software sources, the ksplice-offline package, or the userspace processes are too busy.
If you created an update job with Ksplice selected and the job successfully ran, but you don't see Ksplice job logs for the instance or the instance's Ksplice effective kernel hasn't been updated, it could be caused by one of the following issues.
If you created an update job with Ksplice selected and the userspace job failed, most likely the ksplice-offline package isn't installed.
Ksplice software sources aren't attached
OS Management Hub only creates Ksplice update jobs for an instance if the corresponding software sources have been attached to the instance or group.
ksplice-offline package isn't installed
The instance must have the ksplice-offline package for OS Management Hub to apply Ksplice updates.
Before installing the ksplice-offline package, remove the conflicting uptrack package. The following errors are an indication that the conflicting uptrack package is installed:
exit status 1: Error: Transaction test error:
file /usr/lib/uptrack/regenerate-crontab from install of uptrack-offline-<version>.noarch conflicts with file from package uptrack-<version>.noarch
...
exit status 1: Error: Transaction test error:
file /usr/lib/uptrack/regenerate-crontab conflicts between attempted installs of uptrack-<version>.noarch and uptrack-offline-<version>.noarch
...If the install job fails for the group, an individual instance in the group might have a conflicting Ksplice client installed. See Group manifest doesn't have uptrack, but ksplice-offline installation fails.
To install ksplice-offline:
-
Check if the conflicting
uptrackpackage is installed and remove it (uptrack-offlineis ok).See the following (search for
uptrack): -
Install the latest version of the
ksplice-offlinepackage.See the following (search for
ksplice-offline):
Ksplice software sources haven't synced
If the mirror content on your management station is out-of-date with the software source (either the sync failed or didn't occur recently), the management station might not be distributing the latest Ksplice updates.
- Identify the associated management station by viewing instance details.
- Select the name of the management station to check the status of the mirror sync.
-
In the list of Mirrored software sources, search for
ksplice. - If the status isn't Synced or hasn't been synced recently, resync the software source now.
- If the sync fails, view the failure details by clicking the down arrow on the right-side of the row. One possible issue could be the mirror storage is too small as the Ksplice software sources can be large.
Userspace processes are busy
The following error indicates that the userspace processes were too busy to apply Ksplice patches.
Ksplice was unable to patch the process as one of the patched functions is continuously in use by the process.Retry the Ksplice update when the target instance is under less load.