Possible to modify default update setting in Configuration?

  • 1
  • Question
  • Updated 1 year ago
  • (Edited)
In Configuration, when I see an AP that has the red exclamation point in the Audit column, I click on Update, Update Devices, which shows me the following:

Is there a way to have that last check box ("Upgrade these devices to the latest version of HiveOS") to default to not being checked when going through this update process?  I always like to manually upgrade my access points, so I would never want them to automatically upgrade if I just happen to forget to uncheck this box when I have to update the configuration on the APs, especially since I work for a school district and doing an accidental upgrade during the middle of a school day would cause a disruption.

I'm currently running HM 6.6r3a on-premise.
Photo of Rob Pritchard

Rob Pritchard

  • 86 Posts
  • 8 Reply Likes

Posted 2 years ago

  • 1
Photo of Fraser Hess

Fraser Hess

  • 60 Posts
  • 7 Reply Likes

I'm going to add my voice here and say that I think this default needs to be changed. It's a big breach of things like Convention over Configuration and The Principle of Least Astonishment.  Defaulting the simplest of configuration changes to also updating the code (introducing more risk) and a rebooting all the access points (complete network disruption) means we have to be super careful on every configuration update while the code is behind.

Design wise, I propose the following. The Upgrade these devices to the latest version of HiveOS box should disappear unless a code update is available. When a HiveOS update is available the box should appear and be unchecked by default. Additionally, it should show the HiveOS version that would be installed by if the box was checked.}

Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
In regards to your "design wise" comment, the Upgrade these devices to the latest version of HiveOS box is not there if all the APs that are selected are at the current HiveOS version. It will only appear if there is at least 1 AP selected that is at an older HiveOS version. Otherwise it isn't there. And it doesn't show the HiveOS version because this is the "Simple Update". If you use the "Advanced Update", then you will see the version(s). And if you were doing multiple APs that had different versions of HiveOS, it could be difficult to show which APs were getting which HiveOS version.

There are situations when you would use the Simple Update, and there are times when you would want to use the Advanced Update. I think it is good that you have the option to do either. And whichever you do choose, you still have an additional warning if a reboot is required. So even if you forgot that you left the upgrade box checked, you still have to click through another message warning you about a reboot.

And you can change the default action for when the software is activated. So it is possible that you could have the upgrade set so that it only activates after a reboot rather than a set amount of time after installing the software. Then the AP wouldn't reboot on its own; it would require you to manually reboot it.
Photo of Luke Harris

Luke Harris

  • 265 Posts
  • 18 Reply Likes
I seldom use this function to perform device updates. I would stick to upgrading HiveOS and configuration using the advanced option. But will echo agreement with the above statement. Default behaviors should be configurable.
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
If you are familiar with HiveManager-NG you are aware that it recognizes the concept of our long term stable releases (aka "Golden" releases) versus feature releases, and once you have chosen one or the other, future prompts follow your choice (ie if you select golden releases, you will only be prompted to upgrade when/if a new golden release is available). 

Based on feedback like this conversation, we are making similar changes to HiveManager classic in the next release. If you have already upgraded your HiveManager Online instance to version 6.8r7 then some time in the next week or two you will observe this change in behavior when we patch those to version 6.8r7a.

If you are using an on-premises HiveManager, updates will be available at about the same time.