Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-11749

sanity-sec test 23b fails with 'Should return gid=60010 or 60010 on client2'

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Lustre 2.12.0
    • Fix Version/s: Lustre 2.13.0, Lustre 2.12.2
    • Labels:
      None
    • Severity:
      3
    • Rank (Obsolete):
      9223372036854775807

      Description

      sanity-sec test_23b started failing on October 30, 2018 with 'Should return gid=60010 or 60010 on client2'

      Looking at the client test_log from a recent failure, https://testing.whamcloud.com/test_sets/1e06f64c-f9d7-11e8-b216-52540065bddc , we see an issue parsing output

      CMD: onyx-41vm12 /usr/sbin/lctl list_nids | grep tcp | cut -f 1 -d @
      waited 5 seconds for sync
      getfacl: Removing leading '/' from absolute path names
      CMD: onyx-41vm9.onyx.whamcloud.com getfacl /mnt/lustre/d23b.sanity-sec
      getfacl: Removing leading '/' from absolute path names
      CMD: onyx-41vm9.onyx.whamcloud.com getent passwd
      /usr/lib64/lustre/tests/sanity-sec.sh: line 1834: [: sanityusr: integer expression expected
       sanity-sec test_23b: @@@@@@ FAIL: Should return gid=60010 or 60010 on client2 
      

      This issue may be caused by the landing of the patch for LU-9795 https://review.whamcloud.com/28662.

      From sanity-sec test_23b, the code that fails is

      1799         local fs_id=$((IDBASE+10))
      …
      1828         # getfacl default acl on client2 (mapped gid=60010)
      1829         mapped_id=$(do_node ${clients_arr[1]} getfacl $testdir |
      1830                         grep -E "default:group:.*:rwx" | awk -F: '{print $3}')
      1831         fs_user=$(do_node ${clients_arr[1]} getent passwd |
      1832                         grep :$fs_id:$fs_id: | cut -d: -f1)
      1833         [ -z "$fs_user" ] && fs_user=$fs_id
      1834         [ $mapped_id -eq $fs_id -o "$mapped_id" = "$fs_user" ] ||
      1835                 error "Should return gid=$fs_id or $fs_user on client2"
      1836 
      

      sanity-sec test 23b requires two clients. The test can be kicked off/run on either client 1 or client 2. The issue may be that getfacl and getent needs to be run on the client that is not kicking off the test. In the failures, the test is being run on client 2, but looking at (a small number of) tests that pass, the test is kicked off on client 1.

      More failures are at:
      https://testing.whamcloud.com/test_sets/431b8374-dc8d-11e8-b46b-52540065bddc
      https://testing.whamcloud.com/test_sets/0059669a-dd10-11e8-975a-52540065bddc
      https://testing.whamcloud.com/test_sets/c813ae6e-dd76-11e8-b46b-52540065bddc

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sebastien Sebastien Buisson
                Reporter:
                jamesanunez James Nunez
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: