Bug 1624417
Summary: | rados index object creation assumes rados command available on the baremetal node | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Giulio Fidente <gfidente> |
Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.1 | CC: | agunn, anharris, aschoen, ceph-eng-bugs, gabrioux, gfidente, gmeno, hnallurv, jbrier, kdreyer, nthomas, sankarshan, shan, yrabl |
Target Milestone: | rc | ||
Target Release: | 3.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
.RADOS index object creation no longer assumes rados command available on the baremetal
Previously, the creation of the rados index object in `ceph-ansible` assumed the `rados` command was available on the bare metal node, but that is not always true when deploying in containers. This can cause the task which starts NFS to fail because the `rados` command is missing on the host. With this update to {product} the Ansible playbook runs `rados` commands from the Ceph container instead during containerized deployment.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-06 17:11:43 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: | 1553640, 1584264 |
Description
Giulio Fidente
2018-08-31 14:04:35 UTC
The latest GA version of ceph-ansible is ceph-ansible-3.1.5-1.el7cp, from https://access.redhat.com/errata/RHBA-2018:2819 |