Bug 1247516

Summary: [kdump] [rhevh] kdump service cannot start: Bad mount point
Product: [oVirt] ovirt-host-deploy Reporter: rhev-integ
Component: Plugins.kdumpAssignee: Martin Perina <mperina>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: high Docs Contact:
Priority: high    
Version: 1.3.0CC: adahms, agkesos, alonbl, anande, bazulay, dougsland, ecohen, ederevea, fdeutsch, lsurette, mgoldboi, mperina, oourfali, pablo.iranzo, pnovotny, pstehlik, rbalakri, Rhev-m-bugs, rhodain, yeylon, ylavi
Target Milestone: ---Keywords: Reopened, ZStream
Target Release: 1.3.2Flags: mgoldboi: Triaged+
oourfali: devel_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the following error message would be displayed when the kdump service failed to start: "Command '/sbin/service' failed to execute". This error message was unclear, and users would need to read the log files to determine that the kdump service had failed to start. With this update, the following message is now displayed in these circumstances: "kdump service restart failed. Please either redeploy with Kdump Integration disabled or fix kdump configuration manually and redeploy the host". This message provides clear indication to users in the Events tab, and prevents the need to read the log files to identify which service failed to start.
Story Points: ---
Clone Of: 1203727 Environment:
Last Closed: 2015-09-03 18:13:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1203727, 1248010    
Bug Blocks:    

Comment 1 Alon Bar-Lev 2015-07-28 09:40:02 UTC
why is this z-stream? it is not critical nor breaking anything.

Comment 2 Oved Ourfali 2015-07-28 10:00:17 UTC
(In reply to Alon Bar-Lev from comment #1)
> why is this z-stream? it is not critical nor breaking anything.

If affects a lot of customers, so GSS requested it.
It is easy to fix, so I've agreed that it should get into 3.5.Z.

Comment 3 Alon Bar-Lev 2015-07-28 10:06:07 UTC
(In reply to Oved Ourfali from comment #2)
> (In reply to Alon Bar-Lev from comment #1)
> > why is this z-stream? it is not critical nor breaking anything.
> 
> If affects a lot of customers, so GSS requested it.
> It is easy to fix, so I've agreed that it should get into 3.5.Z.

this is not a fix, it is only a message stating that you should redeploy, it is not sufficient to release a new package.

Comment 4 Oved Ourfali 2015-07-28 10:49:28 UTC
(In reply to Alon Bar-Lev from comment #3)
> (In reply to Oved Ourfali from comment #2)
> > (In reply to Alon Bar-Lev from comment #1)
> > > why is this z-stream? it is not critical nor breaking anything.
> > 
> > If affects a lot of customers, so GSS requested it.
> > It is easy to fix, so I've agreed that it should get into 3.5.Z.
> 
> this is not a fix, it is only a message stating that you should redeploy, it
> is not sufficient to release a new package.

That is sufficient for them, as currently the issue is hidden.
The reason + a way to resolve it is exactly what they asked for / need.

Comment 11 Pavol Brilla 2015-08-06 13:01:28 UTC
Verified on 3.5.4-1.2.el6ev


2015-08-06 14:46:00,759 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 77048ffb, Call Stack: null, Custom Event ID: -1, Message: Installing Host FQDN_WAS_HERE. Restarting kdump.
2015-08-06 14:46:19,712 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation 10.34.62.46: Failed to execute stage 'Closing up': kdump service restart failed. Please either redeploy with Kdump Integration disabled or fix kdump configuration manually and redeploy the host

Comment 13 errata-xmlrpc 2015-09-03 18:13:37 UTC
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://rhn.redhat.com/errata/RHBA-2015-1717.html