[LU-5679] where possible sanity-hsm should wait for file status rather than request state Created: 29/Sep/14  Updated: 19/Apr/22

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

Type: Improvement Priority: Minor
Reporter: John Hammond Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: hsm

Severity: 3
Rank (Obsolete): 15911

 Description   

In several sanity-hsm sub tests the racy wait_request_state calls can be replaced safer waits on a specific HSM status.

test_222b() {
        # test needs a running copytool
	copytool_setup

	mkdir -p $DIR/$tdir
        local f=$DIR/$tdir/$tfile
	local fid=$(copy_file /etc/passwd $f)

        changelog_setup
        $LFS hsm_archive --archive $HSM_ARCHIVE_NUMBER $f
        wait_request_state $fid ARCHIVE SUCCEED
	$LFS hsm_release $f

        md5sum $f

	wait_request_state $fid RESTORE SUCCEED

        local flags=$(changelog_get_flags ${MDT[0]} HSM $fid | tail -1)

        local target=0x80
        [[ $flags == $target ]] || error "Changelog flag is $flags not $target"

        cleanup
}
run_test 222b "Changelog for implicit restore"

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