Chapter 2 Release Notes for OS Provisioning Plug-In

This chapter describes late-breaking news and known issues with the OS provisioning plug-in.

The chapter contains the following information:

• Installation Issues

• Runtime Issues

Installation Issues

There are no known installation issues.

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.

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.

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.

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.