We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description
If new OneGate client (e.g., 5.9.80) is running against old OneGate server (e.g., 5.4.15), the update operation fails:
# onegate vm update --data key=value ERROR: [one.vm.update] Cannot update template. Parse error: syntax error, unexpected EQUAL, expecting $end at line 0, columns 22:23
Related to changes introduced by #1414, because format of data sent from client has changed: https://github.com/OpenNebula/one/pull/3252/files#diff-25cc1e51ebff40297b9dd487dd43be4dR596
To Reproduce Have old OneGate server and new OneGate client. Do update operation from inside VM.
Details
The text was updated successfully, but these errors were encountered:
B OpenNebula#3572: make onegate client compatible with old servers
135487e
PRs to merge in master:
code: #3643 docs: OpenNebula/docs#732 context: OpenNebula/addon-context-linux#184
Sorry, something went wrong.
B OpenNebula#3572: Change in onegate client
041a858
In order to ensure compatibility with old servers
B OpenNebula/one#3572: add updated onegate client
d52075c
LGTM.
B #3572: Change in onegate client to ensure compatibility with old se…
4ccf7f0
…rvers (#3643)
al3xhh
No branches or pull requests
Description
If new OneGate client (e.g., 5.9.80) is running against old OneGate server (e.g., 5.4.15), the update operation fails:
Related to changes introduced by #1414, because format of data sent from client has changed:
https://github.com/OpenNebula/one/pull/3252/files#diff-25cc1e51ebff40297b9dd487dd43be4dR596
To Reproduce
Have old OneGate server and new OneGate client. Do update operation from inside VM.
Details
Progress Status
The text was updated successfully, but these errors were encountered: