+++ This bug was initially created as a clone of Bug #987813 +++
Description of problem:
Adding a newly installed host with Fedora 19 to the engine: failed to configure management network on host: 'ovirtmgmt'
The system has only 1 nic, em1, configured with boot=dhcp.
Version-Release number of selected component (if applicable):
Fedora 19, ovirt-engine 3.3 nightly - git0c5620a, adding to 3.3 cluster
It's different from bug #895080 because host-deploy exit with success.
I'll attach the host-deploy log.
--- Additional comment from Sandro Bonazzola on 2013-07-24 04:14:10 EDT ---
--- Additional comment from Sandro Bonazzola on 2013-07-24 04:28:00 EDT ---
after some investigation I've seen that the failing seems due to missing ifcfg-em1 file in network-scripts directory.
The interface was up thanks to networkmanager but the file for the legacy network script was not there.
creating the ifcfg-em1 file allow to add the host without failures.
--- Additional comment from Sandro Bonazzola on 2013-07-24 06:28:53 EDT ---
On the host there is vdsm-4.12.0-0.1.rc3.fc19.x86_64 from ovirt-beta repo
--- Additional comment from Sandro Bonazzola on 2013-07-24 06:33:16 EDT ---
--- Additional comment from Sandro Bonazzola on 2013-07-24 06:33:54 EDT ---
--- Additional comment from Sandro Bonazzola on 2013-07-24 06:34:36 EDT ---
--- Additional comment from Moti Asayag on 2013-07-24 08:54:49 EDT ---
Looking at the first getVdsCaps reveals that the cfg{} element is empty, while the engine uses to read the boot protocol information from it:
'nics': {'em1': {'netmask': '255.255.255.0', 'addr': '192.168.1.107', 'hwaddr': 'b8:ca:3a:76:9a:43', 'cfg': {}, 'ipv6addrs': ['fe80::baca:3aff:fe76:9a43/64'], 'speed': 1000, 'mtu': '1500'}},
--- Additional comment from Dan Kenigsberg on 2013-07-26 04:34:09 EDT ---
Vdsm still requires ifcfg-based host configuration to function properly, and I do not see this changing for ovirt-3.3 :-(
--- Additional comment from Assaf Muller on 2013-10-13 02:35:57 EDT ---
I'm confused - Why is this an RFE?
Isn't this a bug? Does anyone know why the ifcfg file wasn't created during the initial setupNetworks, as it should have?
--- Additional comment from Dan Kenigsberg on 2013-11-19 08:08:15 EST ---
Some flavors of Fedora installation make without the legacy ifcfg files. We've never claimed to support something like that, hence the "RFE".
We should make without the ifcfg, too, and report the values from the system (that's easier for BONDING_OPTS, a bit harder for BOOTPROTO).
--- Additional comment from John Skeoch on 2014-01-12 20:23:51 EST ---
User hateya's account has been closed
--- Additional comment from Douglas Schilling Landgraf on 2014-01-24 08:45:59 EST ---
--- Additional comment from Itamar Heim on 2014-02-13 16:26:59 EST ---
is this still targeted for 3.4?
--- Additional comment from Dan Kenigsberg on 2014-02-13 19:17:30 EST ---
No, it's not done yet.
Truly verifying this requires some tweaks to vdsm. I suggest that you are an after_get_caps hook that strips vdsm of all 'cfg' content. Then, make sure that Engine is happy with the state of the host's networking.