Bug 702645 - VDSM/RHEVM installation scripts don't open necessary ports on RHEL 5 hypervisor
Summary: VDSM/RHEVM installation scripts don't open necessary ports on RHEL 5 hypervisor
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: vdsm22
Version: 5.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-06 13:09 UTC by David Jaša
Modified: 2016-04-18 06:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-20 09:00:20 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2011-05-06 13:09:05 UTC 
Description of problem:
When one adds a RHEL 5 host (clean install with, vdsm22 and vdsm22-cli packages) to RHEVM 2.2 setup via Admin Portal --> Hosts --> New, RHEVM cannot contact it, because ports in question are blocked by firewall

Version-Release number of selected component (if applicable):
RHEV-M 4.5.4.52920
vdsm22-cli-4.5-63.25.el5_6
vdsm22-4.5-63.25.el5_6

How reproducible:
always

Steps to Reproduce:
1. do a clean install of RHEL 5, install vdsm22{,-cli} packages to it
2. add this host to RHEV setup
3. wait for host reboot
  
Actual results:
after reboot, host is in Non-Operational state, after disabling iptables, host changes state to Up

Expected results:
firewall setup is modified by installation scripts so that ports used for RHEV-M <--> VDSM communication are accessible from RHEV-M machine

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