Review known issues and include them in the 4.19 RNs, if relevant. They will be published here.

Issues:

https://issues.redhat.com/browse/CNV-60564(original OCPBUGS-51113) When a VM is created using RHEL bootable disk images provided, call traces are printed from virtio_balloon (memory ballooning) to the console. [update the existing, incorrect text]

• [Chandra] This issue still exists. Till the latest kernel is adopted in the RHEL (even CentOS/Fedora) guest images, the will continue to appear.
  The existing text on this issue needs update - Raised as https://issues.redhat.com/browse/CNV-60564

https://issues.redhat.com/browse/CNV-56889  In Openshift console> Virtualization perspective, a s390x based VM configuration BootMode currently shows as BIOS, UEFI, UEFI (Secure), but with these values a s390x VM fails as it supports only one bootmode IPL (Initial Program to Load).

https://issues.redhat.com/browse/CNV-56890  In Openshift console> Virtualization perspective, a s390x based VM configuration CPU topology currently allows editing the thread to more than 1. But qemu-kvm for s390x doesn’t allow me to define threads other than 1 as designed. So till this UI issue is fixed, if anyone modifies thread value to 1, VM goes into crashloopbackoff with error “qemu-kvm: S390 does not support more than 1 threads.”

https://issues.redhat.com/browse/CNV-61740 When creating s390x based VM via template, choosing ISO volumes prevents the VM from booting. The workaround is to go to the VM > Configuration > Storage, select the CDROM and change the interface from SATA to SCSI. Afterwards the VM will boot [create new RN]

• [Lakshmi] CDROM uses SATA interface when created from template

https://issues.redhat.com/browse/CNV-61957 GPU devices should not be shown for s390x VMs wherever they appear in the UI [create new RN]