daos-stack
DAOS-16565 control: Log component check at Trace level
The component compatibility check is noisy, and reduces the usefulness of debug-level logging for customers. It's still useful for devs as a trace-level message.
Steps for the author:
- [x] Commit message follows the guidelines.
- [x] Appropriate Features or Test-tag pragmas were used.
- [x] Appropriate Functional Test Stages were run.
- [x] 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).
Ticket title is 'do not log "is compatible with" messages' Status is 'In Review' Labels: 'lrz,scrubbed_2.8,usability' https://daosio.atlassian.net/browse/DAOS-16565
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
The assortment of hardware failures are unrelated to this small logging change. Requesting forced landing.
Test stage Functional Hardware Large 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-16329/5/execution/node/1531/log
The one test failure is a known issue: https://daosio.atlassian.net/browse/DAOS-17751