Last Modified: Nov 22, 2021
Known Affected Versions:
Opened: Sep 26, 2013 Severity: 1-Blocking
If a VCMP guest is configured with an initial hotfix which is then deleted from the system, then the error message "Configuration error: Configuration from primary failed validation: 01071701:3: Initial hotfix image version differs from software image version." may spuriously occur during provisioning. Furthermore, under certain conditions there might be daemon reboots that accompany this error.
The impact may range from a misleading error message, as in the case where the hotfix is actually in the process of syncing in a cluster, to MCP being stuck in a restart loop.
A VCMP guest must be configured with a valid initial hotfix, which is then removed with, for example, 'del sys software hotfix', in tmsh. Daemon restarts (MCPD and dependents) have been observed when the hotfix is deleted during guest install and the primary subsequently rebooted.
Modify the configuration so that the guest referenced in the error is not provisioned, and make sure a valid hotfix is in place before setting its state back to provisioned. This will not completely remove spurious error messages, but will eliminate perpetual MCPD restarts.
The misleading "Initial hotfix image version differs" error message will no longer be emitted unless the configured hotfix image is in fact not compatible. Furthermore, daemon restarts will not occur in the case of races in hotfix image configuration sync, or missing hotfix image.