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?