CURRENT was 11.50, then "disabled", now 11.48?
Last night all our servers were upgraded to 11.50 as they're looking at the CURRENT branch. No problems since the upgrade.
Just came to look at layer2.cpanel.net and noticed CURRENT said "disabled" instead of the version number. Gave it a few more seconds and refreshed; now it says:
Latest cPanel & WHM Builds (All Architectures)
TIER Version Release Date
STABLE 11.48.3.0 Mon Apr 13 23:39:22 2015
RELEASE 11.48.4.2 Mon May 4 18:28:05 2015
CURRENT 11.48.4.2 Tue Apr 21 21:23:10 2015
EDGE 11.49.9999.120 Thu Apr 30 20:28:32 2015
Even EDGE is wrong. What's going on? Am I to expect problems with 11.50 or something? What happens when the auto update runs tonight? Will it downgrade everything and is 11.50 even downgradeable?
-
Just logged into WHM and saw this... 28741 0 -
layer2.cpanel.net now says: Latest cPanel & WHM Builds (All Architectures) TIER Version Release Date STABLE 11.48.4.4 Tue May 19 00:29:31 2015 RELEASE 11.48.4.4 Tue May 19 00:29:31 2015 CURRENT disabled Thu May 21 15:53:33 2015 EDGE 11.49.9999.129 Tue May 19 15:53:05 2015 0 -
Same problem here, CURRENT is saying disabled, and last night and this morning a couple of servers did the update. I tried the CURRENT update that says disabled now, on a test server, and he updated to 11.48.4.4 What will happen to the servers that did the update to 11.50.0.4 automatically ?? We need some words from you CPANEL, please, this is urgent. 0 -
disabled is a new feature we put in for 11.50 and beyond releases. It allows us to block additional people from upgrading to whatever tier (CURRENT) is set to disabled. This allows us to address critical bugs in a more thoughtful way without rushing a fix. If your server is set to current, then you will be told the following when you try to upcp: " cPanel has temporarily disabled updates on the central httpupdate servers. Please try again later." When we address the problem, current will be set to a new version and your next upcp will upgrade like normal. 0 -
now it says: Latest cPanel & WHM Builds (All Architectures) TIER Version Release Date STABLE 11.48.3.0 Mon Apr 13 23:39:22 2015 RELEASE 11.48.4.2 Mon May 4 18:28:05 2015 CURRENT 11.48.4.2 Tue Apr 21 21:23:10 2015 EDGE 11.49.9999.120 Thu Apr 30 20:28:32 2015 Even EDGE is wrong. What's going on?
It appears you've identified a server that shouldn't be listed in DNS. We're investigating now and will probably take that server out of rotation to solve the problem. NOTE: Even if you had hit this server, your cPanel systems that upgraded would have refused to downgrade, so this was effectively set to "disabled" for your servers. --Todd0 -
disabled is a new feature we put in for 11.50 and beyond releases. It allows us to block additional people from upgrading to whatever tier (CURRENT) is set to disabled. This allows us to address critical bugs in a more thoughtful way without rushing a fix. If your server is set to current, then you will be told the following when you try to upcp: " cPanel has temporarily disabled updates on the central httpupdate servers. Please try again later." When we address the problem, current will be set to a new version and your next upcp will upgrade like normal.
Why isn't this in the release notes? I thought that was the whole point of release notes; to let people know what has changed and why. The release notes is the first place I looked before coming here to complain; it would have saved a lot of time and hassle!0 -
So the if it is disabled, some serious problem is happenning with the release. Are we assured by cpanel, that the servers that updated to 11.50, will not have problems? 0 -
So the if it is disabled, some serious problem is happenning with the release. Are we assured by cpanel, that the servers that updated to 11.50, will not have problems?
Yes - cPanel have yet to confirm why the release is disabled. If it's disabled due to fixing critical bugs, what critical bugs? The users (like us) who have already upgraded to that release have a right to know what could potentially be happening (or not) to their servers which has caused cPanel to disable the release.0 -
Yes - cPanel have yet to confirm why the release is disabled. If it's disabled due to fixing critical bugs, what critical bugs? The users (like us) who have already upgraded to that release have a right to know what could potentially be happening (or not) to their servers which has caused cPanel to disable the release.
I don't want to know specifically what the bugs are, since could be security, and say it in public until is fixed, is very bad. I really just want to know, if you can SLEEP WITHOUT WORRIES, that the bugs will not break the servers.0 -
If it's security related, I'd be asking how severe and what it entails. 0
Please sign in to leave a comment.
Comments
11 comments