Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1596726 - Change multipath config steps of Advanced Installation to include load-balancing changes(RFE-1575529)
Change multipath config steps of Advanced Installation to include load-balanc...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.10.0
Unspecified Unspecified
unspecified Severity high
: ---
: 3.11.0
Assigned To: Jose A. Rivera
Neha Berry
:
Depends On:
Blocks: 1596728
  Show dependency treegraph
 
Reported: 2018-06-29 10:36 EDT by Neha Berry
Modified: 2018-10-11 03:21 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1596728 (view as bug list)
Environment:
Last Closed: 2018-10-11 03:20:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:21 EDT

  None (edit)
Description Neha Berry 2018-06-29 10:36:48 EDT
Based on RFE - https://bugzilla.redhat.com/show_bug.cgi?id=1575529



Description of problem:
++++++++++++++++++++++++++
A fresh setup was created for OCP 3.10(v3.10.0-0.67.0) and CNS 3.10 using Ansible advanced deployment playbook( deploy_cluster.yaml).

Starting from gluster-block version- gluster-block-0.2.1-19.el7rhgs , load-balancing feature is enabled and to use this benefit, on the initiator side we will have to set 'prio alua' instead of prio "const" in the /etc/multipath.conf file. 

Since multipath is configured as part of a sub-task in deploy_cluster.yaml deployment, requesting to make the below changes to the multipath configuration file which is added/created in the OCP+CNS nodes.

prio "const"

A document bug is already raised to address changes in multipath conf file.
Bug https://bugzilla.redhat.com/show_bug.cgi?id=1595684

Steps to be performed when we change the conf file manually:
---------------------------

1. Add prio "alua" in /etc/multipath.conf
2. restart multipathd service

 
Sample multipath.conf file to include prio "alua" instead of prio "const"
 # cat /etc/multipath.conf
[...]
# LIO iSCSI
devices {
        device {
                vendor "LIO-ORG"
                user_friendly_names "yes" # names like mpatha
                path_grouping_policy "failover" # one path per group
                path_selector "round-robin 0"
                failback immediate
                path_checker "tur"
                prio "alua"
                no_path_retry 120
                rr_weight "uniform"
        }
}


Versions 
===========
tcmu-runner = tcmu-runner-1.2.0-20.el7rhgs 
gluster-block version- gluster-block-0.2.1-19.el7rhgs and beyond
OCP 3.10 latest

Actual results:
+++++++++++++++++
in current advanced deployment playbook, multipath.conf file of OCP/CNS hosts have [prio "const"] pre-configured. To take advantage of load balancing at gluster-block, we have to manually edit the /etc/multipath.conf file on each of the initiator nodes.


Expected results:
++++++++++++++++

Starting from OCP 3.10 deployment, tcmu-runner = tcmu-runner-1.2.0-20.el7rhgs and  gluster-block version- gluster-block-0.2.1-19.el7rhgs,  Ansible playbook should ,by default, configure prio "alua" and no manual change must be required.

Thanks in advance.
Comment 4 Jose A. Rivera 2018-07-02 08:10:31 EDT
PR is upstream: https://github.com/openshift/openshift-ansible/pull/9038
Comment 5 Scott Dodson 2018-08-01 15:39:52 EDT
In openshift-ansible-3.11.0-0.9.0
Comment 8 Jose A. Rivera 2018-08-13 10:26:48 EDT
3.10.z backport PR: https://github.com/openshift/openshift-ansible/pull/9559
Comment 9 Jose A. Rivera 2018-08-13 14:40:38 EDT
3.10.z PR is merged.
Comment 11 Jose A. Rivera 2018-08-16 09:49:46 EDT
Built as part of openshift-ansible-3.10.28-1
Comment 14 errata-xmlrpc 2018-10-11 03:20:43 EDT
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:2652

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