Description of problem: Image based provisioning should have bootorder: 1 for the containerDisk a example yaml from a VM created from KubeVirt console ``` devices: disks: - bootOrder: 1 disk: bus: virtio name: rootdisk - disk: bus: virtio name: test-noboot interfaces: - bridge: {} name: nic0 rng: {} machine: type: '' resources: requests: memory: 4G networks: - name: nic0 pod: {} terminationGracePeriodSeconds: 0 volumes: - containerDisk: image: kubevirt/fedora-cloud-registry-disk-demo name: rootdisk - dataVolume: name: test-noboot-test-fedora name: test-noboot ``` Version-Release number of selected component (if applicable): master of the plugin How reproducible: Steps to Reproduce: 1.Create a Image based host 2. 3. Actual results: The provisioning works, but should have the bootorder defined Expected results: Additional info:
This seems working on latest nightly Foreman + plugin master
Verified with Sat 6.7 snap 16. A disk tied to contanerDisk volume has indeed bootorder 1 specified in yaml.
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