[LU-16324] conf-sanity test_123ae: old conf_param wasn't stored in params log Created: 18/Nov/22  Updated: 02/Dec/22

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Related
is related to LU-15706 "lctl pool_destroy" can't work correc... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for HUANG XING <hxing@ddn.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/f1834727-5e6d-43c7-92c7-431dd81eab9a

The error happened on b2_15.

From the log:
conf-sanity test_123ae: @@@@@@ FAIL: old conf_param wasn't stored in params log
Trace dump:
= /usr/lib64/lustre/tests/test-framework.sh:6406:error()
= /usr/lib64/lustre/tests/conf-sanity.sh:9354:test_123ae()
= /usr/lib64/lustre/tests/test-framework.sh:6723:run_one()
= /usr/lib64/lustre/tests/test-framework.sh:6770:run_one_logged()
= /usr/lib64/lustre/tests/test-framework.sh:6611:run_test()
= /usr/lib64/lustre/tests/conf-sanity.sh:9368:main()



 Comments   
Comment by Xing Huang [ 02/Dec/22 ]

In patch (https://review.whamcloud.com/#/c/fs/lustre-release/+/49178/), Dongyang ported the master patch of LU-15706 to b2_15 to solve this issue.

Generated at Sat Feb 10 03:25:59 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.