test

Sun N1 Service Provisioning System 6.0 Release Notes

Runtime Issues

This section describes known runtime issues.

Using Special Characters While Renaming Plans or Components Causes Future Deployments to Fail (6582020)

If you rename a plan or component, and include a special character in the object name, future deployments of the plan or component might fail. An Unexpected Error screen is displayed.

The provisioning system UI does not verify that you have used valid characters when you rename a plan or component.

Workaround: Use valid characters when you rename a plan or component.

Host Characteristics Are Not Checked Before Adding to Host Group (6583978)

The provisioning system browser user interface does not check that the characteristics of a host (such as operating system, platform, and version) match a host group when you add the host to a particular host group. For example, you can add a Solaris host to the system#AIX5.2 host group. A subsequent plan run that is targeted for AIX hosts might end up executing on the Solaris host. The provisioning system will not generate an error to warn you about this grouping

Workaround: None.

List of Folders Does Not Refresh After Importing Plug-ins (6581474)

If you import a plug-in, then cancel the import operation, the plug-in is successfully imported and the list of folders for the plug-in does not accurately reflect the plug-in folders. This occurs because the folder list does not refresh after you import a plug-in.

Workaround: Log out of the master server, then log in again to view the list of folders for the plug-in.

Cannot Edit or Delete Folder (6410481)

If a user does not have writer permissions on a folder, the Edit and Delete buttons are disabled on the folder even if the user belongs to the group owner of the folder.

Workaround: Edit the folder permissions to explicitly grant the owner group permission to read, write, and execute for the folder.

All Components Not Listed By Default When Creating Container Component (6558053)

If you use the browser user interface to create a new container component, the New Component creation wizard does not list all the components in the provisioning system by default when you try to add component references.

Workaround: In the Component Reference screen, type in a string in the Search field to search for specific components, then click Search.

If you want to view and select from all the components in the provisioning system, click the Search button without typing a search string.

Windows: Backslash Character (\) Escapes Quotation Marks (”) at End of Paths (6347121)

If you include a backslash character (\) at the end of a Microsoft Windows path, and immediately before a quotation mark (”) in an argument with the N1 SPS command line interface, the command might fail. For example, review the following command.


>a.exe "C:\ab\cd\" -dst

C:\ab\cd\ -dst is interpreted as a single argument instead of the separate C:\ab\cd\ and -dst. This issue occurs because the backslash escapes the second quotation mark, creating a CLI syntax error.

Workaround: Omit trailing backslash characters from the end of Microsoft Windows paths with the N1 SPS CLI.

Importing Bundles That Include Container Components Might Fail (6562949)

If you import N1 SPS bundles that include container components that reference specific versions of subcomponents, the import might fail. This issue occurs because the import operation assigns the next available version number to a subcomponent of a container, and this version of the subcomponent might not exist on the target master server.

Workaround: To best avoid this issue, include bundle search criteria for all the referenced components and their exact versions in your bundle before including the container component that includes these subcomponents

Note –

Because the master server might include varying versions of these subcomponents, you might unintentionally reference different subcomponents in your container component.

Working With N1 SPS in Multiple Browser Tabs Results in Errors (6544803, 6422998, 6548431)

If you work with N1 SPS software in multiple web browser tabs, the provisioning system might not work as expected. At the time of publication, some of the unexpected behavior includes:

Workaround: While working with the N1 SPS software, log in to a single master server through a single web browser tab in a single web browser session.

Navigating With Web Browser Back Button Causes Unexpected Error (6571805)

If you use your web browser Back button to try to navigate to pages that were previously displayed, the pages might not display. Your browser might display an Unexpected Error.

Workaround: To navigate to a previous displayed page, click on the Back to Common Task Page link that is included in the error page.

Solaris: Plans Targeting Remote Agents on Same Host as Master Server Hang During Preflight (6552755)

If you run a plan that targets a Solaris 10 system that serves as both a master server and a remote agent, the plan might hang during preflight.

Workaround: Edit the TCP fusion settings in the /etc/system file. Follow these steps.

  1. In the /etc/system file, disable TCP fusion by editing the do_tcp_fusion entry to read as follows.


    do_tcp_fusion=0

  2. In the /etc/system file, set the tcp_fusion_unread_min value to 0.


    tcp_fusion_unread_min=0

Error When Adding Plan Variable Sets to Plans That Use Dynamic Targeting Feature (6556351)

If you try to add a plan variable set to a plan with the pdb.vs.add command, and the plan XML includes elements that use the dynamic targeting feature, the command fails. An error similar to the following is displayed.


The number of components entered is wrong. (031006)

Workaround: Do not add plan variable sets to a plan that uses the dynamic targeting feature.

Null Pointer Exception Error Occurs When Using <matches> With Null Pattern (6407827)

If you include a <matches> element with a null pattern value in a plan, and then try to check in the plan, the check in fails. A message similar to the following is displayed.


ERROR [main] com.raplix.rolloutexpress.systemmodel.plandb.ElementResolver 
(ElementResolver.java:34) - unable to create element
java.lang.NullPointerException

Workaround: Include a dummy pattern with the <matches> element. For example:


<matches value=":[ip1]" pattern="121212"/>
<matches value=":[group]" pattern="121212"

Unable to Load Library Error Occurs When Calling Shared Objects (6562333)

If a shared library is called by both the Sun N1 Service Provisioning System and another application, an error similar to the following displays.


java.lang.UnsatisfiedLinkError: Unable to load library 
"/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/cli/../
common/lib/solaris/libnative.so":
"Native Library /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/
common/lib/solaris/libnative.so already loaded in another classloader". (025004)
 at 
 com.raplix.util.platform.common.PackageInfo.throwLibraryNotFound(PackageInfo.java:66)
 at com.raplix.util.platform.common.PlatformUtil.loadLibrary(PlatformUtil.java:389)
 at com.raplix.util.platform.common.LibraryLoader$Loader.create(LibraryLoader.java:27)
 at com.raplix.util.DelayedCreator.getValue(DelayedCreator.java:56)
 at com.raplix.util.platform.common.LibraryLoader.load(LibraryLoader.java:58)
 at com.raplix.util.platform.common.NativeLoader.load(NativeLoader.java:43)

This error occurs when an application and the Sun N1 Service Provisioning System CLI call the same shared object.

Workaround: Use a single CommandManager instance to call shared objects.

The following example illustrates how to call a single CommandManager instance.


/** Not thread safe */
public class CMBuilderFactory {
    public static CommandManagerBuilder builder;
    public static CommandManager mgr;

    private CMBuilderFactory() {
    }

    private static CommandManagerBuilder getBuilder() {
        if(builder == null) {
            builder = new CommandManagerBuilder();
        }

        return builder;
    }

    public static CommandManager getCommandManager() {
        if(mgr == null) {
            CommandManagerBuilder bld = getBuilder();
            bld.setCLIInstallationDirectory(..);
            ... // additional setup parameters
            mgr = bld.build();
        }

        return mgr;
    }
}

Reset Maximum Java Heap Size to Import Large Plug-ins (6515287)

If you use the default maximum Java heap size for your N1 SPS master server, large plug-ins might not be successfully imported into your N1 SPS environment. This issue occurs on all non-Microsoft Windows platforms.

Workaround: Follow these steps.Edit the master server startup script (cr_server)

  1. If necessary, stop the master server.


    # N1-SPS-home/cr_server stop

  2. Edit the cr_server startup script, increasing the value of the CR_MAX_HEAP_SIZE parameter from 256 to 512 or 1024.

    If necessary, keep increasing this amount until the import issue no longer occurs.

  3. Restart the master server.


    # N1-SPS-home/cr_server start

Repeated Use of Differential Deploy When Checking in Components Might Consume Disproportionate Memory Resources (6327005)

If you repeatedly use the Differential Deploy feature to check in changes to components or resources, the resource might require disproportionately large memory resources to deploy.

Workaround: Do not use the Differential Deploy feature for components that you plan to revise repeatedly.

Windows: Database Optimization Should Be Performed On a Regular Basis (6262476)

If database optimization is not performed on a regular basis, performance deteriorates.

Workaround: Manually schedule a database optimization task.

This is a two phase process.

Note –

The following steps are performed on the Master Server.

  1. Creation of Database Optimization Script

    Create a new Windows command file called file_name.cmd in the server\bin\ directory of the Master Server installation. Copy the following text to the file_name.cmd file.


    REM No changes need to be made to the script after this line
cd %SPS_MS_DIR%\bin
..\cygwin\bin\bash.exe roxdbcmd vacuumdb -d rox

  2. Scheduling

    1. Choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks.

    2. Start the Task Scheduler Wizard by double-clicking Add Scheduled Task in the Scheduled Tasks folder. Click Next.

    3. Click Browse to open the Select Program To Schedule dialog box. Navigate to the optimizedb.cmd file.

    4. Choose the frequency of task runs.

      It is recommended that you run the task daily. Your options in subsequent screens will depend on your choices. The following steps assume that the user selected the daily option.

    5. Enter the time when the task should be run. Click Next.

      Note –

      It is advisable to run the database optimization task when the system is not being used. Choose the scheduling time accordingly.

    6. Type the name and password of the user who is associated with this task. Click Next.

      Make sure that you choose a user with sufficient permissions to run the program. By default, the wizard selects the name of the user who is currently logged on.

    7. Click Finish.

      The task is scheduled.

    8. For confirmation of successful task scheduling, it is advisable to choose Start ⇒ Settings ⇒ Control Panel ⇒ Scheduled Tasks and check the Task Exit Status Code. A successful task run is indicated by code 0x0.

      Note –

      Please note that the scheduled run of the task should be completed before observing the exit status code.

      For more information on Windows task scheduling options, see http://www.microsoft.com/technet/scriptcenter/guide/sas_man_lpja.mspx.

Backup and Restore Commands Fail To Restart Master Server (6398090)

When the backup and restore scripts are run, the Master Server with an SSL configuration fails to restart after the execution of these commands.

Workaround: Perform one of the following options:

Folder Add Command Fails With Permission Problems (6382198)

If you try to create subfolders and their parent folders by using the fdb.f.add command with the -parents true option, the command might fail. This error occurs if you try to create folders and subfolders of three levels or more.

For example, the following sample command fails because folder f1 does not exist.


r_cli -cmd fdb.f.add  -parents true -fullname /group1/f1/f2/f3 -u user1 -p user1

The following error message is displayed:

Unable to save folder /group1/f1/f2/ due to permissions problem. (013011) access denied (com.raplix.rolloutexpress.systemmodel.userdb.FolderPermission folder:129159219047-1139319070874-31478-1381549121 write)

This error occurs if you do not have administrator rights for a folder, but are a member of the group that owns the folder.

Workaround: When using the -parents true option, create only the new folder and its immediate parent.

Snapshot Data For Nested Components Might Not Be Purged When the Nested Components Get Reinstalled

If a nested component that is installed by way of the installation of a container component, creates snapshots, the snapshot data on the Remote Agent might not get purged when the nested component is uninstalled by the reinstall of the container component. This might lead to the Remote Agent, on which the nested component was installed, to consume more disk space than it should since the orphaned snapshot data was not purged.

Workaround: The orphaned snapshot data might be purged by installing and then uninstalling a simple component that creates snapshots on the Remote Agent with orphaned snapshot data. The install and uninstall cause the Remote Agent to compare its snapshot data with the Master Server. The result is that the snapshot data is purged for all the components that are no longer installed on the Remote Agent.

Plan Execution Pauses for 10 Minutes on execJava in Preflight on IBM AIX Remote Agents (6313197)

On an IBM AIX remote agent, the plan execution for CreateManagedServerPlan might pause for 10 minutes on an execJava step.

Workaround: None.

System Might Hang When Using SSL on Red Hat Linux Advanced Server 3.0 (5084676)

If you are running the Sun N1 Service Provisioning System on Red Hat Linux Advanced Server 3.0, the system might hang when using Secure Socket Layer (SSL) connections.

SSL uses SecureRandom which uses /dev/random to generate random numbers. Red Hat Linux Advanced Server 3.0 includes a bug that causes /dev/random not to collect entropy. Since /dev/random does not generate numbers unless sufficient entropy is collected, applications hang when attempting to read random data from /dev/random.

Workaround: Choose one of the following workarounds:

Notification Rules Might Cause Plans to Run Slowly (6176243)

If you create a notification rule that has few criteria or no criteria, plans might appear to run slowly. The plan does not complete slowly, but the display of the plan results might be delayed.

Workaround: When creating a notification rule, use as many criteria as possible. More criteria for a notification rule decreases the number of notification emails the provisioning system sends across the network. A lower number of notification emails is less likely to interfere with the display of plan results.