[LU-11991] conf-sanity test_32xx fails for separate MGS Created: 22/Feb/19  Updated: 19/Feb/20

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

Type: Bug Priority: Minor
Reporter: Alexander Boyko Assignee: Alexander Boyko
Resolution: Unresolved Votes: 0
Labels: always_except

Issue Links:
Related
is related to LU-10717 several conf-sanity tests failed: FAI... Resolved
is related to LU-8110 Seperated MGS/MDS: conf-sanity test_3... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

It is regression after patch https://review.whamcloud.com/33422 "LU-11556 tests: fix set_persistent_param_and_check breakage". With separate MGS set_persistent_param_and_check run at mgs node, but test stop it, and run local MDS+MGS.



 Comments   
Comment by James A Simmons [ 22/Feb/19 ]

I see you are resolving this with https://review.whamcloud.com/#/c/33589. Why the separate ticket?

Comment by Alexander Boyko [ 28/Feb/19 ]

Only skipping for 32xx at https://review.whamcloud.com/#/c/33589

Comment by Andreas Dilger [ 08/Jul/19 ]

Actually, looking at patch https://review.whamcloud.com/33422 "LU-11556 tests: fix set_persistent_param_and_check breakage" it isn't clear that this introduced the problem that you describe. It was just fixing a problem where "$node" was being passed to set_persistent_param_and_check() instead of "$facet", it doesn't do anything related to starting/stopping the MGS device? Is there some other patch that introduced this breakage, or am I missing the connection?

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