why is this z-stream? it is not critical nor breaking anything.
(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.
(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.
(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.
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
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