Bug 1427248 - [Docs][Upgrades] Re-run update after current operation(s) finished
Summary: [Docs][Upgrades] Re-run update after current operation(s) finished
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 11.0 (Ocata)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks: 1394025
TreeView+ depends on / blocked
 
Reported: 2017-02-27 17:00 UTC by Yurii Prokulevych
Modified: 2020-08-24 05:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-22 12:30:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Yurii Prokulevych 2017-02-27 17:00:50 UTC 
Description of problem:
-----------------------
If the update command is aborted for some reason you can always continue in the process by re-running same command. 

Problem is that already started command is not interrupted and attempt to re-run update immediately after cancel will fail, cuz there is already update in progress.
So before re-running update check there is no actions in progress.

Lukas, please correct the text message if I'm missing smth.
Comment 1 Lukas Bezdicka 2017-02-28 11:09:14 UTC 
Id add how to check that there are no actions in progress.

openstack stack resource-list -n5 overcloud | grep -v COMPLETE or something like that
Comment 8 Scott Lewis 2018-06-22 12:30:39 UTC 
OSP11 is now retired, see details at https://access.redhat.com/errata/product/191/ver=11/rhel---7/x86_64/RHBA-2018:1828
Note You need to log in before you can comment on or make changes to this bug.