-
Notifications
You must be signed in to change notification settings - Fork 283
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
resident_on information in task at change watch shows in pool always the master #3870
Comments
I suspect https://github.com/xapi-project/xen-api/blob/master/ocaml/xapi/taskHelper.ml#L43 It is set to the localhost where it is created and not modified, as far as I can see. I agree that this would provide more value when it would point to the host that executes a task. |
Thank you very much for you response! |
I'll raise (tomorrow) an internal ticket to track this. However, the best way to get this done would be to work on this and raise a pull request. |
Thanks for your (fast) response and for raising a ticket! |
I have created ticket CA-319021 for internal discussion and tracking. |
When watching changes with the xapi, all hosts of a pool receive all informations from every other host in that pool.
For example, when a snapshot is made at a slave of a Pool, the slave(s) and the master receive a task like:
Here - after my opinion - "resident_on" should display on which hosts that task has been started, like the documentation says:
http://xapi-project.github.io/xen-api/classes/task.html
"host ref resident_on - the host on which the task is running"
So "resident_on" should be the OpaqueRef of the slave, but it always shows the OpaqueRef of the master. This way it is not possible to assign the tasks to the right host.
The "resident_on" is working at the VMs and other stuff, but not with the tasks. Why? Is this a bug, or a feature? :D
The text was updated successfully, but these errors were encountered: