Quick test?
service firewalld stop
then ALL ports are open.
NOT Recommended! be sure to turn it back on when your tests are complete.
Cheers,
Robert O'Kane
On 05/31/2019 10:37 AM, Simone Tiraboschi wrote:
On Thu, May 30, 2019 at 2:56 PM Zachary Winter <zachary.winter(a)witsconsult.com
<mailto:zachary.winter@witsconsult.com>> wrote:
I am unable to connect via SPICE (Windows VirtViewer) to VM's running on my
compute node. It appears the node did not auto-configure the firewall because
the .vv files appear to point to the correct IP address and common ports. Is there a
way to re-run/re-execute the firewall auto-configuration now that the
node has already been installed?
From the Web UI, you can set the host to maintenance mode and then select reinstall: it
will also configure the firewall.
But are you really sure that the issue is on host side?
If not, does anyone happen to have firewall-cmd commands handy that I can run to
resolve this quickly? Which ports need to be opened?
The specs on the node are as follows:
OS Version:
RHEL - 7 - 6.1810.2.el7.centos
OS Description:
oVirt Node 4.3.3.1
Kernel Version:
3.10.0 - 957.10.1.el7.x86_64
KVM Version:
2.12.0 - 18.el7_6.3.1
LIBVIRT Version:
libvirt-4.5.0-10.el7_6.6
VDSM Version:
vdsm-4.30.13-1.el7
SPICE Version:
0.14.0 - 6.el7_6.1
GlusterFS Version:
glusterfs-5.5-1.el7
CEPH Version:
librbd1-10.2.5-4.el7
Open vSwitch Version:
openvswitch-2.10.1-3.el7
Kernel Features:
PTI: 1, IBRS: 0, RETP: 1, SSBD: 3
VNC Encryption:
Enabled
--
Robert O'Kane
Systems Administrator
Kunsthochschule für Medien Köln
Peter-Welter-Platz 2
50676 Köln
fon: +49(221)20189-223
fax: +49(221)20189-49223