Viosupgrade from HMC fails with HSCL2970 "fileset(s) required for the VIOS meta data restore seems to be not present in the provided installation image"

Troubleshooting

Problem

VIOS upgrade from 3.1 to 4.1 from HMC fails.

Symptom

HSCL2970 The IOServer command has failed because of the following reason:
Welcome to viosupgrade tool.
Operation triggered for given node(s).
Please wait for completion..
Upgrading from ioslevel '3.1.4.60' to '4.1.2.00'.
Verifying whether the MPIO software(s) is installed on the VIOS.
Following list of fileset(s) required for the VIOS meta data restore
seems to be not present in the provided installation image.
Continuing with the upgrade process may result in restore failure post installation:
1: EMC.Symmetrix.fcp.MPIO.rte => 6.1.1.1:DellEMC Symmetrix FCP MPIO Support Software
Choice[Y/N]:
Invalid choice, Please select from the available choice(s).
...snip...
Choice[Y/N]:
Invalid choice, Skipping the upgrade operation for: ''.
Retry upgrade operation for this VIOS with the correct VIOS object name.
Use of uninitialized value $user_choice in chomp at /usr/ios/sbin/viosupg.pl line 3911.
Use of uninitialized value $user_choice in uc at /usr/ios/sbin/viosupg.pl line 3912.
Use of uninitialized value $user_choice in uc at /usr/ios/sbin/viosupg.pl line 3918.
...

Cause

The image file used for the VIOS upgrade is missing fileset(s) for software that is currently installed in the 3.1 rootvg.

Environment

PowerVM VIOS 3.1 managed by an HMC

Diagnosing The Problem

Assess the VIOS to determine what additional software is installed on the original 3.1 rootvg.

In this example, EMC storage software is installed in the original 3.1 rootvg, but it does not exist in the image file used for the VIOS upgrade.

To check if EMC storage software is currently installed at 3.1, use lssw command:

$ lssw |grep -i emc

In this example, the following software was found:

EMC.Symmetrix.aix.rte:6.1.1.1
EMC.Symmetrix.fcp.MPIO.rte:6.1.1.1

Resolving The Problem

If the additional software currently installed at 3.1 is no longer needed, uninstall. Then, retry the VIOS upgrade.

Otherwise, create a custom mksysb to include the additional software. Then, retry the VIOS upgrade. For more details, refer to the VIOS upgrade checklist > VIOS REQ #3.

Related Information

How to Create Custom Mksysb Image For a VIOS Upgrade (viosupgrade)

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m3p000000PCa2AAG","label":"VIOSUPGRADE-\u003E3.1 to 4.1"}],"ARM Case Number":"TS022138345","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.4"}]

Tips