
The update command no longer requires --templates and --environment-file args. This reflects that change in the docs. Change-Id: I98416a1eda647d2725ce960b7f70a8392c9d9c93 Depends-On: I8aa6262716534dec7b51e64f491d7131c359f802
1.3 KiB
Updating Packages on Overcloud Nodes
You can update packages on all overcloud nodes with a command similar to the following:
openstack overcloud update stack -i overcloud
This command updates the UpdateIdentifier
parameter and
triggers stack update operation. If this parameter is set,
yum update
command is executed on each node. Because
running update on all nodes in parallel might be unsafe (an update of a
package might involve restarting a service), the command above sets
breakpoints on each overcloud node so nodes are updated one by one. When
the update is finished on a node the command will prompt for removing
breakpoint on next one.
Note
Make sure you use the -i
parameter, otherwise update
runs on background and does not prompt for removing of breakpoints.
Note
Multiple breakpoints can be removed by specifying list of nodes with a regular expression.
Note
If the update command is aborted for some reason you can always continue in the process by re-running same command.
Note
The --templates and --environment-file (-e) are now deprecated. They can still be passed to the command, but they will be silently ignored. This is due to the plan now used for deployment should only be modified via plan modification commands.