Bug 1481924 - [RHVH 4.1] port 16514 is not in rules after upgrade host to RHVH 4.1 (el7.4)
Summary: [RHVH 4.1] port 16514 is not in rules after upgrade host to RHVH 4.1 (el7.4)
Keywords:
Status: CLOSED DUPLICATE of bug 1473307
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node-ng
Version: 4.1.4
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-16 04:40 UTC by Ulhas Surse
Modified: 2020-12-14 11:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-16 12:42:21 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3153191 0 None None None 2017-08-16 05:03:43 UTC

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
Note You need to log in before you can comment on or make changes to this bug.