Bug 1537445
| Summary: | [RFE] Support cephmetrics installation using the ansible user | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Madhavi Kasturi <mkasturi> |
| Component: | Ceph-Metrics | Assignee: | Zack Cerza <zcerza> |
| Status: | CLOSED ERRATA | QA Contact: | Sidhant Agrawal <sagrawal> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.5 | CC: | agunn, branto, ceph-eng-bugs, gmeno, hnallurv, jbautist, jbrier, kdreyer, mamccoma, mhackett, prsurve, rperiyas, zcerza |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cephmetrics-2.0-3.el7cp | Doc Type: | Enhancement |
| Doc Text: |
.Installation of {product} Dashboard using the `ansible` user
Previously, installing {product} Dashboard (cephmetrics) with Ansible required root access. Traditionally, Ansible uses passwordless ssh and sudo with a regular user to install and make changes to systems. In this release, the {product} Dashboard can be installed with `ansible` using a regular user. For more information on the {product} Dashboard, see the link:{admin-guide}#installing-the-red-hat-ceph-storage-dashboard-management[Administration Guide].
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-26 18:18:23 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: | 1356451, 1584264 | ||
|
Description
Madhavi Kasturi
2018-01-23 08:39:44 UTC
We should not be telling users that they need to be root to run ansible! Our playbooks work normally as non-root; in fact, that is the only way I've ever executed them. this should be fixed by the docs change, moving to ON_QA *** Bug 1526605 has been marked as a duplicate of this bug. *** 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 |