Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
imgbased.log log contains upgrade/installation logs of RHV-H . This log file is necessary for troubleshooting upgrade/installation issues of RHV-H. Collect this using vdsm plugin.
Version-Release number of selected component (if applicable):
vdsm-4.20.27.2
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Collect imgbased.log in sosreport.
Additional info:
I agree with Sandro, vdsm should not collect log it does not generate, and new
functionality should be only in the sos project.
It would be nice if you also file a bug for:
- separating sanlock.log to its own sos plugin
- adding plugin for ovirt-imageio
I think both bugs should be filed for the sos project.
I'm also changing the title of the bug. Bug should not specify the solution but
the problem.
> - separating sanlock.log to its own sos plugin
We've had this in mainline sos since 2012.
> - adding plugin for ovirt-imageio
We added this in August last year.
(why I was not automatically assigned to the BZ on changing component to sos? sigh..)
devel_ack+ for 7.7, optionally also for 7.6 if other ACKs will be granted (just coincidentally we are doing re-spin around these days..)
please grant OtherQE (to let get qa_ack+) and describe business justification (for pm_ack+).
(In reply to Pavel Moravec from comment #6)
> please grant OtherQE (to let get qa_ack+) and describe business
> justification (for pm_ack+).
imgbased.log log contains upgrade/installation logs of RHV-H . This log file is necessary for troubleshooting upgrade/installation issues of RHV-H, so in order to have it in next RHVH, is important to have this part of RHEL asap, so 7.6 .
thanks
We didnt catch re-spin on time before blocker+ is required, and the BZ severity/priority does not qualify it to be RHEL7.6 blocker. Hence deferring the BZ to RHEL7.7 and potential/probable inclusion in 7.6.z.
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.
https://access.redhat.com/errata/RHEA-2019:2295