Description of problem: Previously libvirt was configured to work well with vdsm, as vdsm i sno longe rpart of core node we should create a sane config which works by default.
This will need communication with Douglas to ensure that the libvirt file is updated/replaced with a correct version when th evdsm-plugin is installed. So vdsm has the configuration it expects. Douglas, the idea is here that ovirt-node carries a libvirt configuration which works like a standalone steup.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed. If this is a blocker please add it to the tracker Bug #1095370
This is an automated message: oVirt 3.4.2 has been released. This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
(In reply to Fabian Deutsch from comment #1) > This will need communication with Douglas to ensure that the libvirt file is > updated/replaced with a correct version when th evdsm-plugin is installed. > So vdsm has the configuration it expects. > > Douglas, the idea is here that ovirt-node carries a libvirt configuration > which works like a standalone steup. Ok, please let me know if you need anything from my side.
This is an automated message. oVirt 3.4.3 has been released while this bug was still open. The bug has been re-targeted to 3.4.4 accordingly.
Re-targeting since 3.4.4 has been released and only security/critical fixed will be allowed for 3.4.z. 3.5.0 is also in blockers only phase, so re-targeting to 3.5.1.
Since we're back under core oVirt and always including VDSM, I'm going to close this. Please re-open if it's still relevant.