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

Bug 1373354

Summary: RFE: 'nova pause' should be able to pause multiple servers at once
Product: Red Hat OpenStack Reporter: Pavel Raiskup <praiskup>
Component: python-novaclientAssignee: Eoghan Glynn <eglynn>
Status: CLOSED WONTFIX QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, dasmith, eglynn, jruzicka, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---Keywords: EasyFix, FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-26 21:55:14 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:

Description Pavel Raiskup 2016-09-06 05:18:58 UTC 
ATM, the 'nova pause' command (in contrast with 'delete' commnand) accepts
only one VM identificator.
Comment 2 Sahid Ferdjaoui 2016-09-06 07:45:45 UTC 
Nova does not provide public API to request multiple pauses at once. That feature have to be implemented following same pattern as the command nova delete in python novaclient.
Comment 4 Stephen Gordon 2017-01-26 21:55:14 UTC 
While this might be nice to have, it's not a priority and is easily worked around using basic shell commands.
Comment 5 Pavel Raiskup 2017-01-27 11:16:13 UTC 
That was meant to be RFE.  No deadline required.  Is this correct way to
submit RFE's?
Comment 6 Stephen Gordon 2017-01-30 14:12:43 UTC 
(In reply to Pavel Raiskup from comment #5)
> That was meant to be RFE.  No deadline required.  Is this correct way to
> submit RFE's?

It is, but we have ~100 open RFEs for compute-related functionality and this is an extremely low priority request with valid alternative workflows to achieve the same result. I updated the status to accurately reflect that we do not expect to get to this.