ControlUp Hive Upgrade Workflow Issue and Request for Improvement

A user encountered an issue with the ControlUp Hive upgrade process and opened a ticket with Support. Upon confirmation from Support, it was found that the upgrade process requires the Hive name to be provided on the command line, which can be inconvenient for organizations managing multiple Hives. The user submitted a feature request for an improved upgrade path and ControlUp is currently looking into this.

Read the entire ‘ControlUp Hive Upgrade Workflow Issue and Request for Improvement’ thread below:

ControlUp Hive upgrade workflow issue

I opened a ticket with ControlUp Support regarding the Hive upgrade process. The installer succeeds, but the upgrade exits with a failure code when the Hive name is not provided. Support confirmed that on an upgrade the Hive name must be supplied on the command line. Without it, the installer defaults to the server name, but this is not an officially supported workflow.

The concern is that this design requires organizations to create a separate deployment for every Hive. This is not practical for any environment that manages many Hives through automated tools. I asked Support to confirm whether this is truly the intended model and requested escalation because this approach does not work at enterprise scale. They indicated that changes would require a feature request through their User Voice portal.

I have asked them to escalate this internally since the ability to deploy upgrades in a single automated process is essential for large environments. Let me know if anyone else has seen this or found a workable approach.

this is indeed as designed and they are correct in it requiring a feature request to be changed

Thanks for the clarification. I have submitted the feature request so it can be considered for future development.

One question I’d appreciate some insight on. If this behavior is truly by design, what was the expected operational model for larger organizations. For example, if an enterprise has 100 Hives, was the assumption that we would create and maintain 100 separate deployments for every upgrade cycle. If that was not the intent, then while my request goes through review, prioritization, development, and eventual release, can you please share what ControlUp would consider the correct method to upgrade a large number of Hives in a single automated workflow.

Right now I’m trying to understand what the supported upgrade path looks like at scale, since the current requirement does not align with how most enterprise automation systems operate.

I cannot comment on that since I was not involved. @member I guess this is a fr for you, I do agree that changing this would be a big thing for customers with multiple custom hives

Hi @member, we are definitely looking into this one. I will update once we have some progress. Thanks for the feedback!

Continue reading and comment on the thread ‘ControlUp Hive Upgrade Workflow Issue and Request for Improvement’.  Not a member? Join Here!