Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1427248

Summary: [Docs][Upgrades] Re-run update after current operation(s) finished
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED EOL QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: high    
Version: 11.0 (Ocata)CC: dmacpher, jcoufal, lbezdick, lbopf, mburns, mcornea, srevivo, yprokule
Target Milestone: gaKeywords: Documentation, Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-22 12:30:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1394025    

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