Description of problem: Add the ability to create an ISO disk container via SDK as in REST. Currently, this option does not exist. I use python-ovirt-engine-sdk4-4.2.2-2.el7.centos.x86_64 ( which is the latest I could find in bob) . From /usr/lib64/python2.7/site-packages/ovirtsdk4/types.py -> Class Disk -> Only the following kwargs exist: class Disk(Device): def __init__( self, active=None, actual_size=None, alias=None, bootable=None, comment=None, description=None, disk_profile=None, format=None, id=None, image_id=None, initial_size=None, instance_type=None, interface=None, logical_name=None, lun_storage=None, name=None, openstack_volume_type=None, permissions=None, propagate_errors=None, provisioned_size=None, qcow_version=None, quota=None, read_only=None, sgio=None, shareable=None, snapshot=None, sparse=None, statistics=None, status=None, storage_domain=None, storage_domains=None, storage_type=None, template=None, total_size=None, uses_scsi_reservation=None, vm=None, vms=None, wipe_after_delete=None, ): In REST: create an ISO disk container in the REST-API exit within the request: <disk> .... <content_type>iso</content_type> .... </disk> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The SDK is not yet updated to use the new model, will keep this bug open as a tracker for the issue and will update when it is taken care of
Tal, I assume the API/SDK is self-documenting, so we don't need any additional docs here, right? (marking "requires-doctext?" until the needinfo is answered, just to stay on the safe side).
Yes, all is documented in the API docs
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra
verified at 4.2.1.3-0.1.el7.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.