Description of problem: Selecting additional disks with Image based provisioning doesn't actually get reflected on VM. I selected an additional disk, but the VM yaml on CNV doesn't have that ``` devices: disks: - disk: bus: virtio name: homer-ejide-example-com-disk-00 interfaces: - bootOrder: 1 bridge: {} macAddress: 'a2:a2:a2:a2:a2:a2' name: default machine: type: '' resources: requests: memory: 1024M networks: - name: default pod: {} terminationGracePeriodSeconds: 0 volumes: - containerDisk: image: kubevirt/fedora-cloud-registry-disk-demo name: homer-ejide-example-com-disk-00 ``` An additional disk was selected from UI Version-Release number of selected component (if applicable): Master of plugin How reproducible: Steps to Reproduce: 1.Add a disk to host config with Image based provisioning 2. 3. Actual results: The VM doesn't actually get the additional disk selected Expected results: Should have multiple disks as selected Additional info:
This seems working on latest nightly Foreman + plugin master, But VM creation still fails due to https://bugzilla.redhat.com/show_bug.cgi?id=1697286
Verified with Sat 6.6 snap 13. 1. Have a Kubevirt CR 2. Hosts -> Create host 3. Deploy on Kubevirt 4. OS -> Image Based 5. VM -> Add 2 volumes 6. Fill the rest, Submit => VM created, volumes visible in Sat, YAML contains: devices: disks: - bootOrder: 1 disk: bus: virtio name: disks-testdom-example-com-disk-00 - disk: bus: virtio name: disks-testdom-example-com-disk-01 - disk: bus: virtio name: disks-testdom-example-com-disk-02 volumes: - containerDisk: image: kubevirt/cirros-container-disk-demo name: disks-testdom-example-com-disk-00 - name: disks-testdom-example-com-disk-01 persistentVolumeClaim: claimName: disks-testdom-example-com-claim-1 - name: disks-testdom-example-com-disk-02 persistentVolumeClaim: claimName: disks-testdom-example-com-claim-2
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-2019:3172