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

CA-397599 XSI-1704 implement setter for blocked ops manually #5991

Merged
merged 2 commits into from
Sep 16, 2024

Conversation

lindig
Copy link
Contributor

@lindig lindig commented Sep 16, 2024

Backport ada0dc7

Currently the setter for field VM.blocked_oeprations is auto generated. Implement this explicitly such that we can update allowed operations which currently is not happening. Allowed operations are used by XenCenter to disable operations; this has led to operations becoming unavaliable because allowed operations where not aligned with blocked operations when blocked operations were updated.

Backport ada0dc7

Currently the setter for field VM.blocked_oeprations is auto generated.
Implement this explicitly such that we can update allowed operations
which currently is not happening. Allowed operations are used by
XenCenter to disable operations; this has led to operations becoming
unavaliable because allowed operations where not aligned with blocked
operations when blocked operations were updated.

Signed-off-by: Christian Lindig <[email protected]>
@@ -1659,6 +1659,15 @@ let set_domain_type ~__context ~self ~value =
Db.VM.set_HVM_boot_policy ~__context ~self
~value:(derive_hvm_boot_policy ~domain_type:value)

let set_blocked_operations ~__context ~self ~value =
Db.VM.set_blocked_operations ~__context ~self ~value
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for debug "%s" __FUNCTION__ here?

Copy link
Member

@psafont psafont Sep 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

__FUNCTION__ is not available in OCaml 4.08, it's also good for debugging, which is less of a need now that the patch has been tested in the master version

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed them; the logs in message forwarding should be enough.

Signed-off-by: Christian Lindig <[email protected]>
@lindig lindig merged commit 2f6028d into xapi-project:1.249-lcm Sep 16, 2024
5 checks passed
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

Successfully merging this pull request may close these issues.

3 participants