Bug 1696880

Summary: ceph ansible 3.x still sets memory option if
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: John Fulton <johfulto>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Yogesh Mane <ymane>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.2CC: aschoen, ceph-eng-bugs, dsavinea, edonnell, gabrioux, gmeno, marjones, nthomas, sankarshan, tchandra, tserlin, vashastr, ymane
Target Milestone: rc   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.16-1.el7cp Ubuntu: ceph-ansible_3.2.16-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-21 15:10:49 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 John Fulton 2019-04-05 20:43:52 UTC 
ceph-ansible 3.2.x still sets the container --memory flag if bluestore is used.

This issue was fixed with the following PR:

https://github.com/ceph/ceph-ansible/commit/dc1c0dcee21deefa359cae30d3a733a4348bfd2f#diff-eeb7d6b3bca9ebda529454853f290989

Could the above be backported to 3.2.x as it will negatively impact bluestore use in the field?
Comment 1 Guillaume Abrioux 2019-04-10 06:50:28 UTC 
This has been backported upstream into stable-3.2, it will be present in the next tag.
Comment 8 errata-xmlrpc 2019-08-21 15:10:49 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/RHSA-2019:2538