CONTAP-813371: Default boot image changes to the new ONTAP version after cluster image abort-update during image installation
Issue
If the diagnostic
The abort confirmation warns that a mixed-version HA pair is possible, and the abort output advises waiting for the installation job to finish before starting a new upgrade. Neither message indicates that the installation will change the default boot image, or that the next reboot or takeover will boot the newly installed version.
The next reboot of an affected node, including a takeover, giveback, or panic, boots the newly installed ONTAP version. The HA pair is then running mixed ONTAP versions, and storage failover is disabled in both directions until both nodes run the same version:
cluster image abort-update command is run while an automated nondisruptive upgrade (ANDU) is installing the new ONTAP image on the nodes, the installation continues on each node after the abort. When the installation finishes, the newly installed image becomes the default boot image.The abort confirmation warns that a mixed-version HA pair is possible, and the abort output advises waiting for the installation job to finish before starting a new upgrade. Neither message indicates that the installation will change the default boot image, or that the next reboot or takeover will boot the newly installed version.
The next reboot of an affected node, including a takeover, giveback, or panic, boots the newly installed ONTAP version. The HA pair is then running mixed ONTAP versions, and storage failover is disabled in both directions until both nodes run the same version:
Takeover is not possible: The version of software running on each node of the SFO pair is incompatible, NVRAM log not synchronized
