Container Manager Issues

These runtime issues might occur in the Solaris Container Manager 3.6 software.

CLI Installation of Solaris Container Manager 3.6 Is Not Translated

If you use the command line interface (CLI) version of the Solaris Container Manager 3.6 installation, it is only available in English. This version is not translated. The English language aspect does not affect the installation process or functionality.

Workaround: To perform the installation in your locale, use the GUI installation (es-guiinst) and setup (es-guisetup).

Utilization Graph Image Titles and Headings Appear in English

If you choose a locale other than English, the title and headings of the Utilization Graph image appear in English. These values are not localized.

SPARC: Extended Accounting Feature Is Disabled in Solaris 8 Release

The Extended Accounting feature is disabled in Container Manager on systems that run the Solaris 8 OS. As a result, the Extended Accounting Data (Exacct) column of the CSV file for a container on a Solaris 8 system will be null.

Some Projects in the /etc/project Database Might Not Be Discovered by Container Manager

If a project in an agent host's /etc/project database has the same project ID as a project in the Sun Management Center database but has a different project name, then the project will not be discovered by Container Manager. A unique project ID across all hosts in the same server context is a Container Manager requirement.

You should not use the projadd command to create projects. Use only Container Manager to manage projects.

Workaround: Delete the non-default project that was created by the projadd command from the agent host's /etc/project database and create the container by using the New Container wizard in Container Manager.

Security Privilege Error Messages Are Incomplete

Error messages displayed during failure of creation, modification, or deletion of Zone, Pool, or Project are incomplete and does not provide enough details. Following are the error messages you might encounter:

• 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

Workaround: If you encounter any of the above errors, refer to the points mentioned below. But first ensure that the user is a valid SunMC user and has the necessary administration privileges (part of esadm, esdomadm groups).

Ensure that the user is associated with the necessary profiles by running the following command:

$ profiles <username>

Following are the necessary profile:

• On Solaris 10 - Zone Management, Pool Management, Project Management

• On Solaris 9 - Pool Management, Project Management

• On Solaris 8 - Project Management

If you find the necessary profiles missing, run the following command (as the superuser) and modify the profiles associated with a user:

# usermod -P "<comma separated list of necessary profiles>" <username>

If any profile does not exist on the system, please add the missing entries in the format mentioned below to the prof_attr file in the /etc/security directory.

Pool Management:::Resource pool management profile:help=RtPoolMgmt.html

Project Management:::Manage Solaris projects:auths=solaris.project.read,solaris.project.write;help=RtProjManagement.html

Run the following command to find if the user is a part of the local access user list for the SCM module.

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -s

If user is not part of the access list, run the following command:

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -l <user_name>