N1 Grid Service Provisioning System User's Guide and Release Notes for the OS Provisioning Plug-In 1.0

Runtime Issues

The following issues are known to exist when provisioning operating systems.

Solaris: Wrong Encryption of root Password Causes JumpStart Error (6245964)

Description: You see the following messages during installation and the installation becomes interactive:

root_password=Clz6pK2b6qw=
	syntax error  line 2 position 15

The password variable sysidcfg_root_password_base_conf in the Solaris OS profile has a encrypted value. However, the password that you supplied was not a Solaris-encrypted password..

Workaround: Use the Solaris tools to encrypt the password. The appropriate mechanism for a user to create an encrypted password is to create a user with a password. Look in the /etc/shadow file for the encrypted password and use it in as a value for the sysidcfg_root_password_base_conf variable.

Solaris: RA Installer Uses Value of HostName Instead of Target `sps_ra_host` (6255081)

Description: If the OS profile has the value install_ra_from_snapshot_spsra="n", the N1 Grid SPSRemote Agent (RA) listens on the IP address specified by the host name rather than the IP address specified in the variable sps_ra_host. In this case, when the RA starts, the transport.config uses the host name of the system rather than the value specified in sps_ra_host.

Workaround: Create and use a snapshot rather than the RA installer. Follow these steps:

Create an RA snapshot. For example, on a Solaris x86 system on which the N1 Grid SPS 5.0 RA is installed, use these commands:

#cd /opt/SUNWn1sps/N1_Grid_Service_Provisioning_System
  #cat > /tmp/exclude
  ./agent/data
  <control-D EOF>
  #tar cvf /tmp/exclude ./agent ./common > /tmp/sps_ra_solaris_x86_5.0.tar

Import the snapshot to the JET server, as explained in How to Import N1 Grid SPS RA Installers.

Note –
The media path should point to a directory reachable from JET Server that contains the tar file that you created in the previous step.

Unable to Change Location of OS Provisioning Scripts on Windows Boot and Install Server (6251010)

Description: You cannot change the OS provisioning script location for a Windows boot and install server once the Windows boot and install server is created.

Workaround: Recreate a new Windows boot and install server that has a different name.

Solaris 10 Installation on Target Host Requires User Response (6245773)

Description: If a time server cannot be reached during installation, the installation becomes interactive. During installation, if the time server was not specified, the sysidcfg file uses the “Solaris 10 Jet Server” as the time server. On Solaris 10 systems, the boot and install servers do not start the time services by default.

Workaround: There are two ways to resolve this issue.

Start the time service on the Solaris 10 JET server manually. Type the following command:
# svcadm enable time:stream
Specify a valid time server (for example, use the address of the OS provisioning server).

Warnings for DHCP Settings Are Not Reported to the User Interface (6248485)

Description: The provisioning operation fails because the DHCP settings are incorrect. There is no message shown in stdout or stderr.

Workaround: The incorrect settings cause the OS provisioning subnet to be created with wrong values. Look at the /var/adm/n1osp* log files on the OS provisioning server for the DHCP error.

JET Attach Fails Because `osp_pkgchk.sh` File Does Not Exist (6257748)

Workaround: Install the jet utilities tar file on the JET server physical host prior to the JET server attach.

In the N1 Grid SPS browser interface, follow these steps:

In the Common Tasks section of the N1 Grid SPS browser interface, select OS Provisioning.
On the OS Provisioning Common Tasks page, click Manage in the JET Solaris Image Servers section.
Select the referenced component /com/sun/n1osp/resource/jet_util.tar.
On the Component Details page, click the Run action next to the default:install procedure.
Select the physical target host name on which the JET server is installed.
Click Run Plan (includes preflight).

Cannot View OS Installation Log by Host Provision Status in Non-EUC Locale (6255797)

Description: Installation log files are always in related EUC locale regardless of the specified locale for the OS installation. When the remote agent locale is different from this EUC locale, you cannot view the log file correctly through the Status Monitoring page because the locales do not match.

Workaround: Connect to service port or console (if applicable) with proper locale to view the log files directly.