Description of problem: This RFE is to track the changes required in the upcall component to generate the events to be consumed by the eventing framework. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
the upcall events related to setting features.cache-invalidation & features.cache-invalidation-timeout volume tunables through gluster volume set interface is already available in mainline through http://review.gluster.org/14973 Moving this BZ to POST.
Given the patch mentioned in the above comment is already part of rhgs-3.2.0 now as a rebase, moving the state to MODIFIED.
Am able to see VOLUME_SET and VOLUME_RESET events corresponding to the options 'features.cache-invalidation' and 'features.cache-invalidation-timeout'. Moving this BZ to verified in 3.2. ############################################################################################################## {u'message': {u'name': u'ozone', u'options': [[u'features.cache-invalidation-timeout', u'600']]}, u'event': u'VOLUME_SET', u'ts': 1481872810, u'nodeid': u'8d3ab9e3-c086-4474-9db2-677d5018d055'} ############################################################################################################## {u'message': {u'name': u'ozone', u'options': [[u'features.cache-invalidation', u'on']]}, u'event': u'VOLUME_SET', u'ts': 1481872829, u'nodeid': u'8d3ab9e3-c086-4474-9db2-677d5018d055'} ############################################################################################################## {u'message': {u'name': u'ozone', u'option': u'features.cache-invalidation'}, u'event': u'VOLUME_RESET', u'ts': 1481872843, u'nodeid': u'8d3ab9e3-c086-4474-9db2-677d5018d055'} ############################################################################################################## {u'message': {u'name': u'ozone', u'option': u'features.cache-invalidation-timeout'}, u'event': u'VOLUME_RESET', u'ts': 1481872870, u'nodeid': u'8d3ab9e3-c086-4474-9db2-677d5018d055'}
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://rhn.redhat.com/errata/RHSA-2017-0486.html