Created attachment 1638519 [details] instance log In BZ1760272 an issue to create and boot instances created with "os_distro=rhel7.5" is fixed. Old instances that were created with the previous configuration required to be changed at database level. With this change, old instances can boot. The issue is that trying to resize those old instances fail with the same error message. 2019-11-19 16:21:59.611 21458 ERROR nova.compute.manager [instance: 2ad4e2b9-4b2e-4030-8b6c-417b5f64af4d] UnsupportedHardware: Requested hardware 'virtio1.0-block' is not supported by the 'kvm' virt driver 2019-11-19 16:21:59.611 21458 ERROR nova.compute.manager [instance: 2ad4e2b9-4b2e-4030-8b6c-417b5f64af4d] 2019-11-19 16:22:00.157 21458 INFO nova.compute.manager [req-b5f0968c-77f8-4c61-bb43-1e9ab94f7bc6 0bb110d62bc14529b98c99c43ecff1b5 8c9e0ad42a5c4deb90c69608604558cf - - -] [instance: 2ad4e2b9-4b2e-4030-8b6c-417b5f64af4d] Successfully reverted task state from resize_finish on failure for instance.
For OSP-10, I think this should already fixed by the following Nova version: openstack-nova-14.1.0-59.el7ost ... which was resolved as part of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1763258 (Requested hardware 'virtio1.0-block' is not supported by the 'kvm' virt driver") If you are _not_ using the above Nova version (openstack-nova-14.1.0-59.el7ost), can you please update to it, re-test, and confirm that it resolves? (Then, we can mark this bug as a duplicate of 1763258.)
Hi Kashyap, I will request local team to test with a newer version and let you know if it works or not.
(In reply to Mikel Olasagasti from comment #2) > Hi Kashyap, > > I will request local team to test with a newer version and let you know if > it works or not. Mikel, Ping — any update from the customer here, based on what I requested in comment#1? We can close this as a duplicate of 1763258; just wanted double-confirmation. (If you're able to reproduce with the correct version I noted in comment#1, then feel free to re-open.)
*** This bug has been marked as a duplicate of bug 1763258 ***