Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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
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: