Description of problem: - The ovirt_disk Ansible module allows you to define the 'bootable' parameter and run in playbooks regardless of whether the disk is attached to a virtual machine or not. - In a scenario where a new disk is created but not attached to a virtual machine and 'bootable: true', the playbook run is successful. However, the 'bootable' flag is not set. Version-Release number of selected component (if applicable): How reproducible: Fully Steps to Reproduce: Using ovirt_disk Ansible module, 1. Create new disk with 'bootable: true' and not attached to VM. Actual results: Disk is created and 'bootable' flag is not set. Expected results: Playbook run should display warning or fail if the disk is not attached to a virtual machine and contains 'bootable: true' Additional info: - Only disks attached to a virtual machine can have the bootable flag set in RHV. - Documentation for the 'bootable' parameter needs to be updated to include this information (https://console.redhat.com/ansible/automation-hub/repo/published/redhat/rhv/content/module/ovirt_disk)
Verified in ovirt-ansible-collection-2.0.3-1.el8ev.noarch Expected results met: [WARNING]: Cannot use 'interface', 'activate', 'bootable', 'uses_scsi_reservation' or 'pass_discard' without specifing VM.
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 (Moderate: RHV Engine and Host Common Packages security update), 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-2022:4712
Due to QE capacity, we are not going to cover this issue in our automation