Bug ID 509063: Creating or loading guest on cluster with empty slot 1 can result in error

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP vCMP(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.3

Opened: Feb 24, 2015
Severity: 3-Major
Related Article:
K17015

Symptoms

Creating or loading guest on a cluster on which slot 1 is empty can result in error.

Impact

The guest create command fails or the config fails to load, and the system posts the error: Unable to find default core count for guest on this hardware.

Conditions

This only occurs on clustered BIG-IP systems when slot 1 is empty (unpopulated) with no 'cores-per-slot' attribute explicitly set.

Workaround

Explicitly set the 'cores-per-slot' attribute in the guest create command or in the guest config.

Fix Information

Creating or loading a guest config on a clustered BIG-IP with an empty slot 1 no longer results in an error, and the default cores-per-slot value is correctly used for the guests.

Behavior Change