Bug ID 1408229: VCMP guest deployment may fail on newly installed blade

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP vCMP(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3

Opened: Nov 29, 2023

Severity: 3-Major

Symptoms

If a VCMP guest is configured to be Provisioned or Deployed to multiple blades in a VIPRION chassis, and one of those blades is replaced or has a new installation of BIG-IP installed, the VCMP guest may fail to be Provisioned or Deployed to the newly installed/reinstalled blade. A message similar to the following may be logged to the LTM log (/var/log/ltm): <date> <time> slot# err vcmpd[#####]: 01510004:3: Guest (GUEST_NAME): Install to VDisk /shared/vmdisks/GUEST_IMAGE_NAME.img FAILED: Child exited with non-zero exit code: 255 When this issue occurs, the blade where the VCMP guest image fails to be installed is found not to be running the KVM kernel module: [root@CHASSIS_NAME:/S1-green-P::Active:Standalone] ~ # clsh 'lsmod | grep kvm' === slot 2 addr 127.3.0.2 color green === kvm_intel 179624 68 kvm 603109 1 kvm_intel irqbypass 13503 1 kvm === slot 3 addr 127.3.0.3 color green === kvm_intel 179624 0 kvm 603109 1 kvm_intel irqbypass 13503 1 kvm === slot 4 addr 127.3.0.4 color green === <<<<<<< no 'kvm' module shown for affected blade === slot 5 addr 127.3.0.5 color blue === === slot 6 addr 127.3.0.6 color blue === === slot 7 addr 127.3.0.7 color blue === === slot 8 addr 127.3.0.8 color blue === === slot 1 addr 127.3.0.1 color green === kvm_intel 179624 68 kvm 603109 1 kvm_intel irqbypass 13503 1 kvm

Impact

The VCMP guest fails to be Provisioned or Deployed to the newly installed/reinstalled blade.

Conditions

This may occur if: -- VCMP is provisioned, and one or more VCMP guests are provisioned/deployed in a VIPRION chassis with multiple blades. -- One of the blades is replaced with a new blade (such as from an RMA replacement). -- The newly installed/reinstalled blade has a version of BIG-IP installed that does not match the BIG-IP version installed and running on the existing blades in the chassis. -- The newly installed/reinstalled blade must reboot multiple times to complete the installation of all required BIG-IP versions to match the existing blades in the chassis. -- One or more VCMP guests are configured to be Provisioned and/or Deployed to the newly installed/reinstalled blade's slot. -- The newly installed/reinstalled blade does not automatically reboot after successfully provisioning VCMP after the automated installation of the final (matching) BIG-IP version.

Workaround

To work around this issue when it occurs, reboot the affected blade. -- From the console of the affected blade: reboot -- From the console of another blade in the chassis: clsh --slot=# reboot (where # is the slot number of the affected blade)

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips