On 04/08/12 17:51, Jacob Wyatt wrote: > I just installed a new 3.1 engine and I have one node with the latest node > iso installed. After setting up one of the network interfaces on the node > and confirming I have network I am able to attach it to the engine. I've > done this starting from both the node and the engine and it seems to work > either way. Everything looks good until I go to the network controls in the > web interface. I need to configure another network interface but to do so > the ovirtmgmt network must be assigned to an interface. I'm not sure why it > isn't already since the node is already assigned to a cluster. If I attempt > to assign the management network it starts reconfiguring the node and then > irrecoverably breaks the network on the node. By irrecoverable I mean I have > to manually log in to the node as root and use ifdown to shut off all of the > interfaces, delete all of the network configs under /config and then restart > the machine and re-setup the network to get it back. Nothing less seems to ! res > tore network to the node. From what I can tell when the node is assigned to > a cluster the network looks good on the node side. It's running a bridge > named ovirtmgmt and seems to be happy. When the engine tries to assign > ovirtmgmt to the node it creates a new bridge named after the network > interface but is unable to start it. I've done a lot troubleshooting of > network issues on 3.0 and have been able to work around them, but I seem to > be at an impasse here. Without the additional network config my VM's won't > work. Is there another way to force the network configuration without using > the web interface? I know what the network setup should be. I've done all > kinds of manual bridging, bonding, etc. under Fedora. I just can't seem to > get oVirt to understand. > > -Jacob
Hi Jacob, You installed the engine from source? if so what is the engine hash commit you used for installation? The reason I am asking that is because we had a major regression last week were we broke the network API. It was fixed in commit fa95ed435ac824ae7fc721239d862337053202bc, I suggest you don't cherry pick this specific commit but rebase on it. Thanks, Livnat > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
