Bug 787384

Summary: all-in-one - Unusable network configuration after adding 127.0.0.1 as host in webinterface
Product: [Retired] oVirt Reporter: Floris <bos>
Component: ovirt-engine-installerAssignee: Alex Lourie <alourie>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, dfediuck, iheim, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 08:04:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Disables "NetworkManager" service, enables "network" service on Fedora hosts
none
jboss server log none

Description Floris 2012-02-04 17:11:20 UTC 
- minimal Fedora 16 kickstart installation
- installed oVirt management software using the instructions: http://www.ovirt.org/wiki/Installing_ovirt-engine_from_rpm
- added 127.0.0.1 as host in the admin webinterface

Excepted behavior:

- Being able to run virtual machines on the management server

Actual behavior:

- the oVirt software installs stuff, reboots, and the user is locked out of his server, because network settings are broken.


/var/log/messages contains "ifcfg-rh: error: Bridge connections are not yet supported"

I think the installation script didn't disable the NetworkManager service that doesn't understand bridge connections?

And I'm not sure if using the management server as node is actually supported, but if it is not, the webinterface should refuse to add the host, as I'm quite sure others will try to do the same thing as me.
Comment 1 Floris 2012-02-05 19:50:03 UTC 
Created attachment 559489 [details]
Disables "NetworkManager" service, enables "network" service on Fedora hosts
Comment 2 Floris 2012-02-05 19:55:58 UTC 
Created attachment 559499 [details]
jboss server log

Apart from the networkmanager problem for which I posted a patch, there are still some other issues when adding the management server as host to the system using the webinterface:

- "override IP tables" is checked by default, but the iptables configuration it loads doesn't open up the management ports (like 8080,8443)

- not sure if it's related to using the management server as a node, but the jboss webapplication often seems to crash shortly after boot, attached server.log
Comment 3 Itamar Heim 2012-02-06 07:18:28 UTC 
This is related to a flow we call "all-in-one", mostly for simple trial deployments, as there are issues with using this for more than this, if adding other hosts to the same DC as the engine is in.
there are some patches going upstream around this, but will probably be based on a dedicated flow/script, rather than via UI.

in any case, using 127.0.0.1 should be avoided, since it will not allow live migration (or storage live migration later on) with that host.

moving to installer component for now, although there is some work around core as well.
Comment 4 Alex Lourie 2012-05-24 10:02:58 UTC 
The installer now includes an all-in-one plugin, which allows performing an installation of oVirt and configure VDSM on the same machine during setup. The development of the plugin included addressing various issues that we previously had (including backend and ovirt-sdk).

This should solve the problem of adding/configuring localhost as the vdsm host.
Comment 5 Itamar Heim 2012-08-09 08:04:48 UTC 
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/