[LU-10334] Ubuntu1604 client sanity-103a: FAIL: ACL misc test failed Created: 06/Dec/17  Updated: 20/Jan/24  Resolved: 20/Jan/24

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.11.0, Lustre 2.10.2, Lustre 2.10.3, Lustre 2.10.4
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Sarah Liu Assignee: James A Simmons
Resolution: Fixed Votes: 0
Labels: ubuntu
Environment:

server: 2.10.2 RC1
client: Ubuntu 16.04


Issue Links:
Related
is related to LU-10997 Ubuntu 18 support Resolved
is related to LU-14139 batched statahead processing Resolved
is related to LU-11594 sanity test_103a: FAIL: permissions f... Resolved
is related to LU-12657 sanity/103 and sanityn/25 fail with 4... Resolved
is related to LU-15259 SLES15.2 sanity test_103a test_125 te... Resolved
is related to LU-13740 Ubuntu 20.04 LTS release Resolved
is related to LU-14776 Ubuntu 20.04 HWE support Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

client console

[413] $ chmod 750 d -- ok
[414] $ ls -dl d | awk '{print $1}' -- ok
[417] $ getfacl --omit-header d -- failed
user::rwx                             | user::rwx
user:bin:r-x                          ? user:daemon:rwx #effective:r-x
user:daemon:rwx #effective:r-x        ? user:bin:r-x
group::rwx      #effective:r-x             | group::rwx #effective:r-x
mask::r-x                             | mask::r-x
other::---                            | other::---
default:user::rwx                     | default:user::rwx
default:user:bin:r-x                  ? default:user:daemon:rwx
default:user:daemon:rwx               ? default:user:bin:r-x
default:group::rwx                    | default:group::rwx
default:mask::rwx                     | default:mask::rwx
default:other::r-x                    | default:other::r-x
                                      |
[432] $ rmdir d -- ok
103 commands (91 passed, 12 failed)
 sanity test_103a: @@@@@@ FAIL: misc test failed



 Comments   
Comment by James Nunez (Inactive) [ 06/Dec/17 ]

Logs for this failure are at: https://testing.hpdd.intel.com/test_sets/8432a7b6-da27-11e7-9840-52540065bddc

Comment by Andreas Dilger [ 06/Dec/17 ]

I don't think this is a real failure, just the "bin" and "daemon" users are reported in the opposite order. Maybe the test needs to sort the output from getfacl?

Comment by Gerrit Updater [ 29/Mar/18 ]

James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/31828
Subject: LU-10334 tests: add tests to ALWAYS_EXCEPT for Ubuntu
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: c64199eaa1851ec9ba5bd0d55883092f08a9a510

Comment by Gerrit Updater [ 30/Mar/18 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/31828/
Subject: LU-10334 tests: add tests to ALWAYS_EXCEPT for Ubuntu
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 68be7b634d8e46c110f11916dd87b9f1c36a90e1

Comment by Andreas Dilger [ 30/Mar/18 ]

This issue has not been fixed, only added to ALWAYS_EXCEPT, so it should NOT be marked resolved for the 2.11 release.

Comment by Gerrit Updater [ 18/Apr/18 ]

James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/32047
Subject: LU-10334 tests: add tests to ALWAYS_EXCEPT for Ubuntu
Project: fs/lustre-release
Branch: b2_10
Current Patch Set: 1
Commit: 020d6df0d2b2cf00b21de77d34039bfb3c7ca422

Comment by Gerrit Updater [ 03/May/18 ]

John L. Hammond (john.hammond@intel.com) merged in patch https://review.whamcloud.com/32047/
Subject: LU-10334 tests: add tests to ALWAYS_EXCEPT for Ubuntu
Project: fs/lustre-release
Branch: b2_10
Current Patch Set:
Commit: a6a82497eb6ed594b2cdef9aaedc8c967f2fb52f

Comment by Gerrit Updater [ 26/Aug/19 ]

Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/35931
Subject: LU-10334 tests: remove sanity 103a from ALWAYS_EXCEPT
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 8d941994455bd7377ed7c5c9b9fe58e5a4d2a6ef

Comment by James A Simmons [ 25/Apr/22 ]

The fix is under LU-15259

Comment by Andreas Dilger [ 20/Jan/24 ]

Please use "Resolved" instead of "Closed", as that allows editing some aspects of the ticket, for example removing the always_except marker now that the test is no longer excluded.

Generated at Sat Feb 10 02:34:07 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.