Skip to content

resident_on information in task at change watch shows in pool always the master #189

Open
@Winteriver

Description

@Winteriver

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:

{
allowed_operations: []
backtrace: "()"
created: "20190519T19:39:24Z"
current_operations: {}
error_info: []
finished: ""
name_description: ""
name_label: "VM.snapshot"
other_config: {}
progress: 1
resident_on: "OpaqueRef:36d4e8fd-7a8f-49c1-a9e8-4e38940a1302"
result: ""
status: "pending"
subtask_of: "OpaqueRef:NULL"
subtasks: []
type: "<none/>"
uuid: "65ace88c-b425-2b16-e6f8-1f7d407dcfbb"
}

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

Tested with: XCP-ng 7.6.0

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions