I've had the same issue, turns out it resets itself everytime you
configure the network interfaces *and* although you "fix it" it wont
"save" the config until I saw the tick box (scroll down) to do so ;) ...
Caught me up a couple times and was going to report it as a bug next week.
The solution is not to reset the node, it's to manually reconfigure the
NIC to have the same / old IP address, the node will come back to live
which then enables you to re-save the network config by setting it to
manual and ticking the box ;)
Alex
On 12/21/2012 08:49 AM, Kevin Maziere Aubry wrote:
Hi all
System : Fedora 17
On node :
Libvirt 0.10
Kernel Linux node1 3.6.10-2.fc17.x86_64
Stable VDSM from repo
On manager :
Ovirt 3.1 stable
Kernel Linux ovirt-manager 3.5.4-1.fc17.x86_64
By default the ovirtmgmt interface is created on node as a bridge with
the same parameters than p1p1. That is good so that you keep network
working on the node.
I've setup a new tagged network on Ovirt, which I have to add to all
the node of my cluster.
So I plug this new network on p1p2, do not touch to ovirtmgmt network,
and apply... and the server is lost.
In fact when reconfiguring the network the ovirtmgmt card is set to
DHCP, which is the problem.
And the only solution to make vdsm back online, is to reset the
complete node.
Kévin
--
Kevin Mazière
Responsable Infrastructure
Alter Way -- Hosting
1 rue Royal - 227 Bureaux de la Colline
92213 Saint-Cloud Cedex
Tél : +33 (0)1 41 16 38 41
Mob : +33 (0)7 62 55 57 05
http://www.alterway.fr <http://www.alterway.fr/>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
