Description of problem: Currnetl host-deploy is disabling NetworkManager during deployment, this should not be necessary anymore once bug 1330128 is solved. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Solution here is a bit more complicated. As discussed with Fabian: NM must be running on all 4.0 hosts NM must NOT be running on all 3.6 hosts (even in a 4.0 env) how to achieve: on 4.0 hosts host-deploy needs to keep NM running on 3.6 hosts host-deploy needs to disable NM Thus host-deploy in 4.0 needs to differentiate the vdsm version. This can be done with the version form ./lib/vdsm/dsaversion.py.in
Rafael, can you handle this? I'll be busy next week and it's important for node.
oVirt 4.0 beta has been released, moving to RC milestone.
Deferring this bug until the complete story around NM is sane.