DAOS-16661 common: PMDK error/warnings to VOS logging (#14923)#17595
DAOS-16661 common: PMDK error/warnings to VOS logging (#14923)#17595grom72 wants to merge 3 commits intorelease/2.6from
Conversation
Integrate PMDK logging system w/ VOS logging pmemobj error and warning messages are written by default to stderr and syslog(). PMDK enables redirecting logging messages to user-specific functions. All error and warning messages are reported using the DAOS logging function, to ensure a coherent events view for VOS and related pmemobj functions. Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
|
Ticket title is 'Integrate PMDK logging system w/ VOS logging system.' |
|
Test stage NLT on EL 8.8 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17595/2/testReport/ |
grom72
changed the title
utils/rpms/daos.spec
Outdated
| * Wed Feb 25 2026 Tomasz Gromadzki <tomasz.gromadzki@hpe.com> 2.6.-17 | ||
| - pmemobj errors and warnings reported via DAOS logging system |
There was a problem hiding this comment.
why does this require a bump to the release version?
There was a problem hiding this comment.
why does this require a bump to the release version?
Fixed in 42fb25a
There was a problem hiding this comment.
i mean why is it required to bump this?
you have no changes to the spec file, so you do not need to touch this file as far as i recall. so could you please explain why this is required (both here and the debian changelog)
There was a problem hiding this comment.
i do not see any change to the packaging so im not clear why you are adding a new entry in the spec file
There was a problem hiding this comment.
I have inherited this approach from master branch indicating clearly that from now VOS log also contains libpmemobj errors/warnings.
* Wed Jul 30 2025 Tomasz Gromadzki <tomasz.gromadzki@hpe.com> 2.7.101-12
- pmemobj errors and warnings reported via DAOS logging system
It is a change that is visible outside the DAOS system.
For example, if somebody had a tool to parse DAOS/vos log, it must be prepared for new type of message (i.e. HARK).
There was a problem hiding this comment.
sorry but this does not make sense to me.. it sounds like the master change itself is wrong.
there is no packaging change here, no dependencies are being upgraded or added. what you are describing should not require a release version bump.
tools can rely on the library version for this distinction .. i do not see how anyone would use RPM versions for functionality or logging changes in their code.
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com> Doc-only: true
github-actions
bot
added
the
priority
Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
4 participants
Integrate PMDK logging system w/ VOS logging
pmemobj error and warning messages are written by default to stderr and syslog(). PMDK enables redirecting logging messages to user-specific functions.
All error and warning messages are reported using the DAOS logging function, to ensure a coherent events view for VOS and related pmemobj functions.
Backport of #14923
Steps for the author:
After all prior steps are complete: