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.
Created attachment 1456212[details]
log files
Description of problem:
vcore files cannot be captured for the first time via kdump function in
cockpit. If using kdump function for the second time via cockpit UI, the
vcore files are captured successfully, the first time vcore files are
also captured with the second ones.
Version-Release number of selected component (if applicable):
rhvh-4.2.5.0-0.20180702.0
cockpit-system-169-1.el7.noarch
cockpit-ws-169-1.el7.x86_64
cockpit-dashboard-169-1.el7.x86_64
cockpit-ovirt-dashboard-0.11.29-1.el7ev.noarch
cockpit-169-1.el7.x86_64
cockpit-machines-ovirt-169-1.el7.noarch
cockpit-bridge-169-1.el7.x86_64
cockpit-storaged-169-1.el7.noarch
kernel-3.10.0-862.6.3.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Clean install rhvh-4.2.5.0-0.20180702.0
2. Login to cockpit via root account
3. Go to "Kernel Dump" page
4. Click the "Test Configuration" button
5. After host reboot, login to host and check the vcore files in address
/var/crash
6. Do step 3 ~5 for the second time.
Actual results:
After step 5, there is no vcore files in the address /var/crash.
After step 6, there are vcore files captured in the address /var/crash,
including the first and second time kdump vcore files.
Expected results:
The vcore files should be captured every time after using kdump function
in cockpit.
Additional info:
Comment 4RHEL Program Management
2021-02-15 07:40:03 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Created attachment 1456212 [details] log files Description of problem: vcore files cannot be captured for the first time via kdump function in cockpit. If using kdump function for the second time via cockpit UI, the vcore files are captured successfully, the first time vcore files are also captured with the second ones. Version-Release number of selected component (if applicable): rhvh-4.2.5.0-0.20180702.0 cockpit-system-169-1.el7.noarch cockpit-ws-169-1.el7.x86_64 cockpit-dashboard-169-1.el7.x86_64 cockpit-ovirt-dashboard-0.11.29-1.el7ev.noarch cockpit-169-1.el7.x86_64 cockpit-machines-ovirt-169-1.el7.noarch cockpit-bridge-169-1.el7.x86_64 cockpit-storaged-169-1.el7.noarch kernel-3.10.0-862.6.3.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Clean install rhvh-4.2.5.0-0.20180702.0 2. Login to cockpit via root account 3. Go to "Kernel Dump" page 4. Click the "Test Configuration" button 5. After host reboot, login to host and check the vcore files in address /var/crash 6. Do step 3 ~5 for the second time. Actual results: After step 5, there is no vcore files in the address /var/crash. After step 6, there are vcore files captured in the address /var/crash, including the first and second time kdump vcore files. Expected results: The vcore files should be captured every time after using kdump function in cockpit. Additional info: