-
Bug
-
Resolution: Done
-
Minor
-
4.12
-
None
-
No
-
False
-
Description of problem:
Documentation change related to the following If you are running OpenShift Container Platform on IBM Z with RHEL KVM, you must assign a serial number to your VM disk. Otherwise, the VM disk can not be identified after reboot. You can use the virsh edit <VM> command to add the <serial>mydisk</serial> definition.
Version-Release number of selected component (if applicable):
4.12
Additional info:
I don't see real reason why it will be different on IBM Z and x86-64 platform. I guess diskmaker-manager pod created the /mnt/local-storage/<storageclass_name>/<dev_disk/by-id_driver-serial> for all platform the same way. We have reproduced this issue on X86-64 cluster and we had to put serial in virsh to make it works. Please discuss it with engineering for a second feedback, but I guess this recommendation should be platform independant.