Bug 1221290
Summary: | [self-hosted] Can't add 2nd host into self-hosted env: The VDSM host was found in a failed state... Unable to add slot-5b to the manager | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ | ||||
Component: | ovirt-hosted-engine-setup | Assignee: | Simone Tiraboschi <stirabos> | ||||
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 3.5.1 | CC: | aburden, bazulay, ecohen, gklein, jbelka, lpeer, lsurette, oourfali, pstehlik, pzhukov, sbonazzo, stirabos, yeylon, ylavi | ||||
Target Milestone: | --- | Keywords: | Regression, TestBlocker, ZStream | ||||
Target Release: | 3.5.3 | Flags: | ylavi:
Triaged+
|
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | integration | ||||||
Fixed In Version: | ovirt-hosted-engine-setup-1.2.4-2.el6ev | Doc Type: | Bug Fix | ||||
Doc Text: |
Previously, in self-hosted engine environments, the HOST_ID for additional hosts was stored as a string, which prevented the Manager from properly identifying and contacting VDSM on the host and resulted in failure to add host. Now, the HOST_ID is stored as an integer and the host is added to the self-hosted engine as expected.
|
Story Points: | --- | ||||
Clone Of: | 1216172 | Environment: | |||||
Last Closed: | 2015-06-15 13:17:27 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1216172 | ||||||
Bug Blocks: | 1218280 | ||||||
Attachments: |
|
Comment 3
Jiri Belka
2015-05-18 11:08:10 UTC
Jiri, the above ioprocess stack trace is a known issue in ioprocess, see bug #1189200 That's not the cause of "[ ERROR ] Unable to add hosted_engine_2 to the manager". can you attach full sos report for this new run? Created attachment 1026733 [details]
sosreport-dell-r210ii-13.rhev.lab.eng.brq.redhat.com-20150518163140.tar.xz
Ha, I put problematic host into maintenance and used 'Reinstall' and now I see it Up. Please inspect the logs why "second" try did work, thanks. jiri, we see similar issues (fail on first run, success on the second run) when environmental / dhcp related issues come in. Can you check the env / dhcp? Ok, found in ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20150518125810-vvuk3a.log : 2015-05-18 12:59:24 DEBUG otopi.context context.dumpEnvironment:500 ENV NETWORK/iptablesEnable=bool:'False' So it's just blocked by this one: https://bugzilla.redhat.com/show_bug.cgi?id=1221148 In a few world: the second host doesn't got the firewall properly configured and so, depending from the previous firewall configuration, the engine could be able or not to contact VDSM and so the issue adding the second host. Just as a workaround, you can try to deploy the second host keeping both iptables and firewalld disabled. ok, ovirt-hosted-engine-setup-1.2.4-2.el7ev.noarch basic tests - maintenance for hosts, moving self-hosted engine, running vm on 2nd host: ... Hosted Engine successfully set up [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20150529112728.conf' [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [root@dell-r210ii-13 ~]# iptables -nL INPUT Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:54321 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:111 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:111 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:161 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:16514 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 5900:6923 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 49152:49216 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Cheers mate Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1108.html |