Created attachment 1584712 [details] Log files Description of problem: Kdump service is stopped with an error when changing crash dump location to "Remote over NFS" Mount: <host ip>:<mount path> Compression check-box is enabled The kdump service cannot be started again from UI. Version-Release number of selected component (if applicable): RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso cockpit-system-195-1.el7.noarch cockpit-195-1.el7.x86_64 cockpit-bridge-195-1.el7.x86_64 cockpit-ws-195-1.el7.x86_64 cockpit-machines-ovirt-195-1.el7.noarch cockpit-dashboard-195-1.el7.x86_64 cockpit-storaged-195-1.el7.noarch cockpit-ovirt-dashboard-0.13.2-2.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso 2. Open "Crash dump location" settings window 3. Select "Remote over NFS", and fill up the Mount, then enable the Compression 4. Apply Actual results: An error occurs and kdump service is stopped Expected results: No error occurs when setting kdump location. Additional info:
blocked on cockpit, we'll rebase on a new version when a fix will be available.
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5.
Similar issue occurs when kdump with "Remote ovier SSH" in cockpit UI. test with RHVH-4.3-20190711.1-RHVH-x86_64-dvd1.iso
Created attachment 1590972 [details] log files for remote over ssh
Dependent bug #1709894 has been closed as not a bug. Dependent bug #1724164 has been closed duplicate of above bug #1709894 Closing this as not a bug since "This is the expected behavior, one needs mount the nfs share if he needs to use nfs for kdump."
Nir, can you coordinate with cockpit team on getting this fixed?
Hi, in rhel-8.3 kexec-tools will support using unmounted dump target, so now it should be doable to just put a nfs entry in /etc/kdump.conf and kdump will work. This may help simplify the cockpit setup greatly.
Specificity kexec-tools-2.0.20-20.el8, the bugzilla is https://bugzilla.redhat.com/show_bug.cgi?id=1814121
Moved to oVirt 4.4.4 since CentOS 8.3 won't be available at 4.4.3 GA time.
According to comment 22, QE will verify this bug when getting the 4.4.4 build.
Test with RHVH-4.4-20201029.0-RHVH-x86_64-dvd1.iso, the function is still failed. QE move it to "ASSIGNED"
(In reply to Wei Wang from comment #24) > Test with RHVH-4.4-20201029.0-RHVH-x86_64-dvd1.iso, the function is still > failed. QE move it to "ASSIGNED" Wei, can you follow up with Kairui Song <kasong> with some details see what is the problem?
(In reply to Dave Young from comment #28) > (In reply to Wei Wang from comment #24) > > Test with RHVH-4.4-20201029.0-RHVH-x86_64-dvd1.iso, the function is still > > failed. QE move it to "ASSIGNED" > > Wei, can you follow up with Kairui Song <kasong> with some > details see what is the problem? I've contact with Kairui Song about this problem. I am waiting for his reply. I will update it later.
(In reply to Dave Young from comment #28) > (In reply to Wei Wang from comment #24) > > Test with RHVH-4.4-20201029.0-RHVH-x86_64-dvd1.iso, the function is still > > failed. QE move it to "ASSIGNED" > > Wei, can you follow up with Kairui Song <kasong> with some > details see what is the problem? Hi Kairui, Could you help to follow this? Thanks!
Test with RHVH-4.4-20210413.0-RHVH-x86_64-dvd1 (this build is based on RHEL8.4), the bug still can be reproduced.
This bug/RFE is more than 2 years old and it didn't get enough attention so far, and is now flagged as pending close. Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.
Hi, I'm not sure where I can find the pkgs version used by RHVH, this bug should be fixed in kexec-tools-2.0.20-20, which should be included in RHEL8.4, if it is still failing, maybe it's a new issue, if there are more detail and system log available, that will be very helpful.
Test with the latest rhvh build RHVH-4.4-20210818.0-RHVH-x86_64-dvd1.iso [root@test ~]# rpm -qa|grep kexec-tools kexec-tools-2.0.20-46.el8_4.2.x86_64 [root@test ~]# imgbase w You are on rhvh-4.4.8.1-0.20210817.0+1 [root@test ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.4 The bug is still exist.
Opened a new BZ for cockpit: https://bugzilla.redhat.com/show_bug.cgi?id=2004041 Closing this bug, as it's not an oVirt/RHV issue, thus there is nothing we can do on our side, besides documenting the issue.
(In reply to Lev Veyde from comment #43) > Opened a new BZ for cockpit: > https://bugzilla.redhat.com/show_bug.cgi?id=2004041 > > Closing this bug, as it's not an oVirt/RHV issue, thus there is nothing we > can do on our side, besides documenting the issue. Why is this closed as not a bug? It is a real bug, the function cannot be used at all in RHVH cockpit.
Re-closing as duplicate, which is hopefully less confusing. Wei Wang, this is tracked in bug 2004041 *** This bug has been marked as a duplicate of bug 2004041 ***
(In reply to Wei Wang from comment #44) > (In reply to Lev Veyde from comment #43) > > Opened a new BZ for cockpit: > > https://bugzilla.redhat.com/show_bug.cgi?id=2004041 > > > > Closing this bug, as it's not an oVirt/RHV issue, thus there is nothing we > > can do on our side, besides documenting the issue. > > Why is this closed as not a bug? It is a real bug, the function cannot be > used at all in RHVH cockpit. It's a real bug, just not one of RHV-H/oVirt. The source of the issue is in the cockpit, and it should be fixed there. Thus after checking and debugging the issue, a new bug for cockpit was opened, and once that the issue is fixed there, it will become fixed in RHV-H/oVirt (and RHEL/CentOS) as well (once the build will include the fixed cockpit package(s) ).