Bug 1535967

Summary:	pcs should allow to set the netmtu when configuring the cluster
Product:	Red Hat Enterprise Linux 7	Reporter:	Michele Baldessari <michele>
Component:	pcs	Assignee:	Ondrej Mular <omular>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	aherr, cfeist, cluster-maint, idevat, omular, rsteiger, tojeline
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pcs-0.9.165-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 08:05:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1520573

Description Michele Baldessari 2018-01-18 11:03:37 UTC

Right now it is not possible to set the MTU used by corosync when creating the cluster. Since corosync defaults to 1500, this might be problematic in certain setups (thing CI running a pacemaker-based control plane in VMs where the MTU is a bit lower).

It's be great if we had a --netmtu parameter when calling 'pcs cluster setup', so we could programmatically set the mtu to the right value when creating the cluster.

Comment 3 Ondrej Mular 2018-05-16 12:22:57 UTC

Proposed fix:
https://github.com/ClusterLabs/pcs/commit/6028859eb969645402d5486123c9c4815846

Test:
[root@rhel75-node1 ~]# pcs cluster setup --name cluster1 rhel75-node1 --netmtu 25000 --local
Shutting down pacemaker/corosync services...
Killing any remaining services...
Removing all cluster configuration files...
[root@rhel75-node1 ~]# pcs cluster corosync 
totem {
    version: 2
    cluster_name: cluster1
    secauth: off
    transport: udpu
    netmtu: 25000
}

nodelist {
    node {
        ring0_addr: rhel75-node1
        nodeid: 1
    }
}

quorum {
    provider: corosync_votequorum
}

logging {
    to_logfile: yes
    logfile: /var/log/cluster/corosync.log
    to_syslog: yes
}

Comment 4 Ivan Devat 2018-06-22 12:12:48 UTC

After Fix:

[ant ~] $ rpm -q pcs pcs-snmp
pcs-0.9.165-1.el7.x86_64
pcs-snmp-0.9.165-1.el7.x86_64

[ant ~] $ pcs cluster setup --name=zoo ant bee --netmtu 25000
Destroying cluster on nodes: ant, bee...
ant: Stopping Cluster (pacemaker)...
bee: Stopping Cluster (pacemaker)...
bee: Successfully destroyed cluster
ant: Successfully destroyed cluster

Sending 'pacemaker_remote authkey' to 'ant', 'bee'
ant: successful distribution of the file 'pacemaker_remote authkey'
bee: successful distribution of the file 'pacemaker_remote authkey'
Sending cluster config files to the nodes...
ant: Succeeded
bee: Succeeded

Synchronizing pcsd certificates on nodes ant, bee...
ant: Success
bee: Success
Restarting pcsd on the nodes in order to reload the certificates...
ant: Success
bee: Success
[ant ~] $ pcs cluster corosync|grep -B5 netmtu
totem {
    version: 2
    cluster_name: zoo
    secauth: off
    transport: udpu
    netmtu: 25000

Comment 8 errata-xmlrpc 2018-10-30 08:05:31 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:3066