I've been trying to deploy ovirt on a multi-node cluster for the past
couple releases and always hit the same sticking point.
Everything seems to come up fine, including the other nodes, but when
I try to connect to an iSCSI server, the server gets stuck in
pending_setup.
In the most recent case (with Fedora 10 and ovirt 0.96), I followed
the iSCSI directions for setting up an iSCSI server on the primary
host which is running the ovirt appliance
(192.168.50.1 from the ovirt view of the world). I verified that I
could discover/login to the iSCSI disk from the ovirt appliance.
Its probably something stupid I'm doing, but this is probably worth
adding to the troubleshooting section of the wiki at the very least.
-eric
On Fri, 2009-01-23 at 10:29 -0600, Eric Van Hensbergen wrote:> I've been trying to deploy ovirt on a multi-node cluster for the past > couple releases and always hit the same sticking point. > Everything seems to come up fine, including the other nodes, but when > I try to connect to an iSCSI server, the server gets stuck in > pending_setup.You need to have a node in the same hardware pool turned on (i.e., listed as available and enabled) - if that's the case, and the pool still stays in pending_setup, check the logs, both on the node and on the server (in /var/log/ovirt-server/*) David
On Fri, Jan 23, 2009 at 11:06 AM, David Lutterkort <lutter at redhat.com> wrote:> On Fri, 2009-01-23 at 10:29 -0600, Eric Van Hensbergen wrote: >> I've been trying to deploy ovirt on a multi-node cluster for the past >> couple releases and always hit the same sticking point. >> Everything seems to come up fine, including the other nodes, but when >> I try to connect to an iSCSI server, the server gets stuck in >> pending_setup. > > You need to have a node in the same hardware pool turned on (i.e., > listed as available and enabled) - if that's the case, and the pool > still stays in pending_setup, check the logs, both on the node and on > the server (in /var/log/ovirt-server/*) >Okay - I now notice that the hosts that I booted are showing up as unavailable (enabled). So, what's the magic here? Is it the requirement that I manually install qemu on the appliance and nodes that Jeremy mentioned? qemu-kvm seems to be present on the nodes, but not on the appliance. -eric