Description of problem:
Currently the sosreport tool, used by log collector, does not collect any information related to hosted-engine. These files include, but may not be limited to:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run log collector in hosted engine environment
2. Extract host sosreports in log collector
No hosted-engine related files are found
All hosted-engine configuration and log files should be included
It may also be useful to grab the output from a few 'hosted-engine' commands, similar to the way in which vdsClient output is collected:
# hosted-engine --vm-status
The RHEV-M VM in these situations is completely unaware that it's a VM, no different than running a baremetal RHEV-M. Though there isn't an obvious and easy way to do it inside the guest, would it be useful (or even possible) to somehow indicate that this is a self-hosted environment? Maybe include a file under the log-collector-data directory (like time_diff.txt) that includes a list of all HA hosts? A lot of our customers simply open cases with brief descriptions and a LC, but no information on the environment. Other times, they simply fail to mention self hosted altogether. This small addition would a great convenience.
Upstream sos plugin request for collecting needed data is here: https://github.com/sosreport/sos/issues/364
We can deliver a sos plugin for hosted-engine within ovirt-hosted-engine-ha or ovirt-hosted-engine-setup for distributions still using sos 2.
sos plugin patches pushed for review:
updated after first review:
Can we get this backported to 3.5? This feature is extremely helpful for anyone trying to troubleshoot issues with hosted-engine, and it would save a decent amount of time for end users.
(In reply to wdaniel from comment #4)
> Can we get this backported to 3.5? This feature is extremely helpful for
> anyone trying to troubleshoot issues with hosted-engine, and it would save a
> decent amount of time for end users.
Proposed for 3.5.1 ZStream
*** Bug 1169098 has been marked as a duplicate of this bug. ***
We have a request upstream to make sos tolerant of non-existent plugins on the command-line (so far just for disabled plugins):
Not sure this would apply to the lC situation (and it's not going to be in the next RHEL releases) but would appreciate comments on the upstream discussion if this seems like something that could be of interest (I know maintaining the lC command lines in the face of changing plugin sets has caused challenges in the past).
Thanks Bryn, commented.
Red Hat Enterprise Linux Server release 7.1 (Maipo)
Red Hat Enterprise Linux Server release 6.7 Beta (Santiago)
hosted-engine data is now being collected by log-collector.
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.