Bug 1577970 - puppet-ceph incorrectly sets rgw_keystone_revocation_interval to absent
Summary: puppet-ceph incorrectly sets rgw_keystone_revocation_interval to absent
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-ceph
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z14
: 10.0 (Newton)
Assignee: Giulio Fidente
QA Contact: Yogev Rabl
URL:
Whiteboard:
: 1624438 (view as bug list)
Depends On:
Blocks: 1529126 1546976
TreeView+ depends on / blocked
 
Reported: 2018-05-14 14:18 UTC by Giulio Fidente
Modified: 2021-02-09 08:14 UTC (History)
5 users (show)

Fixed In Version: puppet-ceph-2.4.2-1.el7ost.noarch.rpm
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-09 08:11:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1770234 0 None None None 2018-05-14 14:18:19 UTC
OpenStack gerrit 568515 0 'None' MERGED Puppet incorrectly sets rgw_keystone_revocation_interval to absent 2021-02-08 20:39:58 UTC

Description Giulio Fidente 2018-05-14 14:18:20 UTC 
When use_pki is set to false, puppet-ceph will ensure rgw_keystone_revocation_interval is absent from the ceph configuration file. (1) The value passed by puppet-tripleo (2)(3) is ignored.

1: https://github.com/openstack/puppet-ceph/blob/master/manifests/rgw/keystone.pp#L189
2: https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/base/ceph/rgw.pp#L85
3: https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/base/ceph/rgw.pp#L96
Comment 1 Giulio Fidente 2018-05-14 14:20:21 UTC 
The submission for master branch needs to be backported into stable/jewel : https://review.openstack.org/#/c/567301/
Comment 3 Lon Hohberger 2019-12-02 11:50:28 UTC 
According to our records, this should be resolved by puppet-ceph-2.4.2-1.el7ost.  This build is available now.
Comment 6 Giulio Fidente 2021-02-09 08:14:05 UTC 
*** Bug 1624438 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.