Ondra, do you want me to add an ovirt-ansible-modules component in ovirt-distribution? Or do you want to close this with resolution upstream and open an issue on https://github.com/ansible/ansible-modules-extras/issues ?

In my opinion we should close this as upstream and issue should be opened at github, but QE wants to track the issues in BZ.

Martin, can we somehow agree on reasonable process?

Sandro, adding new component as ovirt-ansible-modules would be preferable, QE needs to track these issues, and I doubt anyone will check github issues, thus BZ.

However bugzilla does not have any external tracker interface for github issue, so created github issues has to be linked within comment.

(In reply to Lukas Svaty from comment #3)
> Sandro, adding new component as ovirt-ansible-modules would be preferable,
> QE needs to track these issues, and I doubt anyone will check github issues,
> thus BZ.
> 
> However bugzilla does not have any external tracker interface for github
> issue, so created github issues has to be linked within comment.

I prefer upstream. Find a way to track it (using a label, for example). Or create a tracker bug with all links, or just a spreadsheet. We are not providing the modules.

Just a note that user can still fetch info about what disk IDs are attached to vm, which is IMO much more important:

  - name: Fetch VM disk IDs
    ovirt_vms_facts:
      auth: "{{ ovirt_auth }}"
      pattern: name=vm
      fetch_nested: true
      nested_attributes: disk
  
  - name: Print VM disks IDs
    debug:
      var: item.disk.id
    with_items: "{{ ovirt_vms[0].disk_attachments }}"

Or to print VM disks names:

  - name: Get VM disks names
    ovirt_disks:
      auth: "{{ ovirt_auth }}"
      id: "{{ item.disk.id }}"
    with_items: "{{ ovirt_vms[0].disk_attachments }}"
    register: disks
  
  - name: Print VM disks names
    debug:
      var: item.disk.name
    with_items: "{{ disks.results }}"

Need to check out what searches our backend for disks support to see if it worth to implement ovirt_disks_facts.

As agreed please open this issue at github.