Bug 1384622
Summary: | Add the client role to ceph-ansible | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Vasu Kulkarni <vakulkar> |
Component: | ceph-ansible | Assignee: | Sébastien Han <shan> |
Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
Severity: | unspecified | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | unspecified | ||
Version: | 2 | CC: | adeza, aschoen, ceph-eng-bugs, edonnell, gmeno, hnallurv, kdreyer, nthomas, sankarshan, seb, tchandra |
Target Milestone: | --- | ||
Target Release: | 2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-ansible-2.1.1-1.el7scon | Doc Type: | Enhancement |
Doc Text: |
.ceph-client role is now supported
The `ceph-ansible` utility now supports the `ceph-client` role. This new role enables you to copy the Ceph configuration file and administration keyring to node. In addition, you can use this role to create custom pools and clients.
For details, see the https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html-single/installation_guide_for_red_hat_enterprise_linux/#installing_the_ceph_client_role[Installing the ceph-client role] section in the Red Hat Ceph Storage 2 Installation Guide for Red Hat Enterprise Linux.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-14 15:51:16 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: | 1412948 |
Description
Vasu Kulkarni
2016-10-13 17:18:15 UTC
Ken, is it still time to push this in 1.0.5? If so, I can cherry-pick this. This should be resolved in ceph-ansible v2.1.1. The client role has been added as part of ceph-ansible. Verified in version: ceph-ansible-2.1.6-1.el7scon.noarch 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-2017:0515 |