N1 Grid Service Provisioning System 5.0 Release Notes

Runtime Issues

This section describes known runtime issues.

Check In Current Does Not Report Errors for Components That Do Not Support Check In Current (5063014)

The Check In Current operation enables you to ensure that the version of a component in the Master Server repository is the most recent. The Master Server checks its version of the component against the version on the source host. The check is based on metadata regarding the location of the component that was gathered at the time of previous check in.

You cannot perform the Check In Current operation on all component types. Typically, component types that can be browsed using the browser interface are eligible for the Check In Current operation.

When performing a bulk Check In Current operation, if you select a component type that does not support the Check In Current operation, the operation completes with no errors. The results displayed in the Progress dialog box for component types that are not supported might be empty or might represent historical data.

Workaround: No workaround is available.

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

If you are running the N1 Grid 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:

Red Hat plans to include a patch in Update 3 to correct the problem. Apply the patch from Red Hat to your system when the patch is available. For more information about the Red Hat patch, see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=117218.
Do not use SSL as a connection type. Choose TCP/IP or SSH.
Remove /dev/random and replace it with a symbolic link to /dev/urandom. /dev/urandom is less secure than /dev/random but the system does not hang when the provisioning system attempts an SSL connection on Red Hat Linux Advanced Server 3.0.

Error When Importing a File From the Plug-Ins Page (5103015)

From the browser interface on the Plug-Ins page, if you attempt to import a file that is larger than 40 MBytes, the import fails.

Workaround: To import plug-in files larger than 40 MBytes, use the plg.p.add command from the CLI Client . For instructions, see Chapter 11, plg: CLI Commands for Plug-ins, in N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual.

Unable to Bulk Delete All Versions of a Simple Component (6173519)

If you create a new file component using the browser interface and perform a Check In Current operation on the component to create version 1.1, if you attempt to delete both versions of the component at the same time, the following error message displays:

The 1.0 version of the object cannot be deleted as long as other versions
of the same object exist.

Workaround: Do not use bulk delete to delete the two components. Delete the components individually.

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.

Some Master Server APIs Do Not Verify Permissions (6199565)

Some APIs that are available on the Master Server do not check for any permissions. Without permission checks, an unauthenticated user might invoke these services and possibly compromise the Master Server.

Workaround: You can set up the Master Server and CLI Clients to prevent unauthorized access. The following security options are available for the Master Server and the CLI Clients:

Configure the Master Server to use SSL to connect to the CLI Clients.
Install the CLI Client on servers that are accessible only to users who are authorized to access the N1 Grid Service Provisioning System.
On Solaris OS, Red Hat Linux, and IBM AIX servers, install the CLI Client within a user group that contains only authorized provisioning system users as its members.
Set the permissions for the CLI Client private keystore in N1SPS5.0-CLI-home/cli/data/private.store to 640. This permissions setting allows only authorized provisioning system users access to the CLI Client private keys to be able to connect to the Master Server.
On Windows 2000 systems, ensure that the CLI Client private keystore has read permissions granted only to authorized provisioning system users.

Restore Fails if Master Server Path Different Between Backup and Restore (6201207)

If you attempt to restore data to a Master Server that is installed in a different path than the path to the Master Server that you used to create the backup file, the restore fails. The following message appears:

ERROR!  Failed to restore the database successfully.
The following fatal errors were encountered
ERROR:  stat failed on file 'N1SPS5.0-MS-home/': No such file or directory

N1SPS5.0-MS-home is the home directory of the Master Server that you used to create the backup.

Workaround: On the server where you want to restore the Master Server data, reinstall the Master Server into the same directory as the Master Server that you used to create the backup.