On Tue, Dec 29, 2015 at 9:56 AM, Alan Murrell <lists@murrell.ca> wrote:
On 28/12/2015 11:29 PM, Yedidyah Bar David wrote:
Did you principally do exactly the same thing in 3.5 and 3.6?
I did. I basically followed "Up and Running with oVirt 3.5", except I used 3.6 packages.
In both cases just had a simple network interface (no vlan/bonding/whatever) and input it when asked?
Well, I pre-created the 'ovirtmgmt' bridge, as I had to do that under 3.5 otherwise I ran into problems during setup. I can't recall offhand what the bug was (I posted about it a while back), but perhaps whatever it was has been fixed in 3.6, and I shouldn't pre-create the 'ovirtmgmt' bridge?
It should have worked also in 3.5 in principle, not sure about your specific problems. In principle pre-creating the bridge should work, but is not commonly tested. Perhaps you also had issues with NetworkManager?
After I sent my earlier e-mail on this issue, I played around with a couple things and actually got it up and working (the interfaces turned green, etc.). As a test, I rebooted the host, but now I can't even ping the host. it is at the office, so I won't have physical access to it until I go in in a few hours.
What exact versions (OS and ovirt)?
CentOS 7 minimal (after 'yum update', I think it it 7.2?). oVirt is 3.6.1, I believe (whatever version is installed form latest repo packages)
Since I have lost access, I suspect something happened to the 'ovirtmgmt' interface. There is nothing on it that matters, so I may just do a fresh install, but without pre-creating the 'ovirtmgmt' bridge and see if the setup does it (which I understand itis supposed to?)
It is. Please open bugs if it does not work. Thanks and best regards, -- Didi