Bug 1635672 - Use GLUSTER_BLOCKD_STATUS_PROBE_ENABLE enabled templates in glusterfs playbooks
Summary: Use GLUSTER_BLOCKD_STATUS_PROBE_ENABLE enabled templates in glusterfs playbooks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: John Mulligan
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 13:14 UTC by Humble Chirammal
Modified: 2018-11-20 03:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-11-20 03:10:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3537 0 None None None 2018-11-20 03:11:30 UTC

Description Humble Chirammal 2018-10-03 13:14:07 UTC
Description of problem:


As part of fixing https://bugzilla.redhat.com/show_bug.cgi?id=1597726, we have introduced a new variable called GLUSTER_BLOCKD_STATUS_PROBE_ENABLE in gluster template. This variable controls the gluster block service status/health check as part of gluster deamonset readiness probe. By default, this environment variable is set to false so no changes or regression for existing customers. However if a customer/user want to enable this check they can enable it via above mentioned env variable. This bugzilla request is to pick this change in openshift ansible based installer of OCS .

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 4 Wei Sun 2018-11-06 05:48:14 UTC
Please help check if this bug could be verified,thanks!

Comment 14 errata-xmlrpc 2018-11-20 03:10:46 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:3537


Note You need to log in before you can comment on or make changes to this bug.