Bug 1575829
| Summary: | [RFE] Support iscsi-gws upgrade through rolling update | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manohar Murthy <mmurthy> |
| Component: | Ceph-Ansible | Assignee: | Sébastien Han <shan> |
| Status: | CLOSED ERRATA | QA Contact: | Manohar Murthy <mmurthy> |
| Severity: | high | Docs Contact: | John Brier <jbrier> |
| Priority: | high | ||
| Version: | 3.1 | CC: | adeza, agunn, aschoen, ceph-eng-bugs, gmeno, hnallurv, jbrier, nthomas, rperiyas, sankarshan, shan, tchandra, tserlin |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-ansible-3.1.0-0.1.rc17.el7cp Ubuntu: ceph-ansible_3.1.0~rc17-2redhat1 | Doc Type: | Enhancement |
| Doc Text: |
.Support for iSCSI gateway upgrades through rolling updates
Previously, when using a Ceph iSCSI gateway node, `iscsi-gws` could not be updated by `ceph-ansible` during a rolling upgrade. With this update to {product}, `ceph-ansible` now supports upgrading `iscsi-gws` using the `rolling_update.yml` Ansible playbook.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-26 18:20:21 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: | |||
| Bug Blocks: | 1584264 | ||
|
Comment 7
Sébastien Han
2018-08-06 12:48:47 UTC
(In reply to leseb from comment #7) > Thomas, we are testing the backport upstream, thanks for the reminder. When can we expect the build with this fix in 3.1? 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 |