Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: Feb 07, 2014
Using a wildcard delete expression (delete *) on the primary of a bladed chassis, the subsequent messages sent to synchronize the blades will cause the mcpd process to crash.
Potential interruption from secondary blades and inconsistent state between the primary and secondaries.
This only occurs on a chassis with 2 or more blades in sync. Running a wildcard delete against any item will cause the mcpd process on the secondary blades to crash.
In order to prevent the secondaries from crashing, the user should use a transaction to delete specific objects instead of a wildcard expression.
Wildcard delete of items no longer causes secondary mcpd processes to crash.