Description
Lustre failover tests can not be ran test-by-test (ONLY=1 replay-dual.sh && ONLY=2 replay-dual.sh) on the setup with ${facet}_HOST != ${facet}failover_HOST.
t-f keeps the "active" facet info in "${facet}active" files, which are created
when facet_failover() is executed first time in the test session.
Before facet_failover() executed these files are empty and
active facet is ${facet} by default.
In case when tests are executed test-by-test the active facet is
${facet}failover after 1st test completed, and 2nd test is started
having ${facet}failover active without this info stored in
${facet}active files.
It looks reasonable to detect active facet based on current state.
Attachments
Issue Links
- is related to
-
LU-10827 conf-sanity test 0 fails with ‘rmmod: ERROR: Module lustre is in use’
-
- Resolved
-
"Elena Gryaznova <elena.gryaznova@hpe.com>" uploaded a new patch: https://review.whamcloud.com/46360
Subject: LU-6867 tests: detect active facet based on current state
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 208ac4be4f08ca9da5e762ecde66031d7f835f30