Description of problem: throttle-rebal.t is observed failure because invalid cores presented to test. On 8 core vm: The command `cat /proc/cpuinfo | grep processor | wc -l` gives 9 rather than 8. Changing it to `cat /proc/cpuinfo | grep -w processor | wc -l` gives 8. Version-Release number of selected component (if applicable): 4.x How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: The command `cat /proc/cpuinfo | grep processor | wc -l` to give 9 Expected results: The command `cat /proc/cpuinfo | grep processor | wc -l` to give 8 Additional info: $ cat /proc/cpuinfo vendor_id : IBM/S390 # processors : 8 bogomips per cpu: 15432.00 features : esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te cache0 : level=1 type=Data scope=Private size=96K line_size=256 associativity=6 cache1 : level=1 type=Instruction scope=Private size=64K line_size=256 associativity=4 cache2 : level=2 type=Data scope=Private size=1024K line_size=256 associativity=8 cache3 : level=2 type=Instruction scope=Private size=1024K line_size=256 associativity=8 cache4 : level=3 type=Unified scope=Shared size=49152K line_size=256 associativity=12 cache5 : level=4 type=Unified scope=Shared size=393216K line_size=256 associativity=24 processor 0: version = FF, identification = 18BAA6, machine = 2827 processor 1: version = FF, identification = 18BAA6, machine = 2827 processor 2: version = FF, identification = 18BAA6, machine = 2827 processor 3: version = FF, identification = 18BAA6, machine = 2827 processor 4: version = FF, identification = 18BAA6, machine = 2827 processor 5: version = FF, identification = 18BAA6, machine = 2827 processor 6: version = FF, identification = 18BAA6, machine = 2827 processor 7: version = FF, identification = 18BAA6, machine = 2827
Solution : change the command to `cat /proc/cpuinfo | grep -w processor | wc -l`
Created attachment 1416138 [details] Patch for tests/basic/distribute/throttle-rebal.t
Hi Salamani, Would you be able to send patch to gerrit? Susant
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.