Skip Validation Steps During the HyperFlex Upgrade

Introduction

This document describes how to skip validation steps during the HyperFlex upgrade.

Background Information

This can be required in case of hitting certain defects, for example: Cisco bug ID CSCvm77294  and Cisco bug ID CSCvp31021.

Note: Please do not use these steps if you are not instructed to do so. If you think that you need to skip some validation, reach the BU first to confirm.

Procedure

This particular example shows how to skip DRS Validation to workaround the defect Cisco bug ID CSCvm77294

1. Connect to the HyperFlex CMIP (for example, the IP you use to access HX Connect WebUI).
2. Navigate to the /usr/share/springpath/storfs-misc/validation/workflow_scripts directory.

   root@bsv-hxaf220-sc-2-3:~# cd  /usr/share/springpath/storfs-misc/validation/workflow_scripts
   root@bsv-hxaf220-sc-2-3:/usr/share/springpath/storfs-misc/validation/workflow_scripts#

3. Backup the pre_upgrade_cluster_check.xml file before you edit it and confirm that backup was created.
   

   root@bsv-hxaf220-sc-2-3:/usr/share/springpath/storfs-misc/validation/workflow_scripts# cp pre_upgrade_cluster_check.xml pre_upgrade_cluster_check.xml.bak
   root@bsv-hxaf220-sc-2-3:/usr/share/springpath/storfs-misc/validation/workflow_scripts# ls | grep pre_upgrade_cluster_check.xml
   pre_upgrade_cluster_check.xml
   pre_upgrade_cluster_check.xml.bak

4. Edit pre_upgrade_cluster_check.xml and use vi to comment out "Validate DRS Failover" block.
   

   root@bsv-hxaf220-sc-2-3:/usr/share/springpath/storfs-misc/validation/workflow_scripts# vi pre_upgrade_cluster_check.xml
   

5. To comment out the block, insert <!-- before the block and --> after it, so it looks this way:
   

                   <!--
                   <validator type="vcenter-validate-failover" description="Validate DRS Failover">
                       <argument name="vcenter-url" ref="vcenter-url"/>
                       <argument name="vcenter-user" ref="vcenter-user"/>
                       <argument name="vcenter-password" ref="vcenter-password"/>
                       <argument name="vcenter-datacenter" ref="vcenter-datacenter"/>
                       <argument name="ip-address-list" ref="ip-address-list"/>
                       <argument name="skip" value="false"/>
                   </validator>
                   -->

   If the validation fails because of affinity rules that say VM cannot be migrated to all nodes (which includes compute nodes):
   

                   <!--
                   <validator type="vcenter-query-vmotion" description="Validate vMotion Compatibility">
                       <argument name="vcenter-url" ref="vcenter-url"/>
                       <argument name="vcenter-user" ref="vcenter-user"/>
                       <argument name="vcenter-password" ref="vcenter-password"/>
                       <argument name="vcenter-datacenter" ref="vcenter-datacenter"/>
                       <argument name="ip-address-list" ref="ip-address-list"/>
                       <argument name="skip" value="false"/>
                   </validator>
                   -->

6. Save the file and now you can proceed to the HX Connect WebUI and start the upgrade procedure. The appropriate Validation can be skipped now.
7. Make sure to rollback the changes after successful upgrade.

Related Documents

Cisco bug ID CSCvm77294

Cisco bug ID CSCvp31021