I upgraded a CentOS 7 oVirt 4.1.7 (initially installed as 3.5 if it matters) test oVirt cluster to 4.2.0, and ran into one minor issue. The update installed firewalld on the host, which was set to start on boot. This replaced the iptables rules with a blank firewalld setup that only allowed SSH, which kept the host from working. Stopping and disabling firewalld, then reloading iptables, got the host back working. In a quick search, I didn't see anything noting that firewalld was now required, and it didn't seem to be configured correctly if oVirt was trying to use it. -- Chris Adams <cma(a)cmadams.net&gt; _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1511013 - can you confirm? Y. On Sat, Dec 23, 2017 at 1:56 AM, Chris Adams <cma(a)cmadams.net&gt; wrote: > > I upgraded a CentOS 7 oVirt 4.1.7 (initially installed as 3.5 if it > matters) test oVirt cluster to 4.2.0, and ran into one minor issue. The > update installed firewalld on the host, which was set to start on boot. > This replaced the iptables rules with a blank firewalld setup that only > allowed SSH, which kept the host from working. > > Stopping and disabling firewalld, then reloading iptables, got the host > back working. > > In a quick search, I didn't see anything noting that firewalld was now > required, and it didn't seem to be configured correctly if oVirt was > trying to use it. > > -- > Chris Adams <cma(a)cmadams.net&gt; > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Once upon a time, Misak Khachatryan <kmisak(a)gmail.com&gt; said: > It seems me too in the same situation, my cluster shows firewall type > as iptables, and my firewalld status is on hosts: Do you know if you had firewalld installed before upgrading? You should be able to tell by checking your /var/log/yum.log. I suspect that the issue is that oVirt pulls in firewalld, and the firewalld RPM sets itself to run by default, plus it happens to be started after iptables (and so blows away iptables rules). See if this fixes it for you: # systemctl stop firewalld.service # systemctl disable firewalld.service # systemctl restart iptables.service -- Chris Adams <cma(a)cmadams.net&gt; _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users