SRE-4014 tests: Move NvmeIoVerification.test_nvme_server_restart to cb

[ryon-jensen]

• NvmeIoVerification.test_nvme_server_restart

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/SRE-4014

[daltonbohning]

Are we confident this one will pass regularly on ClusterBox? It does run IOR, and in the past the VM network bandwidth has been very low. I'm not sure if ClusterBox has that same isue

[ryon-jensen]

This has passed 20 times in a row, however, there is concern that anything that runs IOR is meant to stress the system, so maybe there's potential for this to not catch bugs running on cluster box because it's not able to stress the system the same way as on HW clusters?? @daltonbohning, @phender, @sylviachanoiyee - thoughts?

[daltonbohning]

This has passed 20 times in a row, however, there is concern that anything that runs IOR is meant to stress the system, so maybe there's potential for this to not catch bugs running on cluster box because it's not able to stress the system the same way as on HW clusters?? @daltonbohning, @phender, @sylviachanoiyee - thoughts?

Reading the test description, this seems like more of a correctness test than a stress test so I think ClusterBox should be okay

daos/src/tests/ftest/nvme/io_verification.py

Lines 20 to 37 in ba87df6

	def test_nvme_server_restart(self):
	"""Jira ID: DAOS-2650.
	Test Description:
	Test will run IOR with non standard transfer sizes for different set of pool sizes.
	Purpose is to verify io transaction to scm and nvme for different pool sizes when
	servers are restarted after write.
	Test Steps:
	1. Create a pool of specified size percentage.
	2. Create a container and run IOR write with specified transfer size. Some transfer size
	is smaller than 4096 and some are larger so that both SCM and NVMe are tested. See the test
	yaml for detail.
	3. Restart servers and verify that all servers restarted.
	4. Run IOR read to verify that reading the data written before the restart works.
	5. Verify IOR consumed the expected amount of space from the pool.
	6. Destroy container and go to step 2. After all transfer sizes are tested, go to next.
	7. Destroy pool and go to step 1.