Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollback support of DM parameters handled in RBUS #225

Open
sundar2k opened this issue Oct 17, 2024 · 0 comments
Open

Rollback support of DM parameters handled in RBUS #225

sundar2k opened this issue Oct 17, 2024 · 0 comments

Comments

@sundar2k
Copy link

Currently the rollback is the scope of the provider component that uses the RBus APIs to set the DM parameters. Incase, if the set fails, the provider to revert to the original value

This approach creates an bug when using the rbus_setMulti API to set multiple DM parameter using this single API call.
If one or more DM parameter set fails during this multiSet operation, the current API only logs the failure, but still returns success to the provider. This eventually leads to error condition.
The implementation for rollback to be handled in the Rbus layer itself, so as if any DM parameters set fails it should revert to the original value and notify the provider with the right return code
This is of the requirement for USP for the atomic set operations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant