Bug 1619167
| Summary: | [iscsi-ansible] iscsigws.yml should be iscsi-gws.yml | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Madhavi Kasturi <mkasturi> |
| Component: | Ceph-Ansible | Assignee: | Sébastien Han <shan> |
| Status: | CLOSED ERRATA | QA Contact: | Madhavi Kasturi <mkasturi> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.1 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, hnallurv, nthomas, sankarshan |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-26 18:23:45 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: | 1622210 | ||
| Bug Blocks: | |||
|
Comment 3
Sébastien Han
2018-08-20 22:07:57 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. 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 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 |