Release Upgrade Delay Question
My system is set to autoupdate to RELEASE. Currently running WHM 88.0.14. I see that 90.0.5 is the current RELEASE version and I understand major updates get a random number of business days delay before applying the update when the cron runs. It's been 4 or 5 days since the current release was approved. Should I continue to wait or manually update the software. I generally prefer to let the cron do its thing.
-
I am wondering the same thing. Usually, I get a delay notice. 0 -
Do either of you have an update failed log? Updates are indeed staggered but if the update hasn't been attempted yet and you would like to move to the next version you're welcome to do so. 0 -
Where would I find this log? 0 -
They're at /var/cpanel/updatelogs/0 -
Do either of you have an update failed log? Updates are indeed staggered but if the update hasn't been attempted yet and you would like to move to the next version you're welcome to do so.
I checked my update log from 27 Aug. The update to 90.0.5 was blocked until Sept 3 "in order to distribute up$". I ran the update via SSH.0 -
Yea that's it. "Upgrade to the next 11.90 build is blocked until Monday, Aug 31, 2020, in order to distribute upgrades over a number of days." Usually, this shows up in WHM but doesn't for me. 0 -
This is strange. Last week, the update log indicated the upgrade to 92.0.4 was blocked until December 8. As it hasn't been updated yet, the latest log shows the upgrade is now blocked until December 15. I am on the "release" tier for upgrades. 0 -
@jdpuglisi - that our staggered update system to ensure that not every cPanel server tries to update all at the same time. You can always force an update at anytime using the "/scripts/upcp --force" command to bypass that staggered release and get the newest update immediately. 0 -
@jdpuglisi - that our staggered update system to ensure that not every cPanel server tries to update all at the same time. You can always force an update at anytime using the "/scripts/upcp --force" command to bypass that staggered release and get the newest update immediately.
I understand the rationale. I also get the updates from the host's mirror. I haven't needed to run the force option when I run the update script through ssh. My comment is two fold. 1. It should be easier to know when the update is blocked until. 2. Modifications to the blocked date should also be more evident.0 -
Thanks for the additional details. How would you recommend we improve that on our side? Currently, if the update gets blocked it leaves an entry in the update log which looks like this: [2020-12-11 01:00:15 -0500] E Blocker found: Upgrade to the next 11.92 build is blocked until Monday Dec 14, 2020 in order to distribute upgrades over a number of days. If you wish to upgrade now, you can do so now with the force option.
If you have notifications enabled this message would also get sent to the manager of the system for review. I'm happy to hear any additional ideas you have on that so I can pass them along to our development team!0 -
Thanks for the additional details. How would you recommend we improve that on our side? Currently, if the update gets blocked it leaves an entry in the update log which looks like this:
[2020-12-11 01:00:15 -0500] E Blocker found: Upgrade to the next 11.92 build is blocked until Monday Dec 14, 2020 in order to distribute upgrades over a number of days. If you wish to upgrade now, you can do so now with the force option.
If you have notifications enabled this message would also get sent to the manager of the system for review. I'm happy to hear any additional ideas you have on that so I can pass them along to our development team!
Well...WHM has an alert when there is an update available in the GUI. Or you can put an alert in the "Update Preferences" panel that shows the system update blocked date.0 -
@jdpuglisi - sounds good to me! Could you get that submitted as a feature request using the link in my signature? 0
Please sign in to leave a comment.
Comments
12 comments