Description of problem: Currently he-setup can not be completed if Networkmanager is running, he-setup enforces the user to disable it. The justification seems to be that vdsm is not working with NM. Once bug 1330128 is solved, this bug can be solved as well. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 1330474 has been marked as a duplicate of this bug. ***
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
See the bug 1326798 is closed as dup on this bug, currently if we disabled Network Manager by default. All the networking relevant info can not be displayed in _cockpit_ UI at all.
(In reply to Ying Cui from comment #3) > See the bug 1326798 is closed as dup on this bug, currently if we disabled > Network Manager by default. All the networking relevant info can not be > displayed in _cockpit_ UI at all. correct me here, the bug 1330474 is closed as dup on this bug.
Note: There is a temporary workaround in NGN 3.6.6 to work around this issue
oVirt 4.0 beta has been released, moving to RC milestone.
Is this issue fixed with latest VDSM?
(In reply to Yaniv Dary from comment #8) > Is this issue fixed with latest VDSM? VDSM is still not managing a NetworkManager managed device but installing NetworkManager-config-server and ensuring that we have NM_CONTROLLED=no on each interface, it seams that NetworkManager doesn't interfere. See https://bugzilla.redhat.com/show_bug.cgi?id=1326798
Some clarification: 1. vdsm itself does not check/handle the networkmanager service 2. hosted-engine-setup checks for a running network manager. 3. host-deploy disables a running networkmanager during deployment. 1. at least in 4.0 NM will pull in the server config - this ensures that NM will not "touch" interfaces 3. can already be configured and is sufficient for 3.6, I suppos ein 4.0 it will be the default to _not_ disable NM Finally 2 - this bug - needs to be fixed to not check for a running NM anymore, because then it is okay that NM is running (because of 1. and 3. above). With all this three pieces in place, all main flow should be working with NM enabled.
Fabian, updates on this?
Yep, we need to wait until vdsm is capable of doing so. Dan, can this be a dependency of the NM blocker/tracker?
Fabian, I have tested with oVirt-4.1-snapshot and I could observe the following: 1. hosted-engine-setup doesn't enforces that NetworkManager should be stopped. 2. But while host-deploy happens ( when the host is added to RHV UI ), NetworkManager is disabled & stopped Is the above observation look correct ? Here is the console log for above mentioned point (1) where hosted-engine-setup doesn't enforce NM to be stopped. [root@ ~]# rpm -qa | grep ovirt-hosted-engine-setup ovirt-hosted-engine-setup-2.1.0.2-0.0.master.20170126102129.git85ecca3.el7.centos.noarch [root@cambridge ~]# systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-01-30 11:59:08 IST; 24h ago Docs: man:NetworkManager(8) Main PID: 960 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─ 960 /usr/sbin/NetworkManager --no-daemon ├─1100 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-ens4f0.pid -lf /var/lib/NetworkManager/dhclient-988b3c89-0812-4521-800e-dbf5f1efcf7f-ens4... └─1107 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eno2.pid -lf /var/lib/NetworkManager/dhclient-a795e74f-0c2f-4f2a-8bce-069d74df38f6-eno2.l... [root@ ~]# hosted-engine --deploy [ INFO ] Stage: Initializing [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and create a VM where you have to install the engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Hardware supports virtualization Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170131124343-h7j795.log Version: otopi-1.6.1_master (otopi-1.6.1-0.0.master.20170112125735.git5eb23cd.el7.centos) [ INFO ] Detecting available oVirt engine appliances [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Generating libvirt-spice certificates [WARNING] Cannot locate gluster packages, Hyper Converged setup support will be disabled. [ INFO ] Please abort the setup and install vdsm-gluster, glusterfs-server >= 3.7.2 and restart vdsmd service in order to gain Hyper Converged setup support. [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:
I assume that you are not using rhv-h. In that case, in order to test hosted-engine with NM still running, you would need to create a file before running hosted-engine-setup /etc/ovirt-host-deploy.conf.d/90-my-nm.conf with disableNetworkManager=bool:False
(In reply to Edward Haas from comment #14) > I assume that you are not using rhv-h. In that case, in order to test > hosted-engine with NM still running, you would need to create a file before > running hosted-engine-setup > > /etc/ovirt-host-deploy.conf.d/90-my-nm.conf > > with > > disableNetworkManager=bool:False This is not needed, ovirt-hosted-engine-setup is already setting that value according the value of OVEHOSTED_NETWORK/refuseDeployingWithNM where the default is True. If we have OVEHOSTED_NETWORK/refuseDeployingWithNM=bool:True, ovirt-hosted-engine-setup is going to check the status of NetworkManager and aboirting if NetworkManager is up. If we have OVEHOSTED_NETWORK/refuseDeployingWithNM=bool:False instead ovirt-hosted-engine-setup is going to ignore the initial status of NetworkManager and it's going to add disableNetworkManager=bool:False to /etc/ovirt-host-deploy.conf.d/70-hosted-engine-setup.conf If it's not working as described here we have a real bug: https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=src/plugins/gr-he-setup/engine/add_host.py;h=30de2c7b1e9ea11faf10a034b78bb63d4d3ab1d6;hb=refs/heads/ovirt-hosted-engine-setup-2.1#l400
What is your `grep disableNetworkManager /etc/ovirt-host-deploy.conf.d/*` SATHEESARAN ?
Tested now on latest 4.1 RHEVH: ovirt-imageio-common-1.0.0-0.el7ev.noarch ovirt-hosted-engine-ha-2.1.0.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.1.0.1-1.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-host-deploy-1.6.0-1.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch ovirt-node-ng-nodectl-4.1.0-0.20170104.1.el7.noarch libvirt-client-2.0.0-10.el7_3.4.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64 vdsm-4.19.4-1.el7ev.x86_64 sanlock-3.4.0-1.el7.x86_64 ovirt-vmconsole-host-1.0.4-1.el7ev.noarch mom-0.5.8-1.el7ev.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch ovirt-setup-lib-1.1.0-1.el7ev.noarch Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016 Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.3 NM is running before the deployment: # systemctl status NetworkManager -l● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-02-06 17:26:31 IST; 10min ago Docs: man:NetworkManager(8) Main PID: 1212 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─1212 /usr/sbin/NetworkManager --no-daemon └─1334 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp4s0f0.pid -lf /var/lib/NetworkManager/dhclient-b41203e1-e801-42b2-b55d-ced7e04e9dab-enp4s0f0.lease -cf /var/lib/NetworkManager/dhclient-enp4s0f0.conf enp4s0f0 Feb 06 17:26:33 localhost.localdomain NetworkManager[1212]: <info> [1486394793.5590] device (enp4s0f0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Feb 06 17:26:33 localhost.localdomain NetworkManager[1212]: <info> [1486394793.5593] device (enp4s0f0): state change: secondaries -> activated (reason 'none') [90 100 0] Feb 06 17:26:33 localhost.localdomain NetworkManager[1212]: <info> [1486394793.5595] manager: NetworkManager state is now CONNECTED_LOCAL Feb 06 17:26:33 localhost.localdomain NetworkManager[1212]: <info> [1486394793.5601] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 06 17:26:33 localhost.localdomain NetworkManager[1212]: <info> [1486394793.5602] policy: set 'enp4s0f0' (enp4s0f0) as default for IPv4 routing and DNS Feb 06 17:26:33 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486394793.5603] policy: setting system hostname to 'puma18.scl.lab.tlv.redhat.com' (from DHCPv4) Feb 06 17:26:33 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486394793.5680] device (enp4s0f0): Activation: successful, device activated. Feb 06 17:26:35 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486394795.3736] device (enp5s0f0): link connected Feb 06 17:26:35 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486394795.8574] policy: set 'enp4s0f0' (enp4s0f0) as default for IPv6 routing and DNS Feb 06 17:26:38 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486394798.5589] manager: startup complete cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:True Started HE deployment on host over NFS from Cockpit, although had to manually install rhvm-appliance-4.1.20170126.0-1.el7ev.noarch on host, as it got problems with repos on host. HE deployment successfully finished, but NM was not running, once deployment was finished: # systemctl status NetworkManager -l● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: enabled) Active: inactive (dead) since Mon 2017-02-06 18:23:57 IST; 22min ago Docs: man:NetworkManager(8) Main PID: 1212 (code=exited, status=0/SUCCESS) Feb 06 18:18:20 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486397900.4644] policy: setting system hostname to 'localhost.localdomain' (no default device) Feb 06 18:18:20 puma18.scl.lab.tlv.redhat.com NetworkManager[1212]: <info> [1486397900.4650] policy: setting system hostname to 'localhost.localdomain' (no default device) Feb 06 18:18:20 localhost.localdomain NetworkManager[1212]: <info> [1486397900.5045] device (vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Feb 06 18:18:20 localhost.localdomain NetworkManager[1212]: <info> [1486397900.5055] device (vnet0): state change: unavailable -> disconnected (reason 'none') [20 30 0] Feb 06 18:23:57 localhost.localdomain systemd[1]: Stopping Network Manager... Feb 06 18:23:57 localhost.localdomain NetworkManager[1212]: <info> [1486398237.3363] caught SIGTERM, shutting down normally. Feb 06 18:23:57 localhost.localdomain NetworkManager[1212]: <info> [1486398237.3390] device (enp4s0f0): released from master device ovirtmgmt Feb 06 18:23:57 localhost.localdomain NetworkManager[1212]: <info> [1486398237.3428] device (vnet0): released from master device ovirtmgmt Feb 06 18:23:57 localhost.localdomain NetworkManager[1212]: <info> [1486398237.3438] exiting (success) Feb 06 18:23:57 localhost.localdomain systemd[1]: Stopped Network Manager. # cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:True
1)Reprovisioned to fresh 4.1 RHEVH. 2)This is the defaults on host: [root@alma03 ~]# cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:True 3)Changed to not to turn off the NM and rebooted: [root@alma03 ~]# vi /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [root@alma03 ~]# cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:False [root@alma03 ~]# reboot Connection to alma03.qa.lab.tlv.redhat.com closed by remote host. Connection to alma03.qa.lab.tlv.redhat.com closed. 4)Once rebooted, checked that value stayed False: # cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:False 5)Manually installed rhvm-appliance-4.1.20170126.0-1.el7ev.noarch on host. 6)Started the HE deployment over NFS from Cockpit. 7)Hosted Engine Setup successfully completed! cat /etc/ovirt-host-deploy.conf.d/90-ngn-do-not-keep-networkmanager.conf [environment:init] VDSM/disableNetworkManager=bool:False You have mail in /var/spool/mail/root # systemctl status NetworkManager -l ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2017-02-07 12:14:55 IST; 24min ago Docs: man:NetworkManager(8) Main PID: 988 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─988 /usr/sbin/NetworkManager --no-daemon Feb 07 12:26:06 alma03.qa.lab.tlv.redhat.com NetworkManager[988]: <info> [1486463166.8094] manager: NetworkManager state is now DISCONNECTED Feb 07 12:26:06 alma03.qa.lab.tlv.redhat.com NetworkManager[988]: <info> [1486463166.8100] policy: setting system hostname to 'localhost.localdomain' (no default device) Feb 07 12:26:06 alma03.qa.lab.tlv.redhat.com NetworkManager[988]: <info> [1486463166.8144] policy: setting system hostname to 'localhost.localdomain' (no default device) Feb 07 12:26:08 localhost.localdomain NetworkManager[988]: <info> [1486463168.5258] manager: (ovirtmgmt): new Bridge device (/org/freedesktop/NetworkManager/Devices/6) Feb 07 12:26:11 localhost.localdomain NetworkManager[988]: <info> [1486463171.5281] device (p1p1): link connected Feb 07 12:26:12 localhost.localdomain NetworkManager[988]: <info> [1486463172.0090] device (ovirtmgmt): link connected Feb 07 12:30:59 localhost.localdomain NetworkManager[988]: <info> [1486463459.7623] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/7) Feb 07 12:30:59 localhost.localdomain NetworkManager[988]: <info> [1486463459.8038] device (vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Feb 07 12:30:59 localhost.localdomain NetworkManager[988]: <info> [1486463459.8047] device (vnet0): state change: unavailable -> disconnected (reason 'none') [20 30 0] Feb 07 12:38:29 localhost.localdomain NetworkManager[988]: <info> [1486463909.7126] device (vnet0): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
(In reply to Dan Kenigsberg from comment #16) > What is your `grep disableNetworkManager /etc/ovirt-host-deploy.conf.d/*` > SATHEESARAN ? Hi Dan, I have tested with RHEL 7.3 and RHV 4.1.Beta and I don't see any files under /etc/ovirt-host-deploy.conf.d/* I see that before 'hosted-engine --deploy', NetworkManager was up and running, post HE deployment, NM is disabled and off.
1)Reprovisioned to fresh 4.1 RHEVH with these components: ovirt-vmconsole-host-1.0.4-1.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch qemu-kvm-rhev-2.6.0-28.el7_3.6.x86_64 vdsm-4.19.7-1.el7ev.x86_64 ovirt-hosted-engine-ha-2.1.0.4-1.el7ev.noarch ovirt-imageio-common-1.0.0-0.el7ev.noarch ovirt-host-deploy-1.6.3-1.el7ev.noarch sanlock-3.4.0-1.el7.x86_64 ovirt-node-ng-nodectl-4.1.0-0.20170227.0.el7.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch ovirt-hosted-engine-setup-2.1.0.4-1.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch libvirt-client-2.0.0-10.el7_3.5.x86_64 mom-0.5.9-1.el7ev.noarch ovirt-setup-lib-1.1.0-1.el7ev.noarch Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016 Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.3 2)/etc/ovirt-host-deploy.conf.d/ is empty on my host. 3)Manually installed rhvm-appliance-4.1.20170221.0-1.el7ev.noarch.rpm on host. 4)NetworkManager is running on host. puma19 ~]# systemctl status NetworkManager -l ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2017-03-14 12:06:39 IST; 3h 36min ago Docs: man:NetworkManager(8) Main PID: 1200 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─1200 /usr/sbin/NetworkManager --no-daemon └─1324 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp4s0f0.pid -lf /var/lib/NetworkManager/dhclient-f8edde8d-1c9c-4f45-9877-3930c46e232e-enp4s0f0.lease -cf /var/lib/NetworkManager/dhclient-enp4s0f0.conf enp4s0f0 Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8592] device (enp4s0f0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8596] device (enp4s0f0): state change: secondaries -> activated (reason 'none') [90 100 0] Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8597] manager: NetworkManager state is now CONNECTED_LOCAL Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8604] manager: NetworkManager state is now CONNECTED_GLOBAL Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8605] policy: set 'enp4s0f0' (enp4s0f0) as default for IPv4 routing and DNS Mar 14 12:06:41 localhost.localdomain NetworkManager[1200]: <info> [1489486001.8606] policy: setting system hostname to 'puma19.scl.lab.tlv.redhat.com' (from DHCPv4) Mar 14 12:06:42 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489486002.2056] device (enp4s0f0): Activation: successful, device activated. Mar 14 12:06:43 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489486003.4137] device (enp5s0f0): link connected Mar 14 12:06:46 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489486006.5553] manager: startup complete Mar 14 15:35:40 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489498540.9231] settings: hostname changed from "localhost.localdomain" to "puma19.scl.lab.tlv.redhat.com" Hosted Engine Setup successfully completed! 5)Started the HE deployment over NFS from Cockpit. 6)Hosted Engine Setup successfully completed! 7)NetworkManager service remained running on host after successful deployment of HE. puma19 ~]# systemctl status NetworkManager -l ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2017-03-14 12:06:39 IST; 4h 2min ago Docs: man:NetworkManager(8) Main PID: 1200 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─1200 /usr/sbin/NetworkManager --no-daemon Mar 14 15:49:21 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499361.1678] manager: (ovirtmgmt): new Bridge device (/org/freedesktop/NetworkManager/Devices/6) Mar 14 15:49:21 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499361.2071] device (enp4s0f0): link connected Mar 14 15:49:21 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499361.8049] device (ovirtmgmt): link connected Mar 14 15:53:44 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499624.7414] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/7) Mar 14 15:53:44 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499624.7648] device (vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Mar 14 15:53:44 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489499624.7658] device (vnet0): state change: unavailable -> disconnected (reason 'none') [20 30 0] Mar 14 16:01:42 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489500102.2432] device (vnet0): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3] Mar 14 16:04:09 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489500249.1827] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/8) Mar 14 16:04:09 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489500249.2087] device (vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Mar 14 16:04:09 puma19.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489500249.2097] device (vnet0): state change: unavailable -> disconnected (reason 'none') [20 30 0] Components on engine from original appliance: rhevm-doc-4.1.0-2.el7ev.noarch rhev-guest-tools-iso-4.1-4.el7ev.noarch rhevm-dependencies-4.1.0-1.el7ev.noarch rhevm-branding-rhev-4.1.0-1.el7ev.noarch rhevm-setup-plugins-4.1.0-1.el7ev.noarch rhevm-4.1.1.2-0.1.el7.noarch Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016 Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) Components on engine after updating to latest bits: rhevm-doc-4.1.0-2.el7ev.noarch rhevm-setup-plugins-4.1.1-1.el7ev.noarch rhev-guest-tools-iso-4.1-4.el7ev.noarch rhevm-branding-rhev-4.1.0-1.el7ev.noarch rhevm-4.1.1.4-0.1.el7.noarch rhevm-dependencies-4.1.1-1.el7ev.noarch Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016 Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) 8)Added 2 NFS data storage domains to get hosted-storage auto-imported. 9)Added additional hosted-engine host puma18, while its NM was running prior to addition of the host. puma18 ~]# systemctl status NetworkManager -l ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2017-03-14 12:05:58 IST; 4h 18min ago Docs: man:NetworkManager(8) Main PID: 1200 (NetworkManager) CGroup: /system.slice/NetworkManager.service ├─1200 /usr/sbin/NetworkManager --no-daemon └─1313 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp4s0f0.pid -lf /var/lib/NetworkManager/dhclient-ac41ed69-a1f4-444a-9a03-c3a152840685-enp4s0f0.lease -cf /var/lib/NetworkManager/dhclient-enp4s0f0.conf enp4s0f0 Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3905] device (enp4s0f0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3955] device (enp4s0f0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3958] device (enp4s0f0): state change: secondaries -> activated (reason 'none') [90 100 0] Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3960] manager: NetworkManager state is now CONNECTED_LOCAL Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3966] manager: NetworkManager state is now CONNECTED_GLOBAL Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3967] policy: set 'enp4s0f0' (enp4s0f0) as default for IPv4 routing and DNS Mar 14 12:06:00 localhost.localdomain NetworkManager[1200]: <info> [1489485960.3968] policy: setting system hostname to 'puma18.scl.lab.tlv.redhat.com' (from DHCPv4) Mar 14 12:06:00 puma18.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489485960.6389] device (enp4s0f0): Activation: successful, device activated. Mar 14 12:06:02 puma18.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489485962.0370] device (enp5s0f0): link connected Mar 14 12:06:04 puma18.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489485964.5444] manager: startup complete 10)NM was still running after addition of additional hosted-engine host. puma18 ~]# systemctl status NetworkManager -l ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2017-03-14 12:05:58 IST; 4h 20min ago Docs: man:NetworkManager(8) Main PID: 1200 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─1200 /usr/sbin/NetworkManager --no-daemon Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.3764] device (enp4s0f0): state change: activated -> deactivating (reason 'connection-removed') [100 110 38] Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.3765] manager: NetworkManager state is now DISCONNECTING Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.4163] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp4s0f0 (0f70a0db-f30a-93ed-f377-3f3750bacad9,"System enp4s0f0") Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.4164] ifcfg-rh: Ignoring connection /etc/sysconfig/network-scripts/ifcfg-enp4s0f0 (0f70a0db-f30a-93ed-f377-3f3750bacad9,"System enp4s0f0") due to NM_CONTROLLED=no. Unmanaged: interface-name:enp4s0f0. Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.4164] device (enp4s0f0): state change: deactivating -> unmanaged (reason 'unmanaged') [110 10 3] Mar 14 16:25:17 localhost.localdomain NetworkManager[1200]: <info> [1489501517.9362] manager: NetworkManager state is now DISCONNECTED Mar 14 16:25:19 localhost.localdomain NetworkManager[1200]: <info> [1489501519.6891] manager: (ovirtmgmt): new Bridge device (/org/freedesktop/NetworkManager/Devices/6) Mar 14 16:25:19 localhost.localdomain NetworkManager[1200]: <info> [1489501519.7278] device (enp4s0f0): link connected Mar 14 16:25:20 localhost.localdomain NetworkManager[1200]: <info> [1489501520.2536] device (ovirtmgmt): link connected Mar 14 16:25:23 puma18.scl.lab.tlv.redhat.com NetworkManager[1200]: <info> [1489501523.0888] policy: setting system hostname to 'localhost.localdomain' (no default device) You have new mail in /var/spool/mail/root Moving to verified.
/etc/ovirt-host-deploy.conf.d/ is empty on both hosts.