This variable should have been included with openshift-ansible-3.11.161-2.git.5.029d67f.el7 from https://access.redhat.com/errata/RHBA-2020:0017 What version of openshift-ansible did you use to deploy?
Many thanks Aditya! > I can't find heketi-template.yml file in /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/files This file was renamed to /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/templates/heketi-template.yml.j2 as it became a .j2-template. When openshift-ansible runs, it will produce a (temporary) heketi-template.yml file which hets applied to the OCP cluster. > Also, the deploy-heketi-template.yml file is not updated with HEKETI_LVMWRAPPER changes: Indeed, at first I did not think it was needed there. However after reading your message and thinking about it a little more, it would be good to add the environment variable there too. The deploy-heketi-template.yml is only used for deploying heketi, and during normal runtime the heketi-template.yml(.j2) is used. But during deployment the first Gluster volume is created (for the heketi db), so LVM commands are executed and that could cause problems (not very likely, but possible). I will send a PR to openshift-ansible to correct this. Note that there is a workaround: Add the HEKETI_LVMWRAPPER (value /usr/sbin/exec-on-host) environment variable to the heketi DeploymentConfig after installation.
(In reply to Niels de Vos from comment #7) > Many thanks Aditya! > > > I can't find heketi-template.yml file in /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/files > > This file was renamed to > /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/ > templates/heketi-template.yml.j2 as it became a .j2-template. When > openshift-ansible runs, it will produce a (temporary) heketi-template.yml > file which hets applied to the OCP cluster. > Thanks, I will raise a documentation bug to correct this. > > Also, the deploy-heketi-template.yml file is not updated with HEKETI_LVMWRAPPER changes: > > Indeed, at first I did not think it was needed there. However after reading > your message and thinking about it a little more, it would be good to add > the environment variable there too. The deploy-heketi-template.yml is only > used for deploying heketi, and during normal runtime the > heketi-template.yml(.j2) is used. But during deployment the first Gluster > volume is created (for the heketi db), so LVM commands are executed and that > could cause problems (not very likely, but possible). > Yes! This will help to perform manual upgrades.
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:0402