Bug 1621255 – [iscsi] purge-iscsi-gateways.yml should disable/stop all the iscsi services

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1621255 - [iscsi] purge-iscsi-gateways.yml should disable/stop all the iscsi services

Summary:	[iscsi] purge-iscsi-gateways.yml should disable/stop all the iscsi services

Status:	ON_QA

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	Ceph-Ansible (Show other bugs)
Sub Component:
Version:	3.1
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	rc
Target Release:	3.2
Assigned To:	Mike Christie
QA Contact:	Manohar Murthy
Docs Contact:	Bara Ancincova

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1629656 1584264
	Show dependency tree / graph

Reported:	2018-08-23 10:37 EDT by mkasturi
Modified:	2018-10-25 12:21 EDT (History)
CC List:	15 users (show)

See Also:
Fixed In Version:	RHEL: ceph-ansible-3.2.0-0.1.beta9.el7cp Ubuntu: ceph-ansible_3.2.0~beta9-2redhat1
Doc Type:	Known Issue
Doc Text:	.Running the Ansible playbook, `purge-iscsi-gateways.yml` does not stop and disable the iSCSI gateway services When purging the Ceph iSCSI gateways using Ceph Ansible, the iSCSI gateway services are still running. You must manually stop and disable these services by doing the following as `root`: ---- systemctl stop rbd-target-api systemctl stop rbd-target-rbd systemctl stop tcmu-runner systemctl disable rbd-target-api systemctl disable rbd-target-rbd systemctl disable tcmu-runner ---- If you are using the `gwcli` command to manage the iSCSI gateways, then do not stop or disable these services.
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	ceph/ceph-ansible/pull/3116	None	None	None	2018-10-02 13:14 EDT

Groups: None (edit)

Comment 6 leseb 2018-10-25 07:07:57 EDT

Present in https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0beta9

For the BZ, I believe it's better if you keep the assignment so if QA finds something then you will be alerted.
So if you fix something upstream in master AND backported in a stable branch AND a release (e,g: https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0beta9) has the fix then you can the BZ to POST :).

Sounds good?
Thanks!

Note You need to log in before you can comment on or make changes to this bug.