On Tue, Jan 15, 2013 at 3:10 PM, Gianluca Cecchi wrote:

BTW: I have a similar problem with an all-in-one f18 + ovirt nightly setup running as a VM

after engine-upgrade to 3.2.0-1.20130115.git2970f58

I found this interesting thing on my All-in-one server.

engine-setup ran on 18/12 12:34. Its log

/var/log/ovirt-engine/engine-setup_2012_12_18_12_12_34.log

contains the lines I reported above.

But if now I go in /etc/sysconfig

# ll iptables*

-rw-------. 1 root root 770 Dec 18 13:02 iptables

-rw-------. 1 root root 1449 Dec 18 13:02 iptables.20121218130224

-rw-------. 1 root root 1740 Nov 8 13:11 iptables-config

So it seems it was overridden by something else.

iptables.20121218130224 contains the engine directives I find in engine-setup log file

Could it be that the host deploy part of AIO incorrectly replaced the engine iptables setup instead of merging with it?

How could I merge them all?

See

current iptables (not ok for engine):

iptables at engine-setup time (ok):

Gianluca