The problem was reproduced with Public ISO #44 Jul 27, 2014 https://fuel-jenkins.mirantis.com/view/ISO/job/publish_fuel_community_iso/17/ After the deployment of Compute nodes finished, a user have to manually run 'modprobe -a kvm; modprobe -a kvm-intel; service libvirtd restart;' on each Compute node.
Can you check, is this related to package or to Puppet manifests?
The problem was reproduced with Public ISO #44 Jul 27, 2014 /fuel-jenkins. mirantis. com/view/ ISO/job/ publish_ fuel_community_ iso/17/
https:/
After the deployment of Compute nodes finished, a user have to manually run 'modprobe -a kvm; modprobe -a kvm-intel; service libvirtd restart;' on each Compute node.
Can you check, is this related to package or to Puppet manifests?