Double check downloaded updates are complete before applying them to the server

Martin eaps shared this idea ago

Not Planned

As a systems administrator, I would like a mechanism to check the integrity of a downloadable update (such as a cPanel & WHM update) so that an incomplete update/download isn’t installed, causing issues.

============

The Problem:

I have recently suffered a ticket-issue whereby an automatic update was downloaded by the WHM auto-update system and then applied to the server.

The download failed (unknown exactly why but it was "yum- incomplete transaction") but the update was still applied by the system. This crashed the server and caused a host of secondary problems.

The Solution:

Solution 1:

Therefore, I was surprised to learn from CPanel Support that once a download element is collected on the local server, it is not verified that the download file is complete, such as using an MD5 filesize comparison check to ensure there are no missing "pieces" before trying to install/use the update.

Solution 2:

Or if not possible, the WHM server should check that the yum transaction completed successfully before trying to use the collected file/resource/update.

I like this idea 0

Replies (1)

cPanelDustin ●

Howdy,

Do you have the original ticket you were dealing with this on? I want to do some additional research on it and tie this feature request to it. Additionally, any additional information you can provide with regard to where the failure occurred would be hugely beneficial on this.

Dustin Scherer (he/him) | Product Owner | @dustinscherer

Reply URL

Martin eaps ●

Hello Dustin,

Further info can be found on ticket ID 93477651 however this is somewhat verbose. TL/DR; there was some sort of server interrupt that interrupted standard yum updates but the automatic systems in WHM still used the newly (but incomplete) downloaded installs without checking they were complete, as in this case it was a kernal update this was critical to the system.

URL

cPanelDustin ●

Thanks for the additional information. I'm going to mark this "Not Planned" at the moment because it's not on our immediate timeline. We will update this ticket when we find a place to prioritize this.

Dustin Scherer (he/him) | Product Owner | @dustinscherer

URL