Solaris Container Manager Bugs

Zone Creation Operation Does Not Show All the Physical Networks (6813833)

The first step “Provide Zone Creation Attributes” in the zone creation wizard has a drop-down list to specify the network interfaces. This drop-down list has only the network interfaces that have been plumbed.

Zone Creation Fails When Resource Pool Is a Dedicated CPU Pool (6618997)

When the zone creation wizard is launched from a Host's context, the resource pool selection screen is displayed. If there is at least one running zone created with a dedicated CPU on the target, the pool list displays it's SUNWtmp pool for selection. Zone creation fails when the SUNWtmp pool is selected. Temporary pools are created as a result of dedicated CPU configuration and cannot be shared by two zones. The following error message is displayed:

Below are the log file contents of the zone you have entered. 
autoboot: No such property type usage: set = Sets property values. 
For resource type ... there are property types ...: 

Workaround: Specify the dedicated CPU number or do not select a SUNWtmp pool for zone creation.

Whole Root Zone Migration Fails (6608767)

Whole root zone migration, including branded zone migration fails. Zone migration and copy, with contents, for a whole root zone might result in the following errors:

• Whole root zones are large in size. Tarring, compressing, and splitting whole root zones take a lot of time. Solaris Container Manager has a small timeout period after which it tries to reattach the original zone.

• Zones are split in fixed sizes of 2Mbytes. The size of the whole root zone is in Gbytes, so the sub- archives are large in number. The awk command does not support string lengths exceeding specified limits.

• The older zone archives remain on the server. During download, some unwanted files might be downloaded as a part of the zone image.

• The target system disk space should be at least three times the size of the zone. Inadequate disk space results in failure while extracting the archives.

In addition to these errors, the following issues might also occur:

• The zone contents are migrated completely, but might not be in the required state to attach to the target. This issue might occur even when Solaris Container Manager is not used for migration of the zone. In such a case, the zone may remain in the installed state, but will not boot.

• The web server installed with Sun MC, might fail. In such a case the whole file transfer will also fail.

Workaround: Ensure that the following conditions are complete:

• es-config -l root -M scm-container the command and profile updates have run successfully

• The hosts have the same hardware configuration and the same the release of OS installed on them

• There is sufficient disk space on the hosts.

• The /var/opt/SUNwsymon/downloads/ directory does not contain any files. Delete the files, if any.

• Wait at least for 2 minutes after clicking on Finish in case of zone copy or migration. Sometimes a blank window might remain on the screen. This window is harmless and can be closed forcefully.

• The /var/opt/SUNWsymon/cfg/scm-zonecopy.properties file has predefined values. The predefined migratePollInterval (600000) can remain as it is. The effective sleep time is equal to pollInterval x retry. Increase the default retry value from five to ten for a larger zone.

Zone Creation Does Not Display Privileges Selection Screens For Branded Zones (6600424)

The zone creation wizard consists of a screen to enter the default and optional privileges for zone configuration in the Solaris 10 11/06 and Solaris 10 8/07 releases. This screen is not displayed for branded zones.

Workaround: Modify the zone privileges using the Zone Properties page. The zone might need to be rebooted if the privileges are updated.

Alarm Created on a Project is Not Reflected at the Zone Level (6513203)

Install Solaris Container Manager 4.0 along with all the patches and create zones. Select any one of the rows of a default project of the newly created zones. When you click on Alarm Thresholds and create an alarm, the alarm is propagated on the left window pane but is not reflected on the zone which causes this alarm.

Workaround: None.

Unable to View Logs of the Renamed Zone (6512003)

When you type the new name of a renamed zone and click the Zone Log button, the following error message is displayed:

Zone Log Contents 
Below are the log file contents of the zone you have entered.
tail: cannot open input

This error indicates that the zone name is not valid. When you type the original name of the zone before it was renamed and click the Zone Log button, the following warning message is displayed:

Zone updated successfully
Zone updated successfully  
Configuring zone with the following attributes: 
zonename lzdeluth2  
Zone Rename successful.  
zoneadm: zone 'del2': WARNING: hme0:1: 
no matching subnet found in netmasks(4) for 10.12.174.155; 
using default of 255.0.0.0

Workaround: None.

Inconsistency While Renaming a Zone (6510926)

Rename a newly created zone and save the new name. Go to the resource Pool default page and the renamed zone is not reflected in the zone list. When you click on the zone, whose rename is not reflected, a new page is displayed. The right panel of this page is blank. The tree on the left panel is not expanded.

After renaming the zone, do not collapse the tree in the left panel. Refresh the system. The renamed zone is displayed on the right panel, but is not displayed under pool_default in the left panel.

Workaround: None.

Utilization Graph Image Titles and Headings Appear in English Language

If you choose a locale other than English, the title and headings of the Utilization Graph image appear in English language. 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 nondefault 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 do 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 previous errors, refer to the profile recommendations that follow. Before this, ensure that the user is a valid Sun Management Center 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 profiles:

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

• On Solaris 9 - Pool Management, Project Management

• On Solaris 8 - Pool Management, 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, add the missing entries in the following format 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>

Agent Performance Becomes Degraded or Unresponsive (6247892)

An agent has crashed leaving scm-container* files in the /var/opt/SUNWsymon/cfg/ directory. When the agent restarts, it might not perform in an optimal manner. This condition might identify itself by the following error message:

Insufficient security privilege to complete the operation.

You can determine the state of the processes on the agent by typing the following command:

% ps -eaf | grep esd

Workaround: To improve performance, type the following commands:

1. Become superuser.

   % su -

2. Stop the agent.

   # /opt/SUNWsymon/sbin es-stop -a

3. Delete the state files.

   # rm /var/opt/SUNWsymon/cfg/scm-container*

4. Restart the agent.

   #/opt/SUNWsymon/sbin/es-start -a

Java Web Console Does Not Restart After Reboot (6252233)

Following a server reboot, the Java Web Console does not start automatically.

To start the Java Web Console, type the following commands:

1. Become superuser.

   % su -

   Type root password.

2. Restart the Java Web Console.

   # /usr/sbin/smcwebserver restart

3. Ensure that Java Web Console restarts in the future.

   # /usr/sbin/smcwebserver enable

Workaround: None.

Zone Creation Fails When Invalid Locale Is Selected (6259233)

If an invalid locale is selected from the Locale drop-down menu in the New Zone wizard, zone creation fails. The Locale drop-down menu might contain invalid locale values.

To determine valid locales, go to “Supported Locales” in International Language Environments Guide.

Workaround: Choose a valid locale from the Locale drop-down menu in the New Zone wizard. If you are unsure of a locale value, select C for the English locale.

Tool Tip Displayed Instead of Alarm Badge (6219617)

If an alarm condition exists, the tool tip of the alarm badge might appear instead of the alarm badge itself.

If you navigate to another pane, then return to the alarmed object's icon, the badge on the icon is correctly displayed.

Workaround: None.

Exception Might Occur When Clicking the Browser Back Button (6241424)

When you click the browser back button, Container Manager might throw an exception. The browser back button is not supported in this release.

To recover from this exception, go to https://server_name:6789/containers and navigate to the appropriate page.

Workaround: None.

Some Processes Owned by User nobody Are Not Moved to a Container (5011290)

On the Solaris 9 Operating System, some processes, for example, the Java^TM application run by user nobody, are not moved to a container because of a bug in the newtask command.

Workaround: Start the applications that are run by user nobody in the appropriate container by using the newtask command.

# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Using nscd as a Match Expression Causes Host to Hang (4975191)

If you use one of the following match expressions when creating a container definition and subsequently activate it, the agent host hangs:

• n

• ns

• nsc

• nscd

Workaround: Start the nscd process in the appropriate project by using the newtask command:

# /usr/bin/newtask -p projectname command

projectname is the project in which the application is to be started and command is the command to start the application.

For more information, see the newtask(1) man page.

Agent Hosts Missing After Reinstalling or Running Setup of Server Layer (4964051)

If you plan to reinstall the Sun Management Center software on the server layer, be sure to save the data when uninstalling. Similarly, if you run setup again on the server layer, be sure to answer No when asked if you want to recreate the database. Otherwise, agent hosts previously discovered might be missing from the database if the data was not saved and you then reinstall or set up again on the server layer.

Workaround: If hosts are missing after you reinstall or rerun setup, restart the Sun Management Center agent on the hosts by doing the following procedure:

1. Log in to agent system.

2. Become superuser.

   % su -

3. Stop the Sun Management Center agent by typing:

   # /opt/SUNWsymon/sbin/es-stop -a

4. Start the Sun Management Center agent by typing:

   # /opt/SUNWsymon/sbin/es-start -a

zlogin -C Is Required After Creating a Zone (6388082)

To access a zone that is present in other physical machine, type zlogin -C <zone-name> from the global zone and set up the zone.

In the Name Server field of zone creation, type the name server value followed by IP address. For example, the value in the Name Server field could be ns1.sun.com (10.255.255.255).