Bug 1720921

Summary:	Provide ansible roles to Startup and Shutdown all vms
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	pasik, rhs-bugs
Target Milestone:	---	Keywords:	TestOnly
Target Release:	RHHI-V 1.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1720922 (view as bug list)		Environment:
Last Closed:	2020-02-13 15:57:20 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:	1720922
Bug Blocks:

Description Gobinda Das 2019-06-16 15:24:23 UTC

Description of problem:
Provide ansible role to support Startup and Shutdown all vms in rhhi environment

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 SATHEESARAN 2020-01-09 08:50:08 UTC

Tested with RHV 4.3.8 + RHGS 3.5.1 ( glusterfs-6.0-25.el7rhgs )

1. Deployed RHHI-V as a hosted-engine setup with 3 nodes
2. Gluster storage domains are created, backed with replica 3 gluster volumes
3. 15 VMs are created
4. All the VMs are shutdown using the playbook

<snip>
---
- name: oVirt shutdown environment
  hosts: localhost
  connection: local
  gather_facts: false

  vars:
    engine_url: https://hostedenginesm3.lab.eng.blr.redhat.com/ovirt-engine/api
    engine_user: admin@internal
    engine_password: redhat
    engine_cafile: /etc/pki/ovirt-engine/ca.pem

  roles:
    - ovirt.shutdown_env
</snip>

5. All the VMs are shutdown first and followed by shutdown of hosts.

Comment 6 errata-xmlrpc 2020-02-13 15:57:20 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0508