usermod Does Not Update the /etc/user_attr File for Privileged Users

During the installation of Container Manager, the /etc/user_attr file is updated by the usermod command. When you attempt to modify the profile of the users whose IDs were entered during the setup phase of Container Manager, the following message might be displayed:

UX: /usr/sbin/usermod: ERROR: user_name is in use. Cannot change it.

If you encounter any of the following errors, update the /etc/user_attr file manually to set the correct profile.

• Cannot create the resource pool

• Cannot create the zone

• Cannot update the project, zone, or pool

• Cannot activate the container for valid user

• Cannot associate the container to the host

On a S10 system, the contents of the /etc/user_attr file must look like the following:

username::::auths=auths;profiles=Pool Management,Zone Management,
Project Management,other_profiles;other_attributes

On a S9 system, the contents of the /etc/user_attr file must look like the following:

username::::auths=auths;profiles=Pool Management,Project Management,
other_profiles;other_attributes

On a S8 system, the contents of the /etc/user_attr file must look like the following:

username::::auths=auths;profiles=Project Management,other_profiles;other_attributes

To check whether the required profiles exist on the host or not, check the contents of the /etc/security/prof_attr file. This file must contain the required profiles according to the version of the Operating System (OS).

If the required profiles are not present, run the /opt/SUNWsymon/addons/SCM/sbin/scm-poolprof-script.sh file to create the required profiles. /opt is the directory in which Container Manager is installed. To run this script, the JAVA_HOME environment variable must have been set to /usr/j2se, or Java must have been installed in /usr/java.