On 11/05/2013 09:44 AM, Sandro Bonazzola wrote:
Il 05/11/2013 15:15, Bob Doolittle ha scritto:
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
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
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 t
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
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?
-Bob
On 11/04/2013 02
By wrapping the mount command on the node and recording the mount args,
I was able to reproduce the issue manually.
Although I can remote mount the iso dir using default options, when I
specify -o nfsvers=3 the mount times out, which is the problem.
I can do a loopback mount on the engine usi
On 2013-11-04 18:54, Bob Doolittle wrote:
If there's any diagnostic info anybody would like me to
acquire first, please speak up asap.
It's always a good idea to keep a copy of /var/log/vdsm/vdsm.log
from oVirt node and /var/log/ovirt-engine/engine.log from
oVirt engine.
Regards
- Frank
I appreciate the tip, although I'm concerned about masking over issues
we'd all prefer to be uncovered and fixed.
If there's any diagnostic info anybody would like me to acquire first,
please speak up asap.
-Bob
On 11/04/2013 12:12 PM, Frank Wall wrote:
On 2013-11-04 18:06, Bob Doolittle wr
On 2013-11-04 18:06, Bob Doolittle wrote:
However, my ISO_DOMAIN remains unattached. If I select it, select its
Data Center tab, and click on Attach, it times out.
Try putting the oVirt node in maintenance mode, wait,
and activate it again. Every once in a while this helped
me solve strange pro
I have a fresh, default oVirt 3.3 setup, with F19 on the engine and the
node (after applying the shmmax workaround discussed in separate
thread). I followed the Quick Start Guide.
I've added the node, and a storage domain on the node, so the Datacenter
is now initialized.
However, my ISO_DOM
10 matches
Mail list logo
