Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1481924

Summary: [RHVH 4.1] port 16514 is not in rules after upgrade host to RHVH 4.1 (el7.4)
Product: Red Hat Enterprise Virtualization Manager Reporter: Ulhas Surse <usurse>
Component: ovirt-node-ngAssignee: Ryan Barry <rbarry>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.4CC: dfediuck, dmardones
Target Milestone: ---Flags: lsvaty: testing_plan_complete-
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-16 12:42:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ulhas Surse 2017-08-16 04:40:46 UTC 
Description of problem:
After upgrading the host to 4.1 (el7.4), the port 16514 is disabled in the firewall configuration due to which migration of VM fails to this new upgraded host.

Version-Release number of selected component (if applicable):
"Red Hat Virtualization Host 4.1 (el7.4)"

How reproducible:
Always 

Steps to Reproduce:
1. Upgrade host to "Red Hat Virtualization Host 4.1 (el7.4)"
2. Activate and try to migrate VMs to this host. 
3. Migration fails with error:

libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://<hostname>/system: unable to connect to server at 'hostname:16514': No route to host


Actual results:
port is blocked and migration fails 

Expected results:
Port should be allowed after upgrade and VM should migrate


Additional info:
Following allowed to migrate VM:

  # firewall-cmd --zone=public --add-port=16514/tcp --permanent
  # firewall-cmd --reload