DAOS-15655 test: stop passing server group

[daltonbohning]

Test-tag: pr ContinuousWrite SpaceRb MultipleContainerDelete PerServerFaultDomainTest TestWithTelemetryIOLatency AgentFailure NetworkFailureTest ServerRankFailure TargetFailure EcodSpaceUsage ParallelIo IorCrash NvmeEnospace NvmeFragmentation NvmeIoVerification NvmeIo NvmePoolCapacity PoolMembershipTest ObjectMetadata datamover soak_smoke NvmePoolCapacity OSAOnlineParallelTest DiskFailureTest,-manual NvmePoolExtend OSAOfflineDrain OSAOfflineExtend OSAOfflineParallelTest OSAOfflineReintegration OSAOnlineDrain OSAOnlineDrain OSAOnlineExtend OSAOnlineExtend OSAOnlineReintegration NvmeEnospace NvmeFault NvmeHealth OSAOfflineDrain OSAOfflineReintegration EcodAggregationOff EcodOnlineMultFail EcodAggregationOffRebuild mdtest ior NvmePoolExclude NvmeFaultReintegrate IoctlPoolHandles ReplayTests BasicClientTelemetry WalMetrics DaosAggregationMultiPoolCont VerifyPoolSpace
Skip-unit-tests: true
Skip-fault-injection-test: true

Required-githooks: true

Before requesting gatekeeper:

• Two review approvals and any prior change requests have been resolved.
• Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
• Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
• Commit messages follows the guidelines outlined here.
• Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

• You are the appropriate gatekeeper to be landing the patch.
• The PR has 2 reviews by people familiar with the code, including appropriate owners.
• Githooks were used. If not, request that user install them and check copyright dates.
• Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
• All builds have passed. Check non-required builds for any new compiler warnings.
• Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
• If applicable, the PR has addressed any potential version compatibility issues.
• Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
• Extra checks if forced landing is requested
  • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
  • No new NLT or valgrind warnings. Check the classic view.
  • Quick-build or Quick-functional is not used.
• Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

[github-actions]

Ticket title is 'Using a different system name (other than daos_server) does not work.'
Status is 'Open'
Labels: 'triaged'
https://daosio.atlassian.net/browse/DAOS-15655

[daosbuild1]

Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14201/1/display/redirect

[daosbuild1]

Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-14201/1/testReport/

[daosbuild1]

Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-14201/2/testReport/

[daltonbohning]

Single failure in https://build.hpdd.intel.com/blue/organizations/jenkins/daos-stack%2Fdaos/detail/PR-14201/2/tests
Is for a manual test not expected to pass in CI

daos/src/tests/ftest/vmd/fault_reintegration.py

Line 92 in c122a9a

:avocado: tags=all,manual

Intentionally made a manual test:
https://daosio.atlassian.net/browse/DAOS-13157

[daltonbohning]

Please use this description for merge

Stop passing --dfs.group to ior and mdtest since they get this information from the agent.