reboot Resource
This page is generated from the Chef Infra Client source code.To suggest a change, edit the reboot.rb file and submit a pull request to the Chef Infra Client repository.
Use the reboot resource to reboot a node, a necessary step with some installations on certain platforms. This resource is supported for use on the Microsoft Windows, macOS, and Linux platforms. In using this resource via notifications, it’s important to only use immediate notifications. Delayed notifications produce unintuitive and probably undesired results.
New in Chef Infra Client 12.0.
Syntax
The full syntax for all of the properties that are available to the reboot resource is:
reboot 'name' do delay_mins Integer # default value: 0 reason String # default value: "Reboot by Chef Infra Client" action Symbol # defaults to :nothing if not specified endwhere:
rebootis the resource.nameis the name given to the resource block.actionidentifies which steps Chef Infra Client will take to bring the node into the desired state.delay_minsandreasonare the properties available to this resource.
Actions
The reboot resource has the following actions:
:cancel- Cancel a pending reboot request.
:nothing- This resource block doesn’t act unless notified by another resource to take action. Once notified, this resource block either runs immediately or is queued up to run at the end of a Chef Infra Client run. (default)
:reboot_now- Reboot a node so that the Chef Infra Client may continue the installation process.
:request_reboot- Reboot a node at the end of a Chef Infra Client run.
Properties
The reboot resource has the following properties:
delay_mins- Ruby Type: Integer | Default Value:
0The amount of time (in minutes) to delay a reboot request.
reason- Ruby Type: String | Default Value:
Reboot by Chef Infra ClientA string that describes the reboot action.
Common Resource Functionality
Chef resources include common properties, notifications, and resource guards.
Common Properties
The following properties are common to every resource:
compile_timeRuby Type: true, false | Default Value:
falseControl the phase during which the resource is run on the node. Set to true to run while the resource collection is being built (the
compile phase). Set to false to run while Chef Infra Client is configuring the node (theconverge phase).ignore_failureRuby Type: true, false, :quiet | Default Value:
falseContinue running a recipe if a resource fails for any reason.
:quietwon’t display the full stack trace and the recipe will continue to run if a resource fails.retriesRuby Type: Integer | Default Value:
0The number of attempts to catch exceptions and retry the resource.
retry_delayRuby Type: Integer | Default Value:
2The delay in seconds between retry attempts.
sensitiveRuby Type: true, false | Default Value:
falseEnsure that sensitive resource data isn’t logged by Chef Infra Client.
Notifications
notifiesRuby Type: Symbol, 'Chef::Resource[String]'
A resource may notify another resource to take action when its state changes. Specify a
'resource[name]', the:actionthat resource should take, and then the:timerfor that action. A resource may notify more than one resource; use anotifiesstatement for each resource to be notified.If the referenced resource doesn’t exist, an error is raised. In contrast,
subscribeswon’t fail if the source resource isn’t found.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate,:immediatelySpecifies that a notification should be run immediately, for each resource notified.
The syntax for notifies is:
notifies :action, 'resource[name]', :timer subscribesRuby Type: Symbol, 'Chef::Resource[String]'
A resource may listen to another resource, and then take action if the state of the resource being listened to changes. Specify a 'resource[name]', the :action to be taken, and then the :timer for that action.
Note that subscribes doesn’t apply the specified action to the resource that it listens to - for example:
file '/etc/nginx/ssl/example.crt' do mode '0600' owner 'root' end service 'nginx' do subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately end In this case the subscribes property reloads the nginx service whenever its certificate file, located under /etc/nginx/ssl/example.crt, is updated. subscribes doesn’t make any changes to the certificate file itself, it merely listens for a change to the file, and executes the :reload action for its resource (in this example nginx) when a change is detected.
If the other resource doesn’t exist, the subscription won’t raise an error. Contrast this with the stricter semantics of notifies, which will raise an error if the other resource doesn’t exist.
A timer specifies the point during a Chef Infra Client run at which a notification is run. The following timers are available:
:beforeSpecifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayedDefault. Specifies that a notification should be queued up, and then executed at the end of a Chef Infra Client run.
:immediate,:immediatelySpecifies that a notification should be run immediately, for each resource notified.
The syntax for subscribes is:
subscribes :action, 'resource[name]', :timer Guards
A guard property can be used to evaluate the state of a node during the execution phase of a Chef Infra Client run. Based on the results of this evaluation, a guard property is then used to tell Chef Infra Client if it should continue executing a resource. A guard property accepts either a string value or a Ruby block value:
- A string is executed as a shell command. If the command returns
0, the guard is applied. If the command returns any other value, then the guard property isn’t applied. String guards in a powershell_script run Windows PowerShell commands and may returntruein addition to0. - A block is executed as Ruby code that must return either
trueorfalse. If the block returnstrue, the guard property is applied. If the block returnsfalse, the guard property isn’t applied.
A guard property is useful for ensuring that a resource is idempotent by allowing that resource to test for the desired state as it’s being executed, and then if the desired state is present, for Chef Infra Client to do nothing.
PropertiesThe following properties can be used to define a guard that’s evaluated during the execution phase of a Chef Infra Client run:
not_ifPrevent a resource from executing when the condition returns
true.only_ifAllow a resource to execute only if the condition returns
true.
Examples
The following examples demonstrate various approaches for using the reboot resource in recipes:
Reboot a node immediately
reboot 'now' do action :nothing reason 'Cannot continue Chef run without a reboot.' delay_mins 2 end execute 'foo' do command '...' notifies :reboot_now, 'reboot[now]', :immediately end Reboot a node at the end of a Chef Infra Client run
reboot 'app_requires_reboot' do action :request_reboot reason 'Need to reboot when the run completes successfully.' delay_mins 5 end Cancel a reboot
reboot 'cancel_reboot_request' do action :cancel reason 'Cancel a previous end-of-run reboot request.' end