Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1802814

Summary: Ceph manila keys are created and added to the auth list of Ceph even when not deploying Manila
Product: Red Hat OpenStack Reporter: Darin Sorrentino <dsorrent>
Component: openstack-tripleo-heat-templatesAssignee: Francesco Pantano <fpantano>
Status: CLOSED ERRATA QA Contact: Nathan Weinberg <nweinber>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.0 (Train)CC: fpantano, gfidente, gouthamr, hbrock, jslagle, mburns, moddi, vimartin
Target Milestone: z2Keywords: Triaged
Target Release: 16.0 (Train on RHEL 8.1)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-0.20200324120625.c3a8eb4.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-14 12:15:31 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:

Description Darin Sorrentino 2020-02-13 22:51:22 UTC
Description of problem:

When deploying an overcloud that includes a Ceph deployment, the /etc/ceph/ceph.client.manila.keyring is being created and the client is being added to the auth list with permissions that are not scoped to specific pools:

'caps': {'mgr': 'allow *', 'mon': 'allow rw', 'osd': 'allow rwx'}

This client should not be created if not deploying manila


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Darin Sorrentino 2020-02-13 22:52:09 UTC
Sorry, if I wasn't clear in the description, Manila is NOT being deployed in this scenario but the client is created anyway.

Comment 11 errata-xmlrpc 2020-05-14 12:15:31 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, 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:2114