[LU-10734] sanity test_160g: User cl8 still found in changelog_users

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0
• Affects Version/s: Lustre 2.11.0
• Labels: sles12 suse
• Severity: 3
• Assignee: Bruno Faccini (Inactive)
• Reporter: Maloo

Description

sanity test_160g - User cl8 still found in changelog_users
^^^^^^^^^^^^^ DO NOT REMOVE LINE ABOVE ^^^^^^^^^^^^^

This issue was created by maloo for Bob Glossman <[e-mail]>

This issue relates to the following test suite run:
https://testing.hpdd.intel.com/test_sets/5a8495f4-1bfa-11e8-a6ad-52540065bddc
https://testing.hpdd.intel.com/test_sets/34e243bc-1be3-11e8-a7cd-52540065bddc

test_160g failed with the following error:

User cl8 still found in changelog_users

This may be a dup of LU-9624
I can't tell if it is so I am raising a fresh ticket.
Will let somebody else decide if it's a dup or not.

Issue Links

• is related to: LU-11161 sanity test_160g fails for DNE with ''mds2: User cl9 still registered''
• is related to: LU-9624 enable sanity.sh test_160a failures for DNE
• is related to: LU-10680 MDT becoming unresponsive in 2.10.3

Comments

[Peter Jones]

Landed for 2.12

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/31604/
Subject: LU-10734 tests: ensure current GC interval is over
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 821087e65882a9885964ed07d6f2a630dfb599d5

[Bob Glossman (Inactive)]

This fail is blocked for now. test 160g was added to ALWAYS_EXCEPT in a patch landed to master for LU-10680. May need to look for similar fails if and when test 160g is taken back out of ALWAYS_EXCEPT.

[Gerrit Updater]

Faccini Bruno ([e-mail]) uploaded a new patch: https://review.whamcloud.com/31604
Subject: LU-10734 tests: ensure current GC interval is over
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 72032b016ea8ab62cc681e72b5565ba207a6c316

[Bruno Faccini (Inactive)]

Eh eh, after taking some time to think about it, I was wondering if the only regression/side effect coming from patch https://review.whamcloud.com/27535 ("a37134d LU-9624 tests: fix pre-DNE test exceptions/llog usage"), that we strongly suspect to be the cause of these failures, is to have slightly reduced the execution/elapsed time of sanity/test_160g script's beginning/prologue that may now take less than the 2 seconds of delay interval between 2x garbage-collection thread runs (as it has just run in sanity/test_160f, when sanity.sh is being fully executed during auto-tests) being used/configured ("changelog_min_gc_interval=2").
And this seems to be confirmed during my reproducer testing.

So a simple "sleep 2" at the beginning of sanity/test_160g should fix this problem.

[Peter Jones]

> It didn't fail during normal testing, but I guess SLES is not part of regular testing.

Well, it is tested regularly, but due to the round robin system used for pre-landing review test runs, it is not guaranteed to run before everything lands unless people proactively request this with test parameters.

[Andreas Dilger]

Note also that with patch https://review.whamcloud.com/31552 "LU-10680 mdd: disable changelog garbage collection by default" test_160f and test_160g need to be modified to set changelog_gc=1 at the start of each test, and remove the tests from ALWAYS_EXCEPT so that the tests will run properly.