Description of problem: I was doing 3.4 -> 3.5 -> 3.6 -> 4.0 SHE migration (on NFS) and hosted-engine --upgrade-appliance fails (running on 3.6 EL7 host, engine 3.6 EL6): ~~~ ... [ ERROR ] Failed to execute stage 'Environment customization': The following existing interfaces are not suitable for vdsm: vnet0,eth0. You might want to pull out an interface out of a bridge to be able to use it [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine upgrade failed: this system is not reliable. If necessary you can use --rollback-upgrade option to recover the engine VM disk from a backup Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160806004255-adphm8.log You have new mail in /var/spool/mail/root [root@10-34-60-151 ~]# brctl show bridge name bridge id STP enabled interfaces ;vdsmdummy; 8000.000000000000 no rhevm 8000.001a4ad04003 no eth0 vnet0 [root@10-34-60-151 ~]# ip a s 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master rhevm state UP qlen 1000 link/ether 00:1a:4a:d0:40:03 brd ff:ff:ff:ff:ff:ff 3: rhevm: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 00:1a:4a:d0:40:03 brd ff:ff:ff:ff:ff:ff inet 10.34.60.151/22 brd 10.34.63.255 scope global dynamic rhevm valid_lft 17928sec preferred_lft 17928sec 4: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN link/ether 42:cb:d4:a7:51:f0 brd ff:ff:ff:ff:ff:ff 6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master rhevm state UNKNOWN qlen 500 link/ether fe:1a:4a:d0:40:05 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc1a:4aff:fed0:4005/64 scope link valid_lft forever preferred_lft forever ~~~ I was doing 3.6->4.0 SHE migration and it was working fine. It's maybe related to all the flow described above. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.0.1.3-1.el7ev.noarch otopi-1.5.1-3.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. have 3.6 SHE hosts EL7 with 3.6 engine EL6 (result of 3.4->3.5->3.6 migration flow) 2. install 4.0 rpms on both EL7 hosts 3. hosted-engine --upgrade-appliance Actual results: failure [ ERROR ] Failed to execute stage 'Environment customization': The following existing interfaces are not suitable for vdsm: vnet0,eth0. You might want to pull out an interface out of a bridge to be able to use it Expected results: should work Additional info:
Created attachment 1188086 [details] ovirt-hosted-engine-setup-20160806003141-aj66tm.log
The root cause is that the code is looking just for a management bridge called ovirtmgmt while on Jiri's host it's named rhevm since it was initially created by 3.4 code.
A simple workaround is to execute: hosted-engine --deploy --otopi-environment='OVEHOSTED_NETWORK/bridgeName=str:rhevm' or using an answer file to force the management bridge name.
(In reply to Simone Tiraboschi from comment #3) > A simple workaround is to execute: > hosted-engine --deploy > --otopi-environment='OVEHOSTED_NETWORK/bridgeName=str:rhevm' > or using an answer file to force the management bridge name. The workaround works fine, thx.
ok, ovirt-hosted-engine-setup-2.0.1.4-1.el7ev.noarch no workaround needed anymore.