IBM Cloud Infrastructure Center Upgrade Validator Overview

The Upgrade Validator performs a series of checks on the management node and compute nodes for the current IBM Cloud Infrastructure Center installation. The Upgrade Validator can be run in "Pre-upgrade" mode (default) to perform checks prior to an upgrade, and "Post-upgrade" mode to perform checks after an upgrade. Results for each validation check are reported to the console output, including documentation links and any suggested changes.

In addition, the Upgrade Validator includes a "fix" mode. By default, the Upgrade Validator attempts to fix certain checks in the environment. This behavior can be disabled with the --nofix flag. More information on the validation checks can be found beneath.

For any validation checks involving compute nodes, the Upgrade Validator checks each compute node currently being managed by the management node.

To use the Upgrade Validator, there must be a previous version of IBM Cloud Infrastructure Center installed, such as version 1.1.3 or 1.1.4.

By default, the Upgrade Validator runs in Pre-upgrade mode and performs some automatic fixes.

The location of ./validate-upgrade is under extract_location/icic-opsmgr-1.2.4.0/images/icic-1.2.4.0/lib .

• Run the Pre-upgrade Validator with default behavior, use the Upgrade Validator with no flags.

  ./validate-upgrade
  

• Run the Post-upgrade Validator with default behavior, use the Post-upgrade flag.

  ./validate-upgrade --postupgrade
  

• Run the Upgrade Validator without performing any automatic fixes in the environment, use the --nofix flag. (This can be used with --postupgrade .)

  ./validate-upgrade --nofix
  

• Run the Upgrade Validator and perform automatic fixes for optional validation checks (experimental), use the --fix flag. (This can be used with --postupgrade .)

  ./validate-upgrade --fix
  

• Run the Upgrade Validator to validate specific compute nodes

  ./validate-upgrade --computenodes BOEM1,BOEM2
  

• Run the Upgrade Validator with specific validators

  ./validate-upgrade --validators mgmt_umask_config,selinux_config 
  

This section details the validation checks performed by the Upgrade Validator. If the check is denoted with (Automatic Fix) , it will be automatically fixed with the Upgrade Validator unless disabled with the --nofix flag. If the check is denoted with (Fix Available) , it can be automatically fixed with the --fix flag. If the check is denoted with (Manual Fix Needed) , the validation check cannot be automatically fixed and must be manually fixed by the user. If the check is denoted with (Diagnostic Check) , no fix is needed, and the check is only performed to report information to the user.

• validate_clean_cache (Automatic Fix) - Checks if the cached /var/opt/ibm/icic/backups/etc/nova/nova.conf file was cleaned. In fix mode, the cached nova.conf file is deleted.
• validate_mgmt_disk_space (Manual Fix Needed) - Checks if the management node has enough disk space for an upgrade.
• validate_compute_disk_space (Manual Fix Needed) - Checks if each compute node has enough disk space for an upgrade.
• validate_selinux_config (Diagnostic Check) - Checks the selinux configuration for the management and compute nodes and warns if there it is not enabled. Note: SELinux must be enabled for the management node, an install or upgrade of IBM Cloud Infrastructure Center will fail if SELinux is not enabled for the management node. SELinux is recommended but not mandatory for the compute nodes.If you didn't enable SELinux for compute nodes of your previous IBM Cloud Infrastructure Center installation, then please keep the SELinux setting unchanged, otherwise you may fail to upgrade the compute node
• validate_mgmt_umask_config (Fix Available) - Check the umask configuration for the management node. In fix mode, the shell configurations are modified to set umask for bash shells. May require a new shell instance. Note: If the umask setting in management node and compute node is not 022, change the umask back to 022 before the upgrade. Please refer to redhat Managing the umask how to check and set default umask for a user.
• validate_compute_umask_config (Fix Available) - Check the umask configuration for the compute nodes. In fix mode, the shell configurations are modified to set umask for bash shells.
• validate_mgmt_firewall_config (Diagnostic Check) - Checks the firewall being used on the management node.
• validate_compute_firewall_config (Diagnostic Check) - Checks the firewall being used on the compute nodes.
• validate_icic_policy_change_backup (Automatic Fix) - Checks if the policy files were changed recently. In fix mode, the policy files are automatically backed up to the default backup folder.
• validate_check_compute_ssi_status (Diagnostic Check) - If in a z/VM environment, checks if the z/VM system is an SSI configuration or not.
• validate_check_storage_agent_node (Manual Fix Needed) - Checks if there is storage provider added on management node. Note: If there is storage provider added on management node, you must migrate the storage provider from the management node to compute node. Refer to Migrate storage about how to migrate storage provider.
• mgmt_icic_config (Manual Fix Needed) - Checks if any default configuration values have been updated in various directories. If this check is flagged it means that a default configuration value may have been updated and would be overwritten on upgrade. Please backup these changed configs (if any) before upgrade and then apply them to the config file if needed. If this is not the case then this can be safely ignored.
• compute_sshd_config (Manual Fix Needed) - Checks the sftp server configuration in /etc/ssh/sshd_config on the compute node.

• validate_icic_install_error_check (Diagnostic Check) - Checks for errors that may have occurred during a recent installation.
• validate_icic_upgrade_error_check (Diagnostic Check) - Checks for errors that may have occurred during a recent upgrade, including errors that may have occurred during the restore operation.