-
Notifications
You must be signed in to change notification settings - Fork 475
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
Snapshots details not included in one.vmpool.infoextended #4136
Comments
Can you provide more information about how are you testing this issue and which OpenNebula version are you using? I've tried for OpenNebula 5.10.1 by doing the XML-RPC directly and it does retrieve snapshots information:
|
@christian7007 I re-verified your finding by doing xml-rpc directly as well in Python and snapshots does appear. But, when I use |
@christian7007 Found the source of issue. https://github.com/OpenNebula/one/blob/master/share/doc/xsd/vm_pool.xsd is missing the |
Good catch, thanks! This should be fixed in the upcoming release. |
Sure, I closed my duplicate. If you want to make gitcop happy you need wrap whole commit message to max 50 chars per line. |
@xorel Thanks. I edit it directly, is it possible to edit commit message after commit. |
I guess you need to git amend and force push. |
* B OpenNebula/one#4136 Add xsd fix to res. issues * M #-: Fix links formatting in resolved issues
Co-authored-by: Ahmed Bilal Khalid <ahmedbilal96@gmail.com> (cherry picked from commit 8df3e4a)
Description
Disk snapshot details are not present in output of
one.vmpool.infoextended
.To Reproduce
Try to perform the
one.vmpool.infoextended
XML-RPC and inspect the output.Expected behavior
Snapshot details should be present in
one.vmpool.infoextended
output but it isn't.Additional context
Although, the detail can be obtained by individually getting it using
one.vm.info
but that is tiresome and takes too much time in case of hundreds of VMs.https://github.com/OpenNebula/one/blob/2ff0324bb224dd73d246b864bd0cd9eea115e998/share/doc/xsd/vm.xsd
Progress Status
The text was updated successfully, but these errors were encountered: