Is forced update an intended behaviour?

[martin MHC]

So my server had WHM 100.12 on it, and I had set my update preferences to the lowest possible (stable), and I had for a few days had a popup on the top RHS saying "ready to update to 102.15 click here" as usual, and I expressedly didn;t click that link, as I wanted to retain paper lantern as long as possible.

Today, I find that the server has auto-updated itself to Jupitar theme version 102.15 without any confirmation. Is this intended and expected behaviour?



.
.
.
.
.
.

Before being forced to use Jupitar I never realised how many shades of white existed!

 

[cPRex]

Hey there! Yes, that is the intended behavior. The notification is just letting you know that you have the option to perform that update immediately instead of letting it happen automatically overnight. You can always check the update settings in WHM >> Update Preferences.

 

[martin MHC]

Hey there! Yes, that is the intended behavior. The notification is just letting you know that you have the option to perform that update immediately instead of letting it happen automatically overnight. You can always check the update settings in WHM >> Update Preferences.

Thanks for confirming Rex, I figured this wasn't ticket worthy as I suspected updates were inevitable.
In the past I've always got them quickly but with the transition to Jupitar wanted to put it off as long as possible.

Cheers

 

[cPRex]

You can always force the server to stay on a certain version, but that work needs to happen on the command line by editing the /etc/cpupdate.conf file.