Bug 1590275

Summary: Pool application tags are not applied unless supplied
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Giulio Fidente <gfidente>
Component: Ceph-AnsibleAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact:
Priority: low    
Version: 3.1CC: anharris, aschoen, ceph-eng-bugs, ceph-qe-bugs, gabrioux, gcharot, gmeno, hnallurv, kdreyer, nthomas, sankarshan, tserlin
Target Milestone: rc   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.1.0-0.1.rc10.el7cp Ubuntu: ceph-ansible_3.1.0~rc10-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-26 18:21:59 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: 1578730    

Description Giulio Fidente 2018-06-12 10:51:11 UTC 
Description of problem:
Pool application tags are not applied unless supplied by the user; as a result the cluster ends up in HEALTH_WARN state with a message saying:

  application not enabled on N pool(s)


Version-Release number of selected component (if applicable):
ceph-ansible-3.1.0-0.1.rc8.el7cp
Comment 3 Giulio Fidente 2018-06-12 10:53:56 UTC 
I guess one option we have is to default all openstack_pools and pools to 'rbd' when application is not passed and manila_data/manila_metadata to 'cephfs'
Comment 4 Giulio Fidente 2018-06-12 14:38:10 UTC 
Also note that cephfs_pools does not accept the same syntax which pools and openstack_pools use, so a consumer wouldn't be able to set the application tag for the cephfs pools anyway.
Comment 5 Ken Dreyer (Red Hat) 2018-07-12 18:53:59 UTC 
The external PR is tagged in ceph-ansible's stable-3.1 upstream as v3.1.0rc10
Comment 11 errata-xmlrpc 2018-09-26 18:21:59 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-2018:2819