Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1152202 - No route to rhel7 after successful host deploy
Summary: No route to rhel7 after successful host deploy
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.5.0
Assignee: Saggi Mizrahi
QA Contact: Pavel Stehlik
Whiteboard: infra
Depends On:
Blocks: rhev35betablocker rhev35rcblocker rhev35gablocker
TreeView+ depends on / blocked
Reported: 2014-10-13 14:55 UTC by Ohad Basan
Modified: 2016-02-10 19:14 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-10-21 12:16:41 UTC
oVirt Team: Infra
Target Upstream Version:

Attachments (Terms of Use)

Description Ohad Basan 2014-10-13 14:55:15 UTC
Description of problem:
I have a setup of rhevm 3.5.
added a rhel7 host. host deploy succeeded and vdsm is up
selinux is set on permissive state. yet the engine can not seem to establish connection with the host despite the fact that the host is fully reachable.
I will attach all the relevant logs

2014-10-13 17:37:02,000 WARN  [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (SSL Stomp Reactor) Retry failed: No route to host
        at Method) [rt.jar:1.7.0_65]
        at [rt.jar:1.7.0_65]
        at org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient$ [vdsm-jsonrpc-java-client.jar:]
        at org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient$ [vdsm-jsonrpc-java-client.jar:]
        at [vdsm-jsonrpc-java-client.jar:]
        at [rt.jar:1.7.0_65]
        at org.ovirt.vdsm.jsonrpc.client.utils.ReactorScheduler.performPendingOperations( [vdsm-jsonrpc-java-client.jar:]
        at [vdsm-jsonrpc-java-client.jar:]

Comment 3 Eyal Edri 2014-10-21 08:57:53 UTC
fails automation on el7 - adding to beta blocker.

Comment 4 Saggi Mizrahi 2014-10-21 12:16:41 UTC
We don't do routing. We just use the IP. If there is no route to host it's not because of anything related to jsonrpc.

Comment 5 Piotr Kliczewski 2014-10-21 12:45:50 UTC
Saggi is right that it is not related to jsonrpc. Together with Ohad we investigated the issue and after capturing the traffic we can see that the host response to any network frame sent to vdsm port is ICMP type 3 code 10 which is 
according to the iptables rule:

REJECT     all  --              reject-with icmp-host-prohibited

My assumption is that we do not configure iptables properly during host deploy.

Comment 6 Piotr Kliczewski 2014-10-21 13:32:20 UTC
We have confirmation that host deploy did not configure iptables because it was told not to do it.

Note You need to log in before you can comment on or make changes to this bug.