Skip to content

DAOS-19791 dlck: fix rc, errors and warnings counting and reporting - #19325

Open
janekmi wants to merge 4 commits into
masterfrom
janekmi/DAOS-19791-dlck-rc-err-warn-num-counting-fix
Open

janekmi wants to merge 4 commits into
masterfrom
janekmi/DAOS-19791-dlck-rc-err-warn-num-counting-fix

Conversation

@janekmi

@janekmi janekmi commented Oct 19, 2026

Copy link
Copy Markdown
Contributor
  • track both the number of errors and warnings per target
  • reset status (counters and rc) at each step so they do not affect each other
  • do not fail iteration. Callbacks always have to return 0. A corrupted node does not have to stop the iteration. We cannot continue processing nodes down the failed path.
  • do not return a code from the xxx_process() functions. It is always ignored anyway. Make sure the code is recorded in the status though.
  • report the pool validation result always, not only on success.
  • refactor collecting statuses from targets so all: rc, errors num and warnings num are passed to the reporting function
  • refactor the report printing functions to accomodate all aspects of the status (rc, errors_num and warnings_num)
  • fix one CK_PRINTF (not an error) -> CK_PRINTF_ERR (error)
  • a couple minor fixes where not a correct return code was printed.

Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-el-9.6-rpms: true
Skip-test-leap-15-rpms: true
Skip-func-hw-test: true

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

- track both the number of errors and warnings per target
- reset status (counters and rc) at each step so they do not affect each
  other
- do not fail iteration. Callbacks always have to return 0. A corrupted
  node does not have to stop the iteration. We cannot continue
processing nodes down the failed path.
- do not return a code from the `xxx_process()` functions. It is always
  ignored anyway. Make sure the code is recorded in the status though.
- report the pool validation result always, not only on success.
- refactor collecting statuses from targets so all: rc, errors num and
  warnings num are passed to the reporting function
- refactor the report printing functions to accomodate all aspects of
  the status (rc, errors_num and warnings_num)
- fix one CK_PRINTF (not an error) -> CK_PRINTF_ERR (error)
- a couple minor fixes where not a correct return code was printed.

Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-el-9.6-rpms: true
Skip-test-leap-15-rpms: true
Skip-func-hw-test: true

Signed-off-by: Jan Michalski <jan-marian.michalski@hpe.com>
@janekmi
janekmi requested review from NiuYawei and grom72 October 19, 2026 23:29
@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Ticket title is 'dlck: fix rc, errors and warnings num handling'
Status is 'In Review'
https://daosio.atlassian.net/browse/DAOS-19791

@janekmi
janekmi requested review from a team as code owners October 19, 2026 23:29
@janekmi
janekmi requested review from Nasf-Fan and removed request for NiuYawei October 20, 2026 07:38
Doc-only: true
skip-cancel-previous-builds: true

Signed-off-by: Jan Michalski <jan-marian.michalski@hpe.com>
Comment thread src/utils/dlck/cmds/dlck_cmd_check.c
Comment thread src/utils/dlck/cmds/dlck_cmd_check.c Outdated
Comment thread src/utils/dlck/dlck_engine.h Outdated
Comment thread src/utils/dlck/dlck_report.c
Comment thread src/utils/dlck/dlck_report.c Outdated
Comment thread src/utils/dlck/dlck_report.c
- rename dlck_xstream_status_set_rc -> dlck_status_set_rc
- rename dlck_xstream_status_set -> dlck_status_set
- make dlck_status_set reset rc of the input status
- make dlck_report_results' total account for rcs from targets
- revert random change in conts_process

Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-el-9.6-rpms: true
Skip-test-leap-15-rpms: true
Skip-func-hw-test: true

Signed-off-by: Jan Michalski <jan-marian.michalski@hpe.com>
@janekmi
janekmi requested a review from Nasf-Fan October 22, 2026 16:06
Nasf-Fan
Nasf-Fan previously approved these changes Oct 23, 2026
Signed-off-by: Jan Michalski <jan-marian.michalski@hpe.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants