Bug 1659611
| Summary: | ceph ansible rolling upgrade does not restart tcmu-runner and rbd-target-api | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Mike Christie <mchristi> |
| Component: | Ceph-Ansible | Assignee: | Dimitri Savineau <dsavinea> |
| Status: | CLOSED ERRATA | QA Contact: | Yogesh Mane <ymane> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.5 | CC: | agunn, aschoen, ceph-eng-bugs, dsavinea, edonnell, gmeno, gsitlani, jdillama, nthomas, sankarshan, tchandra, tserlin, vashastr, ymane |
| Target Milestone: | rc | ||
| Target Release: | 3.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-ansible-3.2.16-1.el7cp Ubuntu: ceph-ansible_3.2.16-2redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
.The `rolling_update.yml` playbook now restarts `tcmu-runner` and `rbd-target-api`
Previously, the iSCSI gateway infrastructure playbooks, specifically `rolling_update.yml`, only restarted the `rbd-target-gw` daemon. With this update, the playbook also restarts the `tcmu-runner` and `rbd-target-api` daemons so the updated versions of those daemons are used.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-21 15:10:24 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: | 1726135 | ||
|
Description
Mike Christie
2018-12-14 19:27:18 UTC
Hey Dimitry, We will need the fix here too: https://github.com/ceph/ceph-ansible/pull/3954 Hi Mike, I'm saw the PR and it looks good to me. I just need you to update the commit message and we should be good to merge and backport it. 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 |