IJ49629: SSP OR CM DB DOES NOT START AFTER VIOSUPGRADE

APAR status

• Closed as documentation error.

Error description

• After a viosupgrade with option "-F" to copy the users
  and groups from VIOS 3.1 install, CPU usage on the VIOS
  could be high and caused by SSP and/or CM DB
  initialization looping on :
  ...
  ERROR: Failed to get group id for 'db_users'
  ...
  

Local fix

• $ oem_setup_env
  # stopsrc -s vio_daemon
  # mkgroup -'A' id='202' users='vpgadmin,padmin' db_users
  # startsrc -s vio_daemon -a "-d 4"
  # kill -1 vio_daemon's PID
  

Problem summary

•  recommended NOT to use -F forcecopy with -g for
   system specificing usage of -g and -F forcecopy flags for
  viosupgrade did not describe the dangers of using these flags
  to overwrite default vios users required for the vios to
  function properly.
  https://community.ibm.com/community/user/power/blogs/ruchira-cha
  wla/2023/12/08/vios-41-migration-demystified-expert-tips-and-ins
  i
  
  The blog has been updated to include the note:  Note: It is
  files like /etc/group.The -g flag without the -F forcecopy
  option copies the files to the location:
  /home/padmin/backup_files directory in the new rootvg volume
  group.
  
  /
  

Problem conclusion

• Updated blog.  -g and -F forceopy should not be used to force
  overwrite /etc/group when migrating VIOS as new users/groups
  might be introduced that are required for VIOS to function and
  should not be lost.  Instead, just use -g, and manually merge
  the copy of /etc/group from backup_files after migration.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels