Bug 1601325
| Summary: | [ceph-ansible:iscsi] rbd-target-gw service is in failed state after the playbook run | ||||||
|---|---|---|---|---|---|---|---|
| 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: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.1 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, kdreyer, mchristi, nthomas, sankarshan, seb, tchandra, tserlin | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 3.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | RHEL: ceph-ansible-3.1.0-0.1.rc12.el7cp Ubuntu: ceph-ansible_3.1.0~rc12-2redhat1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-09-26 18:22:32 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: | |||||||
| Attachments: |
|
||||||
I do, alright no problem, good to know this is fixed :). This will be in upstream stable-3.2 which corresponds to RHCS 3.1. You can already find the patch in v3.2.0beta1 upstream tag. This is the first I've heard of intending to ship stable-3.2 in RHCS 3.1. That would be a big change from what the QE team has been testing so far for RHCS 3.1. How can we get this change into stable-3.1 instead? I discussed with Guillaume today on IRC. We prefer to re-target this BZ to RHCS 3.2 at this point, so that we don't destabilize stable-3.1 for this RFE. Created attachment 1470844 [details]
move rbd-target-gw startup
Can we do a simple fix in 3.1 like the attached patch?
Without a fix, the last parts of setup will fail and have to be manually run in each node.
That patch looks simple enough to me Mike. I recommend you submit a PR to GitHub against the stable-3.1 branch, so Sebastien can see it and approve it. Github PR for the less invasive fix for 3.1: https://github.com/ceph/ceph-ansible/pull/2944 Looks like the patch was merged into the 3.1 branch. Ken and Sebastien, can I go ahead and change this back to 3.1 instead of 3.2? I just tagged rc12. https://github.com/ceph/ceph-ansible/releases/tag/v3.1.0rc12 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 |
Hey Sebastien, Do you handle both upstream and downstream for ceph-ansible? Assigning this back to you because this looks like it is fixed in the current upstream code in this commit: commit 91bf53ee932a6748c464bea762f8fb6f07f11347 Author: Sébastien Han <seb> Date: Fri Mar 23 11:24:56 2018 +0800 ceph-iscsi: support for containerize deployment so we only need to bring part of that patch in downstream. The problem is rbd-target-gw needs the rbd pool to be created, keyring to be copied over, and the iscsi-gateway.cfg to be setup before starting the rbd-target-gw service. As you know in your patch for container support you moved that setup to common.yml and executed it before prerequisites.yml, so that fixes the problems we hit in this bz.