Description of problem:
rhevm configs are not collected
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. log collector collect
3. check the engine/etc direcotry
no rhevm directory
rhevm or ovirt-engine directory
Seems to affect 3.5 as well.
(In reply to Petr Beňas from comment #1)
> Seems to affect 3.5 as well.
It's a bug in sos. I can workaround it duplicating the directory content instead of creating the symlink in the archive. Is this acceptable for the automation testing? Or does it require the symlink?
From a GSS point of view, is this relevant? Do we really need the symlink?
While testing this, I've found some issues. I'll open a bug for them.
From our point of view it's necessary to have the folder content in sos. It's not really matter to us how the implementation would look.
(In reply to Tomas Dosek from comment #3)
> From our point of view it's necessary to have the folder content in sos.
> It's not really matter to us how the implementation would look.
Just to clarify Sandro's question: For some versions now, /etc/rhevm is a symlink to /etc/ovirt-engine. We already collect the latter. The question was whether it's important at all to also collect /etc/rhevm (which, as Sandro said, with the current implementation will look like a copy of /etc/ovirt-engine rather than a symlink to it).
Sandro - on a second thought, I think we do have to collect also /etc/rhevm, just for weird cases where it does not exist (although iirc this shouldn't break anything) or where it's actually not a symlink but a partial/modified copy of /etc/ovirt-engine.
(In reply to Yedidyah Bar David from comment #5)
> Sandro - on a second thought, I think we do have to collect also /etc/rhevm,
> just for weird cases where it does not exist (although iirc this shouldn't
> break anything) or where it's actually not a symlink but a partial/modified
> copy of /etc/ovirt-engine.
Ok, make sense.
Why is this bug on POST without setting a proper group in the whiteboard?
(In reply to Oved Ourfali from comment #7)
> Why is this bug on POST without setting a proper group in the whiteboard?
Just forgot to set the field, sorry.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.