This user must be deleted prior to upgrade.
In the example above user "hmc" has UID 106 - which is in the list of impacted UIDs. In this example user "hmc" has UID 106 user "hmcxx" has UID 167.ī) Compare the UID to the following list of built in UIDs Hmcxx:x: 167:500:test hmc user:/home/hmcxx:/bin/hmcbash Hmc:x: 106:500:HMC HMC User grep ^hmcxx: /etc/passwd The UID is the 3rd field (colon grep ^hmc: /etc/passwd If desired, the list of users found in step 2 can be narrowed down further by performing the following additional steps: (optional) Determine if the user has a conflicting UID
#Usb burning tool fix parsing error upgrade
In this example there are two user profiles that may cause the upgrade issue.ģ. If one or more users are found, continue to the next step (optional) or skip to "Preventing the upgrade lshmcusr -F name | grep hmc If no results are found, the HMC is not impacted. Search for any user with the letters 'hmc' in the name. Log into a restricted shell (ssh) as hscroot or another user with hmcsuperadmin role.Ģ. To determine if the HMC to be upgraded will encounter the error perform the following:ġ. The user profile must have a "UID" (an internal user id number used by the base operating system) that conflicts with the UID of one of the built in user ids in V7R7.8.0. The user profile must have the letters "hmc" in the name. In addition, both of the following must be true: The problem only impacts HMCs that have had an additional user profile created. The problem is caused by an error parsing and restoring the HMC user profile data during the upgrade process. If ssh is enabled, only the hscroot id is able to log in successfully. The GUI login fails with a message that either the USERID or PASSWORD is not correct.
#Usb burning tool fix parsing error how to
It also describes how to recover an HMC after a failed upgrade.Īfter an upgrade to HMC 7.7.8, no user profile is able to log into the GUI. This document describes how to determine if an existing HMC can be upgraded to HMC V7R7.8.0 without encountering a known issue that causes log in failures after the upgrade.