Description of problem: Red Hat IT raised concern over rpm scripting: Iterating over ls output is fragile. Use globs. Reference - https://github.com/koalaman/shellcheck/wiki/SC2045 Quoting: Please consider changing /etc/init.d/gluster-system-settings from: #!/bin/bash # # chkconfig: 35 99 12 # description: Configure sysctl settings to optimize Gluster I/O # for i in $(ls -d /sys/block/*/queue/iosched 2>/dev/null); do iosched_dir=$(echo $i | awk '/iosched/ {print $1}') [ -z $iosched_dir ] && { continue } path=$(dirname $iosched_dir) [ -f $path/scheduler ] && { echo "deadline" > $path/scheduler } done modprobe fuse; if ! grep -q Gluster /etc/security/limits.conf ; then echo '* - core unlimited # added by Gluster' >> /etc/security/limits.conf fi to: #!/bin/bash # # chkconfig: 35 99 12 # description: Configure sysctl settings to optimize Gluster I/O # for i in /sys/block/*/queue/iosched; do iosched_dir=$(echo ${i} | awk '/iosched/ {print $1}') [ -z ${iosched_dir} ] && { continue } path=$(dirname ${iosched_dir}) [ -f ${path}/scheduler ] && { echo "deadline" > ${path}/scheduler } done modprobe fuse; if ! grep -q Gluster /etc/security/limits.conf ; then echo '* - core unlimited # added by Gluster' >> /etc/security/limits.conf fi
@Sunil : can we accept this for 3.4.1?
@Rahul : can we accept this for 3.4.1?
Build version: redhat-storage-server-3.4.2.0-1.el6rhs.noarch (RHEL 6) redhat-storage-server-3.4.2.0-1.el7rhgs.noarch (RHEL 7) After successful installation of redhat-storage-server all the io-schedulers for the block devices are set to "deadline". RHEL 6 # cat /sys/block/vdb/queue/scheduler noop anticipatory deadline [cfq] # rpm -qa | grep redhat-storage-server redhat-storage-server-3.4.2.0-1.el6rhs.noarch RHEL 7 # cat /sys/block/vdb/queue/scheduler [mq-deadline] kyber none # rpm -qa | grep redhat-storage-server redhat-storage-server-3.4.2.0-1.el7rhgs.noarch Hence, based on comment #16 , comment #17 and the above observation, moving this bug to VERIFIED.
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:3827