A community member I met in FOSDEM mentioned this issue to me, and I've just seen[1] it is fixed in latest Foreman - when provisioning VMs via Foreman, the OS is now properly set in oVirt.