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.
Make sure you use the -i parameter, otherwise update runs on background and does not prompt for removing of breakpoints.
Multiple breakpoints can be removed by specifying list of nodes with a regular expression.
If the update command is aborted for some reason you can always continue in the process by re-running same command.
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.