Skip to content

DAOS-18963 cart: Add rpc origin address#18262

Open
frostedcmos wants to merge 1 commit into
release/2.6from
frostedcmos/DAOS-18963-2.6
Open

DAOS-18963 cart: Add rpc origin address#18262
frostedcmos wants to merge 1 commit into
release/2.6from
frostedcmos/DAOS-18963-2.6

Conversation

@frostedcmos
Copy link
Copy Markdown
Contributor

  • Add stringified rpc origin address to rpc_priv
  • Print origin from RPC_* (e.g. RPC_INFO() ) macros, as well as during failed bulk transfers or failures to send reply

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

- Add stringified rpc origin address to rpc_priv
- Print origin from RPC_* (e.g. RPC_INFO() ) macros, as well as during failed bulk transfers or failures to send reply

Signed-off-by: Alexander A Oganezov <alexander.oganezov@hpe.com>
@frostedcmos frostedcmos requested review from a team as code owners May 15, 2026 18:46
@github-actions
Copy link
Copy Markdown

Ticket title is 'cart: Print RPC origin address'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-18963

@github-actions github-actions Bot added the priority Ticket has high priority (automatically managed) label May 15, 2026
@frostedcmos frostedcmos added the unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving. label May 15, 2026
@daosbuild3
Copy link
Copy Markdown
Collaborator

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

Labels

priority Ticket has high priority (automatically managed) unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving.

Development

Successfully merging this pull request may close these issues.

3 participants