Setting a reboot for an object

Using the BLPackage editor, you can specify a reboot for an object in a package.

This procedure allows you to specify a reboot for any server running any operating system.

This procedure also lets you indicate that an object being deployed includes instructions for a reboot, and those instructions are not part of the BLPackage instructions. This kind of reboot is called out-of-band. It is important to note any requirements for out-of-band reboots. If you do not, a reboot might occur while another Deploy Job is processing, which could leave a server in an unreliable state.

When a job requires a reboot, the job must run in single-job mode, which means only the current job can be processed. Other Deploy Jobs must wait. Forcing a Deploy Job into single-job mode prevents a job from rebooting a server while other Deploy Jobs are also being processed. When a server reboots, the job that caused the reboot is processed first when the server starts up again. All other jobs, whether they are existing or new jobs, wait to process until the rebooting job completes.

This procedure allows you to specify that servers perform a reconfiguration reboot after deploying an object. A reconfiguration reboot, which only applies to Oracle Solaris servers, is required for some new hardware and for some software patches.

To set a reboot for an object

  1. In the hierarchy view, select an object included in the BLPackage.
    On the right you see the attributes associated with that object.
  2. In the right pane, for Reboot, select one of the following:
    • Not required — No reboot is required. This is the default setting.
    • After item deployment — Reboot after this object is deployed. You can override this setting using Deploy Job options.
    • After item deployment with reconfiguration (Solaris ONLY) — After this object is deployed, perform a Solaris reconfiguration reboot. If the target server is not a Solaris machine and you select this option, a normal reboot occurs. You can override this setting using Deploy Job options.
    • Out-of-band — This object includes instructions for a reboot, but that reboot is not included in the instructions for a Deploy Job. When deploying a software package, if an out-of-band reboot does not occur, the job completes successfully but generates warnings. If you select this option, any Deploy Job used to deploy this package is automatically defined to use single-job mode. Also, rollback information is be created for this object, assuming rollback is enabled.
    • By end of job — A reboot is required, but not immediately. The reboot requirement is satisfied the next time a target server reboots. If no reboots occur before the end of the job, the server reboots then.
    • By end of job with reconfiguration (Solaris ONLY) — A Solaris reconfiguration reboot is required, but the reboot should not occur immediately. Instead, the next time the target server needs to reboot, a reconfiguration reboot is performed. If no reboots are required before the end of the job, the server performs a reconfiguration reboot then. If the target server is not a Solaris machine and you select this option, a normal reboot occurs. You can override this setting using Deploy Job options.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*