[Users] Host x is installed with VDSM version (<UNKNOWN>)
Hello ovirt users. New to ovirt and having troubles. Trying to setup a dedicated ovirt engine host and use a separate, exiting CentOS 6.5 host to run some guests as a node. When I tried to add the host, it recognizes it but throws errors of: Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command. I'm looking to run this host with it's local storage. I've tried to add a local storage path on the host via ovirt of "/data/images" but it seems to have no effect. Any help appreciated. Thanks, Matt
Hi, well how did you install vdsm on the centos 6.5 node in the first place? from the ovirt.org stable repo I hope? pay attention that there is currently a bug, you need to install python-cpopen beforehand from epel repo: yum -y install python-cpopen HTH Am 31.01.2014 05:43, schrieb Matt Warren:
Hello ovirt users. New to ovirt and having troubles.
Trying to setup a dedicated ovirt engine host and use a separate, exiting CentOS 6.5 host to run some guests as a node.
When I tried to add the host, it recognizes it but throws errors of:
Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10].
In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command.
I'm looking to run this host with it's local storage. I've tried to add a local storage path on the host via ovirt of "/data/images" but it seems to have no effect.
Any help appreciated.
Thanks, Matt
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Saw the python-cpopen issue from yum and did a manual install.
python-cpopen.x86_64 1.3-1.el6 @epel
Should it be the vdsm-python-cpopen.x86_64 4.13.3-2.el6 from the ovirt-3.3.2 repo? Vdsm was installed from the ovirt 3.3.2 repo
Installed Packages vdsm.x86_64 4.13.3-2.el6 @ovirt-3.3.2
On 1/31/14, 3:56 AM, "Sven Kieske" <S.Kieske@mittwald.de> wrote:
well how did you install vdsm on the centos 6.5 node in the first place?
from the ovirt.org stable repo I hope?
pay attention that there is currently a bug, you need to install python-cpopen beforehand from epel repo:
yum -y install python-cpopen
HTH
Am 31.01.2014 05:43, schrieb Matt Warren:
Hello ovirt users. New to ovirt and having troubles. Trying to setup a dedicated ovirt engine host and use a separate, exiting CentOS 6.5 host to run some guests as a node. When I tried to add the host, it recognizes it but throws errors of: Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command. I'm looking to run this host with it's local storage. I've tried to add a local storage path on the host via ovirt of "/data/images" but it seems to have no effect. Any help appreciated. Thanks, Matt
Any troubleshooting ideas for vdsm reporting UNKNONW version when it's clearly 4.13 installed? On 1/31/14, 8:01 AM, "Matt Warren" <mwarren@hnw.com> wrote:
Saw the python-cpopen issue from yum and did a manual install.
python-cpopen.x86_64 1.3-1.el6 @epel
Should it be the vdsm-python-cpopen.x86_64 4.13.3-2.el6 from the ovirt-3.3.2 repo?
Vdsm was installed from the ovirt 3.3.2 repo
Installed Packages vdsm.x86_64 4.13.3-2.el6 @ovirt-3.3.2
On 1/31/14, 3:56 AM, "Sven Kieske" <S.Kieske@mittwald.de> wrote:
well how did you install vdsm on the centos 6.5 node in the first place?
from the ovirt.org stable repo I hope?
pay attention that there is currently a bug, you need to install python-cpopen beforehand from epel repo:
yum -y install python-cpopen
HTH
Am 31.01.2014 05:43, schrieb Matt Warren:
Hello ovirt users. New to ovirt and having troubles. Trying to setup a dedicated ovirt engine host and use a separate, exiting CentOS 6.5 host to run some guests as a node. When I tried to add the host, it recognizes it but throws errors of: Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command. I'm looking to run this host with it's local storage. I've tried to add a local storage path on the host via ovirt of "/data/images" but it seems to have no effect. Any help appreciated. Thanks, Matt
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Fri, Jan 31, 2014 at 01:26:20PM -0500, Matt Warren wrote:
Any troubleshooting ideas for vdsm reporting UNKNONW version when it's clearly 4.13 installed?
Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command.
Engine cannot tell which Vdsm is install, since there's a serious problem there - so serious that Vdsm cannot report its own version. Could you restart Vdsm and follow vdsm.log and supervdsm.log for hints on why does the storage subsystem fail to start?
On 2/1/14, 5:09 PM, "Dan Kenigsberg" <danken@redhat.com> wrote:
On Fri, Jan 31, 2014 at 01:26:20PM -0500, Matt Warren wrote:
Any troubleshooting ideas for vdsm reporting UNKNONW version when it's clearly 4.13 installed?
Host x is installed with VDSM version (<UNKNOWN>) and cannot join cluster Default which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. In reading some google searches, suggestion was to first run "vdsClient -s 0 getVdsCaps". This returns "Failed to initialize storage" for any vdsClient command.
Engine cannot tell which Vdsm is install, since there's a serious problem there - so serious that Vdsm cannot report its own version.
Could you restart Vdsm and follow vdsm.log and supervdsm.log for hints on why does the storage subsystem fail to start?
Dan, thanks for the reply. I ended up down this chain of reasoning on Friday. Discovered the vdsm.log and saw that it was having sudo problems. Those were likely cause by my puppet agent stepping on whatever setup vdsm had done to sudoers on install. I repaired what I could from the sudoers changes in the ovirt git repo (though not exact as that file looks to have a number of paths evaluated at runtime). VDSM was able to run cleanly and then ovirt could detect the version and carry on.
participants (3)
-
Dan Kenigsberg -
Matt Warren -
Sven Kieske