daos icon indicating copy to clipboard operation
daos copied to clipboard

DAOS-18091 test: Use ram field to detect MD-on-SSD

Open shimizukko opened this issue 5 months ago • 9 comments

These tests run on HW Medium, which includes MD-on-SSD cluster. If the test runs on MD-on-SSD, in server config, storage -> class would be ram. If it runs on a normal cluster, storage -> class would be dcpm. Currently, we're skipping these tests if it's on MD-on-SSD cluster.

One way to determine is to check the pool directory. On MD-on-SSD, the pool directory would be empty after system stop. However, it seems it takes some time to remove the files in the directory and we don't know how long we should wait for sure. We just need to determine whether we're on MD-on-SSD, so simply check the server config.

Skip-unit-tests: true Skip-fault-injection-test: true Test-tag: PoolMembershipTest PoolListConsolidationTest DMGCheckStartOptionsTest

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).

shimizukko avatar Nov 01 '25 06:11 shimizukko

Ticket title is 'Check automated CR tests are properly executed on MD-on-SSD and normal cluster' Status is 'In Progress' https://daosio.atlassian.net/browse/DAOS-18091

github-actions[bot] avatar Nov 01 '25 06:11 github-actions[bot]

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/2/execution/node/742/log

daosbuild3 avatar Nov 01 '25 09:11 daosbuild3

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/3/execution/node/741/log

daosbuild3 avatar Nov 02 '25 12:11 daosbuild3

Test stage Functional Hardware Medium completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/10/execution/node/735/log

daosbuild3 avatar Nov 07 '25 16:11 daosbuild3

Test stage Functional Hardware Medium completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/11/execution/node/737/log

daosbuild3 avatar Nov 09 '25 21:11 daosbuild3

Test stage Functional Hardware Medium completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/12/execution/node/766/log

daosbuild3 avatar Nov 10 '25 08:11 daosbuild3

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/12/execution/node/780/log

daosbuild3 avatar Nov 10 '25 08:11 daosbuild3

Test stage Functional Hardware Medium completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/13/execution/node/791/log

daosbuild3 avatar Nov 24 '25 22:11 daosbuild3

Test stage Functional Hardware Medium completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17068/14/execution/node/822/log

daosbuild3 avatar Nov 30 '25 21:11 daosbuild3