Bug 590380
| Summary: | [PATCH] s-c-kdump crashes on live media | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Lubomir Rintel <lkundrak> | ||||
| Component: | system-config-kdump | Assignee: | Roman Rakus <rrakus> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Han Pingtian <phan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | CC: | atodorov, ovasik, phan, tsmetana | ||||
| Target Milestone: | rc | Keywords: | EasyFix, Patch | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | system-config-kdump-2.0.2.1-16.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-11-10 21:41:43 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Heh. Nice hit. Two things. 1) Why is s-c-kdump on live media? Ah, nevermind. 2) The check was missing, thanks for the patch! (In reply to comment #4) > 1) Why is s-c-kdump on live media? Duh, because I installed it there? :) Default RHEL6 Beta 1 installation contained kdump, possibly due to a same reason, a comps group that dragged it in. It's that useless anyway -- live images can be installed to hard driver via liveinst as they are, and hard drive installations are booted with grub, so s-c-kdump works happily there. I have applied your patch. This can be fixed in system-config-kdump-2.0.2.1-16.el6. system-config-kdump-2.0.2.2-2.el6 in snap #12 LiveCD says: "Don't know how to configure your bootloader". Moving to VERIFIED. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |
Created attachment 412612 [details] Proposed fix, apply with git am Description of problem: Traceback (most recent call last): File "/usr/share/system-config-kdump/system-config-kdump.py", line 1826, in <module> win = MainWindow() File "/usr/share/system-config-kdump/system-config-kdump.py", line 473, in __init__ self.default_kernel = self.default_kernel_name()[:-1] File "/usr/share/system-config-kdump/system-config-kdump.py", line 1422, in default_kernel_name default_kernel = self.dbus_object.getdefaultkernel() File "/usr/share/system-config-kdump/system-config-kdump.py", line 206, in getdefaultkernel return self.dbus_object.getdefaultkernel (dbus_interface = "org.fedoraproject.systemconfig.kdump.mechanism") File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.65 was not provided by any .service files Version-Release number of selected component (if applicable): system-config-kdump-2.0.2-6.el6.noarch Additional info: Since we do not support syslinux, and we probably would not be able to overwrite its configuration (e.g. on ROM media), just provide the user with a sane error message. See the attached patch.