[Users] ISO_DOMAIN won't attach

[Sandro Bonazzola]

Il 05/11/2013 15:15, Bob Doolittle ha scritto:
> 
> On 11/05/2013 02:35 AM, Sandro Bonazzola wrote:
>> Il 04/11/2013 20:58, Bob Doolittle ha scritto:
>>> Aha - finally nailed it.
>>>
>>> Although iptables was disabled on engine, firewalld was not. Once I disabled firewalld, nfsv3 mounts worked fine, and ISO_DOMAIN was able to attach.
>>>
>>> Is the admin expected to take care of this, or is engine-setup supposed to disable firewalld?
>> While running engine-setup it asks you if you want to configure firewalld if present.
>> If you say no it asks you if you want to configure iptables if present.
>> If you say no you'll need to take care of configuring it manually.
>> If iptables has been choosen to be configured, firewalld is disabled if present.
> 
> I simply took the defaults to all questions, which presumably should lead to a working configuration. Does it not?

Well, yes it should.
The point here is that having the host running the engine also as hypervisor should be done during setup using the all-in-one plugin.
Adding the host to the engine later is not a supported path yet, due to Bug 995362.

>> Did you add the host from web interface instead of using all in one plugin?
>> ovirt engine is not able to handle firewalld, see https://bugzilla.redhat.com/show_bug.cgi?id=995362
>> Bug 995362 - [RFE] Support firewalld.
> 
> Yes - web interface.

Ok, that explain how it happened.
As workaround as you already discovered, you can just disable firewalld.
I'm sorry for the inconvenient


> 
> -Bob
> 


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com