See output of engine-setup below. I have to explicitly typeout iptables for it to continue. Firewall manager to configure (iptables): [ ERROR ] Invalid value Firewall manager to configure (iptables): [ ERROR ] Invalid value Firewall manager to configure (iptables): iptables [ INFO ] iptables will be configured as firewall manager. [root ~]$ rpm -q rhevm-setup rhevm-setup-3.3.2-0.50.el6ev.noarch
(In reply to Matthew Davis from comment #0) > See output of engine-setup below. I have to explicitly typeout iptables for > it to continue. > > Firewall manager to configure (iptables): > [ ERROR ] Invalid value > Firewall manager to configure (iptables): > [ ERROR ] Invalid value > Firewall manager to configure (iptables): iptables > [ INFO ] iptables will be configured as firewall manager. > > > [root ~]$ rpm -q rhevm-setup > rhevm-setup-3.3.2-0.50.el6ev.noarch This is the intended behavior. See [1] for a detailed description. In particular, if no firewall managers are active, user is forced to make a significant decision - choosing to activate a previously inactive service - and therefore there is no default, even if there is only one candidate. An example where this is important: If a user has some other active firewall manager (such as ferm, firehol, fwbuilder etc) which is not supported by setup, we do not want to override the current settings (probably breaking stuff) if a user merely presses 'Enter' all the time accepting defaults. So, to sum up: If you have just iptables installed, do not care about all the complications of setup, just want 'Enter' to accept defaults without having to type anything, just make sure you enable iptables prior to running setup. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1024707#c9