Bug 1659961 - kdump always started in rhel 7.5
Summary: kdump always started in rhel 7.5
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: ovirt-host
Version: 4.2.7
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-17 09:36 UTC by Fabrice Bacchella
Modified: 2018-12-25 11:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-17 09:50:07 UTC
oVirt Team: Integration
Embargoed:


Attachments (Terms of Use)

Description Fabrice Bacchella 2018-12-17 09:36:47 UTC
I disabled kdump on an host:

    <kdump_status>disabled</kdump_status>

I also disable the service in systemd:

    systemctl status kdump
    ...
    Loaded: loaded (/usr/lib/systemd/system/kdump.service; disabled; vendor preset: enabled)
    ...

But's it's required by vdsmd:

    systemctl show vdsmd.service | grep Wants
Wants=dev-hugepages1G.mount mom-vdsm.service abrtd.service ovirt-imageio-daemon.service libvirt-guests.service system.slice kdump.service

So it's started anyway. Is there a way to prevent that ?

Comment 1 Yedidyah Bar David 2018-12-17 09:50:07 UTC
(In reply to Fabrice Bacchella from comment #0)
> I disabled kdump on an host:
> 
>     <kdump_status>disabled</kdump_status>
> 
> I also disable the service in systemd:
> 
>     systemctl status kdump
>     ...
>     Loaded: loaded (/usr/lib/systemd/system/kdump.service; disabled; vendor
> preset: enabled)
>     ...
> 
> But's it's required by vdsmd:
> 
>     systemctl show vdsmd.service | grep Wants
> Wants=dev-hugepages1G.mount mom-vdsm.service abrtd.service
> ovirt-imageio-daemon.service libvirt-guests.service system.slice
> kdump.service
> 
> So it's started anyway. Is there a way to prevent that ?

bugzilla isn't a support forum/service, please ask such questions on systemd-related forums/lists/etc. Thanks.

I think you can try 'systemctl mask', didn't try it, no idea what this will cause to vdsm if it works.


Note You need to log in before you can comment on or make changes to this bug.