I'm closing this issue on WORKSFORME because this feature already exists.

Where can I set it? I don't see any changes in 6.3.1, there's Size, Storage domain, Preallocate disk and Bootable.

Created attachment 1457433 [details]
Storage form

you can find the disk interface under `Storage` (in virtual machine tab)

This does not exist in 6.3.1. Is it part of a minor update which we did not applied yet?

Looks like this will only be available in 6.4

I checked this through WebUI and creating, importing and associating host works as expected.

How can I create a volume and specify its type through Hammer? I can't find it in help.

hey, please run 'hammer host create --help', 
part of the output is as following:
  oVirt:
    --compute-attributes:
      cluster
      template            Hardware profile to use
      cores               Integer value, number of cores
      memory              Amount of memory, integer value in bytes
      start               Boolean (expressed as 0 or 1), whether to start the machine or not

    --interface:
      compute_name        Eg. eth0
      compute_network     Select one of available networks for a cluster

    --volume:
      size_gb             Volume size in GB, integer value
      storage_domain      Select one of available storage domains
      bootable            Boolean, only one volume can be bootable

I still can't see how to specify interface type. Which is what this BZ is about. Note, network interface type != disk interface type.

It's missing from hammer, please open a new BZ for hammer.

The functionality should be available through WebUI & Hammer & API. I think this BZ clearly failed verification so instead of verifying it and opening a new one, I'm setting this one back to assigned.

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/21762 has been resolved.

Bryan, I think you (or more likely, your bot) changed the status by mistake. Setting back to ASSIGNED.

Setting FailedQA so that the script will not reset this.

Lukas,
The functionality is in hammer, but it missing from the help. 
if you will add interface=<your interface (for example id)> under --volume section that will work, 
please try and let me know if it worked for you.

It works for API v3.

It doesn't work for API v4 due to bug 1665134.

Setting this back to ASSIGNED due to missing help content.

Back to Shira.

The bug this depends on was updated and the error there needs to be fixed but was a result of wrong parameters so it should not block testing for this bug.

From the other bug it seems all that is missing here is the documentation in hammer.

Setting back to ASSIGNED due to the same reason as mentioned in comment 17 (missing Hammer help content).

The help was added in the fix https://bugzilla.redhat.com/show_bug.cgi?id=1738894 : 
  oVirt:
    --volume:
      size_gb             Volume size in GB, integer value
      storage_domain      ID or name of storage domain
      bootable            Boolean, only one volume can be bootable
      preallocate         Boolean, set true to preallocate
      wipe_after_delete   Boolean, set true to wipe disk after delete
      interface           Disk interface name, must be ide, virto or virto_scsi

    --interface:
      compute_name        Compute name, e.g. eth0
      compute_network     Select one of available networks for a cluster, must be an ID or a name
      compute_interface   Interface type

    --compute-attributes:
      cluster             ID or name of cluster to use
      template            Hardware profile to use
      cores               Integer value, number of cores
      sockets             Integer value, number of sockets
      memory              Amount of memory, integer value in bytes
      start               Boolean (expressed as 0 or 1), whether to start the machine or not

Lukas, can you check again ?

Shira, I can check again and again but in Sat 6.7 snap 11, the help doesn't contain it:

# hammer host create --help
...
  oVirt:
    --volume:
      size_gb             Volume size in GB, integer value
      storage_domain      ID of storage domain
      bootable            Boolean, only one volume can be bootable
      preallocate         Boolean, set true to preallocate
      wipe_after_delete   Boolean, set true to wipe disk after delete

    --interface:
      compute_name        Compute name, e.g. eth0
      compute_network     Select one of available networks for a cluster, must be an ID
      compute_interface   Interface type

    --compute-attributes:
      cluster             ID of cluster to use
      template            Hardware profile to use
      cores               Integer value, number of cores
      sockets             Integer value, number of sockets
      memory              Amount of memory, integer value in bytes
      start               Boolean (expressed as 0 or 1), whether to start the machine or not
...

lukas, under --interface you have compute_interface which is the interface type.

Please, see my comment 10.

I opened a merged request to cherry-pick

Verified with Sat 6.7 snap 11. Used both WebUI and Hammer to create a host with volume of specified type:

hammer host create --compute-resource-id 1 --organization-id 1 --location-id 2 --name rhev3cli7 --domain-id 1 --subnet-id 1 --operatingsystem 'RedHat 7.7' --architecture x86_64 --provision-method image --image-id 1 --interface "compute_name=test,compute_network=<ID>,compute_interface=VirtIO" --volume "size_gb=20,storage_domain=<ID>,bootable=false,preallocate=false,wipe_after_delete=false,interface=ide"

The Hammer help now contains:

  oVirt:
    --volume:
      size_gb             Volume size in GB, integer value
      storage_domain      ID of storage domain
      bootable            Boolean, only one volume can be bootable
      preallocate         Boolean, set true to preallocate
      wipe_after_delete   Boolean, set true to wipe disk after delete
      interface           Disk interface name, must be ide, virto or virto_scsi

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454