On Sun, Jun 23, 2019 at 3:30 AM <zachary.winter(a)witsconsult.com> wrote:
Regarding "Perhaps try to find out what exactly failed?", that is why I posted
this thread. I am new to oVirt and trying to master it, but I do not know where to look.
I have not found any documentation yet that tells me which logs to look at when, so please
bear with me as I try to figure this out. Thank you however for your help.
For general information, see:
https://www.ovirt.org/documentation/admin-guide/chap-Log_Files.html
I ran the yum command you listed and got the debug output. I do in fact have a storage
domain on the Node, and I am almost certain that is why it is failing. I suspect that
removing the storage domain will allow the update to work, but I am confused though
because I have successfully updated this node with a storage domain on it several times
now, so is this going to be a permanent requirement?
This check was added for the following bug, in 4.2.2 (so rather new -
it makes sense that you did mange to use one in the past):
https://bugzilla.redhat.com/show_bug.cgi?id=1549630
So it seems to prevent local storage domains on the root filesystem.
So you can/should probably try moving your storage domain to a
separate filesystem.
is there any advanced documentation (i.e., this log captures this, here is what to look
for when this happens) available?
There is lots of material on
ovirt.org, including many pages and many
many posts to the mailing lists.
I am not aware of any book-style "advanced documentation".
For this particular example, to find above bug, I did this:
Found the place in the source code that includes this scriptlet:
https://github.com/oVirt/ovirt-node-ng/blob/master/packaging/ovirt-node-n...
Search the git log for this file. You can do this in github ("History"
button), but I find it much more comfortable to use 'git log -u' and
search inside. This finds:
https://github.com/oVirt/ovirt-node-ng/commit/a46150de468fac72224762e67e4...
And this links to the bug.
Best regards,
--
Didi