Bug 1619167 - [iscsi-ansible] iscsigws.yml should be iscsi-gws.yml
Summary: [iscsi-ansible] iscsigws.yml should be iscsi-gws.yml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 3.1
Assignee: Sébastien Han
QA Contact: Madhavi Kasturi
URL:
Whiteboard:
Depends On: 1622210
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-20 08:48 UTC by Madhavi Kasturi
Modified: 2018-09-26 18:24 UTC (History)
7 users (show)

Fixed In Version: RHEL: ceph-ansible-3.1.0-0.1.rc19.el7cp Ubuntu: ceph-ansible_3.1.0~rc19-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-26 18:23:45 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 3041 0 None None None 2018-08-20 14:02:57 UTC
Red Hat Product Errata RHBA-2018:2819 0 None None None 2018-09-26 18:24:47 UTC

Comment 8 Sébastien Han 2018-08-23 11:24:07 UTC
We already have this: https://github.com/ceph/ceph-ansible/blob/stable-3.1/infrastructure-playbooks/purge-iscsi-gateways.yml#L25

All the playbooks now look for either iscsigws or iscsi-gws, so if iscsi-gws.yml exists, this should work.

Not sure to understand the problem now.
We are not going to replace the default template iscsigws.yml.sample.

Thanks.

Comment 10 Sébastien Han 2018-08-23 14:01:29 UTC
Hi,

Moving forward we will have iscsigws.yml.sample.
As I said, all the playbooks are configured to look for both iscsigws and iscsi-gws host sections. So if your "old" install had a section [iscsi-gws], it'll still work, as well as your iscsi-gws.yml, you just need to merge your iscsi-gws.yml with the new iscsigws. yml if you want to get the latest config options. But that's not different from any updates.

Does that clarify? Or am I missing something?
Thanks

Comment 13 errata-xmlrpc 2018-09-26 18:23:45 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-2018:2819


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