DescriptionFrancesco Pantano
2020-07-27 07:54:12 UTC
Description of problem:
In the OSP integration context, when the dashboard is deployed using tls-everywhere framework,
the dashboard_protocol parameter is set to https.
This setting trigger the ceph-ansible tasks that are supposed to:
1. pass the generated certificates (defined using grafana_{key,crt} and dashboard_{key,crt}) to the dashboard related containers;
2. configure grafana to work with https
3. configure the Ceph Dashboard to point to the proper grafana url and load the appropriate key,crt via the Ceph existing commands
The process described above fails when a "copy" task of these files is executed.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 1Francesco Pantano
2020-07-27 09:32:17 UTC
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 (Red Hat Ceph Storage 4.1 Bug Fix update), 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-2020:4144
Description of problem: In the OSP integration context, when the dashboard is deployed using tls-everywhere framework, the dashboard_protocol parameter is set to https. This setting trigger the ceph-ansible tasks that are supposed to: 1. pass the generated certificates (defined using grafana_{key,crt} and dashboard_{key,crt}) to the dashboard related containers; 2. configure grafana to work with https 3. configure the Ceph Dashboard to point to the proper grafana url and load the appropriate key,crt via the Ceph existing commands The process described above fails when a "copy" task of these files is executed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: