Description of problem: ovirt-node makes no use whatsoever of NetworkManager. Currently vdsm networking experiences issues when NM is running. Thus, it is advisable that it would be disabled on the node image. Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.0-5.0.5.vdsm.fc19.iso How reproducible: Steps to Reproduce: 1.Install ovirt-node 2.drop to shell using F2 3.systemctl status NetworkManager Actual results: loaded(active) Expected results: inactive(dead) Additional info:
fixing in ovirt-node-plugin-vdsm instead of core ovirt-node
Why are we limiting ourselves to F19? I would prefer to block NetworkManager until vdsm plays nicely with it, be it F20 or F21.
my preference is to handle this long term in ovirt-node directly either by removing NetworkManager completely or ensuring that it's disabled by default. I'd also argue that vdsm could (should?) disable NetworkManager if it's a problem for vdsm...
(In reply to Mike Burns from comment #3) > > I'd also argue that vdsm could (should?) disable NetworkManager if it's a > problem for vdsm... Our problem with this is that users may want to disable NetworkManager as long as they intend to play with host configuration via oVirt, but later re-enable NM.
We should consider changing the kickstart file for ovirt-node to have -NetworkManager, no reason to ship it with the node.
(In reply to Dan Kenigsberg from comment #4) > (In reply to Mike Burns from comment #3) > > > > I'd also argue that vdsm could (should?) disable NetworkManager if it's a > > problem for vdsm... > > Our problem with this is that users may want to disable NetworkManager as > long as they intend to play with host configuration via oVirt, but later > re-enable NM. Not supported on ovirt-node (you can't enable/disable services like that) (In reply to Antoni Segura Puimedon from comment #5) > We should consider changing the kickstart file for ovirt-node to have > -NetworkManager, no reason to ship it with the node. We're looking at using NM apis for working with network config in the near future, so removing it long term is not an option, disabling is.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.