Description of problem: ----------------------- As there are gluster and virt services are running on the same host/machines, gluster slice setup is required to cap the number of cores consumed by gluster process. Gdeploy has gone with the standard value of 33% cores allocated to gluster process. The same needs to implemented with gluster-ansible roles too. Version-Release number of selected component (if applicable): ------------------------------------------------------------- gluster-ansible-roles-1.0.4-3 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Complete RHHI-V deployment with RHVH 4.3 Actual results: --------------- gluster slice is not configured Expected results: ----------------- gluster slice should be configured
Tested with gluster-ansible-features-1.0.4-5 Glusterfs slice is now available [root@ ~]# systemctl status glusterd ● glusterd.service - GlusterFS, a clustered file-system server Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/glusterd.service.d └─99-cpu.conf Active: active (running) since Wed 2019-03-06 13:53:36 IST; 3h 30min ago Main PID: 5365 (glusterd) CGroup: /system.slice/glusterd.service ├─ 5365 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level IN... ├─ 9863 /usr/sbin/glusterfsd -s dhcp37-161.lab.eng.blr.redhat.com ... ├─10355 /usr/sbin/glusterfsd -s dhcp37-161.lab.eng.blr.redhat.com ... └─10377 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glus... Mar 06 13:53:31 dhcp37-161.lab.eng.blr.redhat.com systemd[1]: Starting Gluste... Mar 06 13:53:36 dhcp37-161.lab.eng.blr.redhat.com systemd[1]: Started Gluster... Mar 06 14:29:28 dhcp37-161.lab.eng.blr.redhat.com glusterd[5365]: [2019-03-06... Mar 06 14:29:40 dhcp37-161.lab.eng.blr.redhat.com glusterd[5365]: [2019-03-06... [root@ ~]# cat /etc/systemd/system/glusterfs.slice [Slice] CPUQuota=200% [root@ ~]# nproc 4
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/RHEA-2019:1121