test

Sun N1 Service Provisioning System 6.0 Release Notes

Chapter 2 Sun N1 Service Provisioning System 6.0 Issues

This chapter describes Sun N1 Service Provisioning System 6.0 issues that are known to be problems.

Installation Issues

This section describes known issues with installation.

Solaris: Master Server Installation in Non-Global Zone Fails (6423893)

If you try to install the Sun N1 Service Provisioning System master server software in a non-global zone on a Solaris 10 system, the installation fails. The following error is displayed.


 Checking your Shared Memory and Semaphore configuration.
                Checking for module 'shmsys'
                Module 'shmsys' is not loaded.  Attempting to load the module.
Insufficient privileges to load a module
        Load module 'shmsys' and then restart the N1 SPS Master Server Installer 
       (try this: modload /kernel/sys/shmsys)
                Checking for module 'semsys'
                Module 'semsys' is not loaded.  Attempting to load the module.
Insufficient privileges to load a module
        Load module 'semsys' and then restart the N1 SPS Master Server Installer
        (try this: modload /kernel/sys/semsys)

Workaround: Manually load the shmsys and semsys modules, then retry the installation.


# modload /kernel/sys/shmsys
# modload /kernel/sys/semsys

Solaris x86: Secure Shell Session Does Not Terminate After Remote Installation of Remote Agent (6551914)

If you use the cr_ra_remote command to remotely install a remote agent over a secure shell connection (SSH) from a master server that is running the Solaris 9 OS, the SSH session does not terminate correctly.

Workaround: Apply patch ID 114357-05 or newer to the master server before you install the remote agent.

Solaris: Installation Scripts Fail in Bourne Shell (6568718)

If you run the Sun N1 Service Provisioning System scripts in a Bourne shell, the installation fails. An error message similar to the following is displayed.


cr_cli_solaris_sparc_pkg_6.0.sh: /: cannot execute
Usage: grep -hblcnsviw pattern file . . .

Workaround: Follow these steps.

  1. Assign execution permissions to the installer script.


    # chmod +x installer-script

    Where installer-script refers to the following scripts.

    • cr_ms_solaris_sparc_pkg_6.0.sh

    • cr_ms_solaris_x86__pkg_6.0.sh

    • cr_cli_solaris_sparc_pkg_6.0.sh

    • cr_cli_solaris_x86_pkg_6.0.sh

    • cr_ld_solaris_sparc_6.0.sh

    • cr_ld_solaris_x86_6.0.sh

    • cr_ra_solaris_sparc_6.0.sh

    • cr_ra_solaris_x86_6.0.sh

  2. Launch the installer.

    • For the master server, type the appropriate command.

      • For SPARC systems:


        # ./ksh cr_ms_solaris_sparc_pkg_6.0.sh

      • For x86 systems:


        # ./ksh cr_ms_solaris_x86_pkg_6.0.sh

    • For the CLI client, type the appropriate command.

      • For SPARC systems:


        # ksh cr_cli_solaris_sparc_pkg_6.0.sh

      • For x86 systems:


        # ksh cr_cli_solaris_x86_pkg_6.0.sh

    • For the local distributor, type the appropriate command.

      • For SPARC systems:


        # ksh cr_ld_solaris_sparc_6.0.sh

      • For x86 systems:


        # ksh cr_ld_solaris_x86_6.0.sh

    • For the remote agent, type the appropriate command.

      • For SPARC systems:


        # ksh cr_ra_solaris_sparc_6.0.sh

      • For x86 systems:


        # ksh cr_ra_solaris_x86_6.0.sh

N1 SPS Software Does Not Start After Reboot if SSL Connectivity Is Selected During Installation (6575906)

During the Sun N1 Service Provisioning System installation program, if you select an SSL selection, and select to reboot the host system after the installation, the N1 SPS software does not start after the reboot.

The following message is displayed in the /var/svc/log/application-management-spsra:default.log file.


Invalid password. The password has to be greater than 6 characters in length
Please enter the plaintext password for keystore:stty: : No such device or address

This issue occurs on systems that are running the Solaris OS or Linux operating systems.

Workaround: Choose the appropriate workaround.

Cannot Install in Root (/) Directory (6457372)

During the Sun N1 Service Provisioning System installation program, if you specify the root directory (/) as the installation location for Sun N1 Service Provisioning System, the installation fails. This failure occurs on the following platforms.

Workaround: Specify a non-root directory as the installation directory for the Sun N1 Service Provisioning System.

Solaris: PostgreSQL Database Does Not Start After Installation if Shared Memory Is Not Available (6562505)

If, after you install the Sun N1 Service Provisioning System, the system shared memory is not available, the PostgreSQL database does not start successfully. An error message similar to the following is displayed.


FATAL:  could not create shared memory segment: Invalid argument
DETAIL:  Failed system call was shmget(key=9001001, size=427900928, 03600).
HINT:  This error usually means that PostgreSQL's request for a shared memory segment 
exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or 
reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 
427900928 bytes), reduce PostgreSQL's shared_buffers parameter (currently 51200) 
and/or its max_connections parameter (currently 52).
        If the request size is already small, it's possible that it is less than 
your kernel's SHMMIN parameter, in which case raising the request size or 
reconfiguring SHMMIN is called for.
        The PostgreSQL documentation contains more information about shared memory 
configuration.
Error! Failed to start the postgres database using pg_ctl!

Workaround: Choose the appropriate workaround.

Solaris x86: Master Server Installation Fails on Systems With Patch 118855-30 (6567294)

If you install the N1 SPS master server on a Solaris 10 x86 system that has patch ID 118855-30 installed, the installation fails. The following error message is displayed.


Checking for required and recommended Solaris 5.10 patches.
        Patch 124631-03 is required for this installation and does not exist on
your system.
        Patch 120273-13 is required for this installation and does not exist on
your system.

Workaround: Add patches 124631-03 and 120273-13 or greater version, then reinstall the N1 SPS software on the master server.

Windows: Resource Check Ins Might Be Rejected (6396403)

Per a recent change in the way resource space is managed, the variable used to configure the Master Server resource repository size has changed in name and function. Therefore, the default configuration files need to be changed.

The new variable, rsrc.minMSRepoVolFreeSpace, specifies the minimum number of bytes of disk space that should remain available before further resource check ins are rejected. If a value is not given to rsrc.minMSRepoVolFreeSpace, the Master Server can use as much disk space as needed, up to the entire disk.

Workaround: On Windows Master Servers, manually delete configuration variable rsrc.maxMSRepoSize and add the new configuration variable rsrc.minMSRepoVolFreeSpace. Both variables pertain to the management of resource disk space on the Master Server.

Windows: Windows 2000 Installation Might Fail When Configuring HTTPS (6398475)

While installing the Sun N1 Service Provisioning System 6.0 Master Server on Windows, the installation fails when selecting the I Am Ready to Specify the HTTPS configuration now option. When choosing this option, the installer prompts for keystore file path and keystore password. The installation might fail by throwing the following error:

Error 1720: There is a problem with this windows installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.

The possible causes for this error are:

Workaround: To prevent an error, verify the following:

As an alternative, you can also select the I will specify the HTTPS configuration after the install option instead of the I am ready to specify the HTTPS configuration now option and perform keystore configuration later.

For more information, see Creating a Keystore File and Keystore Password for HTTPS Connections in Sun N1 Service Provisioning System 6.0 Installation Guide.

Problems Starting the Master Server on Solaris Systems That Do Not Meet Minimum System Configuration Requirements (6395197)

The N1 SPS Master Server uses the PostgreSQL database. PostgreSQL requires a shared memory segment when it is started. If the PostgreSQL's request for a shared memory segment exceeds available memory, then database startup fails with the following error message on the console:

Error! Failed to initialize the database (exit value was 1). Exiting..

The installation of the Master Server is incomplete. It can be removed by using the following command:

# pkgrm SUNWspsms SUNWspsc1

Also the db error log would contain a message similar to the following:

IpcMemoryCreate: shmget(key=5432001, size=426688512, 03600) failed: Not enough space

It is recommended, to stop all other processes that might be using shared memory during master server installation. If the master server could not be installed even after upgrading the physical RAM, refer to Chapter 11, Upgrading to the Sun N1 Service Provisioning System 6.0, in Sun N1 Service Provisioning System 6.0 Installation Guide. This chapter describes the steps required to migrate the Master Server from this machine to a different one that meets the minimum system requirements.

Workaround: The workaround for this issue is to increase the physical RAM on the system. The Master Server cannot be installed on systems that do not meet the minimal system configuration requirements.

The minimal system configuration requirements for Master Server are documented at Master Server Hardware Requirements in Sun N1 Service Provisioning System 6.0 Installation Guide.

Also, if Master Server installation was successful, but fails to start up due to shared memory constraints, the shared memory requirement of the Master Server could be reduced by using one, or both, of the following methods:

Windows: Installation Fails When User Does Not Have Correct Privileges or Incorrect Password Is Entered (6394017)

The user is installing a Master Server, Remote Agent, or Local Distributor on a Windows system. If the user chooses to run the Windows Service as Other Account, the user needs to provide a username that has Log on as a service privileges. If the user types an invalid password or the username does not have Log on as a service privileges, the installed services fail to start.

When the services fail to start, one of the following error messages is displayed:

This error occurs because the user typed an invalid password or the username does not have Log on as a service privileges. Username validation only validates the existence of the user on that computer. The credentials are not checked to see if the password is valid for that user or if the username has "Log on as a service" privileges.

Workaround: To prevent this error, implement one of the following workarounds:

Uninstallation Issues

This section describes known issues with uninstallation.

Side-by-Side Upgrade of a Windows Master Server Uninstall Fails (6188943)

When you are performing a side-by-side upgrade of a Windows Master Server, immediate uninstallation fails. Uninstallation might require manual intervention and reboot to complete.

Workaround: Stop the Master Server service from the Services application in the Windows Control Panel before running the Master Server uninstallation. After the uninstallation completes, the Master Server services are still present. Reboot the machine to remove the Master Server services entries in the Services application in the Windows Control Panel.

Uninstallation Window Displays Previous Sun N1 Service Provisioning System Version Value (6189043)

After upgrading a Sun N1 Service Provisioning System Windows version of the Local Distributor or Remote Agent to the next version, if you uninstall that Local Distributor or Remote Agent, the title of the uninstallation window displays the previous version.

Workaround: The uninstallation program proceeds properly. Ignore the erroneous title.

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.

Security Issues

Closing Web Browser With Multiple Web Browser Sessions Open Does Not Log Out of N1 SPS Session (6569108)

If you have two or more web browser sessions running on a system , and close a web browser session that is running the Sun N1 Service Provisioning System without logging out of the application, the same N1 SPS session can be accessed from an open web browser session.

Additionally, if the web browser software that you are using to run the Sun N1 Service Provisioning System software includes additional applications, such as an email client, these applications can also cause you N1 SPS session to remain active.

Workaround: Log out of your N1 SPS session by clicking the Log Out button in the browser interface.

Issues Interacting With the Windows 2000 Plug-In

This section describes known issues with the Windows 2000 plug-in.

Changing a Microsoft IIS Setting and Then Resetting It Might Result in Differences Being Found (6189034)

When performing model to install comparisons that include snapshots of IIS settings, if an IIS setting is changed and then changed back to its original value on the target server, comparison results might indicate differences when no difference exists. In particular, IIS metabase properties that are inherited from parent nodes, such as read/write web site permissions or default document settings, are prone to this behavior.

Workaround: Ignore the differences that are found in these cases.

Cannot Uninstall Windows IIS Application (6197564)

When you uninstall a Windows IIS Application, the Master Server browser interface displays that the uninstallation was successful. However, the COM+ applications are not completely removed. The COM+ applications remain in the Add/Remove Software Programs in the Control Panel.

Workaround: Manually remove the remaining COM+ applications.

To prevent this problem, when you install the application, increase the value of the shutdownDelaySecs variable.

Issues Interacting With the BEA WebLogic Plug-In

This section describes known issues with the WebLogic plug-in.

EJB Component Is Not Uninstalled (5109783)

If you run the default uninstall procedure for an EJB component that was deployed to more than one virtual WebLogic managed server and select only one of the managed servers to be uninstalled, the EJB component does not appear to be uninstalled from the managed server.

After the uninstall, if you click the tab on the WebLogic console for the managed server from which you uninstalled the EJB, the console correctly reports that the EJB is no longer deployed. Also, when you click the EJB tab, the console reports that the EJB is no longer targeted at the managed server from which it was uninstalled.

However, on the EJB tab, the console reports that the EJB is deployed on the managed server.

If you uninstall the EJB from all managed servers, the EJB is removed from the WebLogic console correctly.

Workaround: The WebLogic Plug-In is uninstalled correctly. Ignore the erroneous display.

Comparison Fails With Snapshot Error When WebLogic Application Was Deleted From the WebLogic Console (6186456)

If you deploy a WebLogic web application that contains a web application container with a WAR file and web application settings and include a snapshot and then delete the web application from the WebLogic Console, the following error displays if you run a model to install comparison on the web application component:


Could not complete operation on webapp domain.
No such webapp exists on domain /domain/. (310101)

The comparison should report a difference between the model and what is installed on the server. However, the comparison fails.

Workaround: No workaround is available.

Comparison Does Not Report Differences For Undeployed Components (6186457)

If you use the WebLogic Console to undeploy a WebLogic WAR or EJB component from a managed server or cluster, the WebLogic Console reports that the WAR or EJB component is still targeted to that managed server or cluster. Consequently, if you run a model to install comparison on the managed server or cluster, the comparison reports no differences. The model to install comparison checks the WebLogic Console and reports targeted applications as deployed.

Workaround: No workaround is available.

Comparison Results Incorrect for Content Changes Made to the On Disk Representation of WebLogic Application Archives (6196108)

If a WebLogic application is installed using the Sun N1 Service Provisioning System 6.0 and then content changes are made to the on disk WAR archive on the administration server, the changes are not reported in comparison results. The problem does not occur when configuration changes are made.

Workaround: Comparisons can be customized using the generate and prepare extensions with more capabilities to preprocess the on disk representation prior to running the comparison. This type of customization might require some advanced scripting.

SSL Connections to WebLogic Administration Servers Are Not Supported (6203385)

When setting up a WebLogic administration server in the Sun N1 Service Provisioning System 6.0, clicking the Secure checkbox will attempt to set up connectivity using SSL. This selection causes an error when attempting to perform actions that require access to the WebLogic administration server.

Workaround: Always setup WebLogic administration server connections with requiring SSL connectivity. Do not select the Secure checkbox.

Issues Interacting With the SAP Plug-In

This section describes known issues with the SAP plug-in.

Plans Fail If Master Server Is Not Prepared After Loading Plug-in ( 6392022)

If you import the SAP plug-in into your provisioning system, and then run SAP plug-in plans without preparing the master server, the plans fail. A message that is similar to the following error is displayed.


Problems encountered during plan run or preflight
The plan (or preflight) "/com/sun/sap/CreateGroupPlan" finished with 1 failed host(s).
(017034)
Cannot perform operation on component system service: com.sun.sap#UtilSS because it was
not installed on host cliHost (017057)
Unable to resolve installed component for system service: com.sun.sap#UtilSS. (602021)

Workaround: After you import the SAP plug-in, prepare the master server.

Localization Issues

This section describes issues encountered when using the Sun N1 Service Provisioning System 6.0 in locales other than the English locale.

Cannot Import Variable Sets That Include Non-ASCII Characters(6576425)

If you try to import a variable set that includes non-ASCII characters in the set name or details, the import fails.

Workaround: None.

Cannot Save or Check Out Plans or Components That Contain Non-ASCII Characters (6565638, 6576430)

If you use the browser user interface to try to save or download the XML file of a plan or component that includes non-ASCII characters, the operation fails.

Workaround: Use the command line interface to save or checkout plan or component XML that includes non-ASCII characters.

Search Pattern With Non-ASCII Latin-1 Characters Does Not Work Correctly (6302462)

In the Latin-1 locale environment, non-ASCII characters should not be used in the search pattern. For example, umlauts in German and accents in French. The desired match might not be in the returned set when the find operation is executed.

Workaround: Latin-1 locale users should not use non-ASCII characters as the input to the find command. Using non-ASCII characters might not return the desired result. Use only ASCII characters in these locales.

Locale Sensitive Sorting Is Not Supported

String–based data within the Sun N1 Service Provisioning System is sorted using the standard dictionary lexicon. Locale-specific collation is not performed. Consequently, accented versions of characters appear in a different position than the same unaccented characters.

Upgrade Issues

Solaris: Master Server Migration From N1 SPS 5.2 Release to N1 SPS 6.0 Release Fails (6546854)

If you migrate a master server from the N1 SPS 5.2 release to the N1 SPS 6.0 release, the migration fails under the following circumstances.

The following error message is displayed.


svcadm: svc:/application/management/spsms:default: Permission denied.

Workaround: Follow these steps.

  1. Add the following entry in the /etc/user_attr file.


    n1sps::::auths=solaris.smf.manage.spsms

  2. Add the following entry in the /etc/security/auth_attr file.


    solaris.smf.manage.spsms:::N1 SPS Master Server::help=

  3. In a terminal window, execute the following command.


    # /usr/sbin/usermod -A solaris.smf.manage.spsms n1sps

Update Hosts Progress Dialog Box Does Not Continuously Refresh (6383815)

If you click the Update Entire Host Network button during an upgrade of remote agents or local distributors where the database has thousands of hosts, the Update Host Progress dialog box might not continuously refresh. The dialog box provides the current status for approximately 20 minutes. Although the dialog box stops refreshing, the upgrade continues.

Workaround: Go to the Hosts List page and click the View Current Host Updates link.