Bug 1651054 - [iSCSI-container] - After cluster purge and recreation, iSCSI target creation failed.
Summary: [iSCSI-container] - After cluster purge and recreation, iSCSI target creation...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 3.3
Assignee: Guillaume Abrioux
QA Contact: Manohar Murthy
Aron Gunn
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2018-11-19 04:15 UTC by Manohar Murthy
Modified: 2019-08-21 15:10 UTC (History)
18 users (show)

Fixed In Version: RHEL: ceph-ansible-3.2.0-0.1.rc8.el7cp Ubuntu: ceph-ansible_3.2.0~rc8-2redhat1
Doc Type: Enhancement
Doc Text:
.Removing iSCSI targets using Ansible Previously, the iSCSI targets had to be removed manually before purging the storage cluster. Starting with this release, the `ceph-ansible` playbooks remove the iSCSI targets as expected. For bare-metal Ceph deployments, see the _Removing the Configuration_ section in the the {product} {release} link:{block-dev-guide}#configuring_the_iscsi_target_using_ansible[Block Device Guide] for more details. For Ceph container deployment, see the {product} {release} link:{container-guide}#removing-the-ceph-iscsi-gateway-in-a-container-container[Container Guide] for more details.
Clone Of:
: 1658299 (view as bug list)
Environment:
Last Closed: 2019-08-21 15:10:24 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 3395 0 'None' closed purge: add iscsi support 2020-02-25 04:09:33 UTC
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:10:49 UTC

Comment 11 seb 2018-11-29 11:05:48 UTC 
Changing component to ceph-ansible
Comment 12 seb 2018-12-04 17:06:57 UTC 
In https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0rc8
Comment 44 errata-xmlrpc 2019-08-21 15:10:24 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/RHSA-2019:2538
Note You need to log in before you can comment on or make changes to this bug.