@mystery, we fixed your FusionHub issue and rebooted the FusionHub few times without issue. We suspect this is due to hardware ID changed at the Digital Ocean. Do let us know if the problem persists.
Thanks.
@mystery, we fixed your FusionHub issue and rebooted the FusionHub few times without issue. We suspect this is due to hardware ID changed at the Digital Ocean. Do let us know if the problem persists.
Thanks.
Thank you very much. All I did was reboot the VM/Droplet via Digital Oceanâs control panel. Do you mind sharing (via private message is fine) how you fixed it so if I encounter it again, I can fix myself? I am also happy to reboot the VM and see if it happens again if you would like to collect logs to see what is going on, just let me know. Thanks again TK!
@mystery, this need to be done by the engineering team. We also try to find out why the hardware ID will be changed occasionally after a reboot. Do let me know if this happens again.
Thanks.
This happened to me when I spun up a test instance in DO shortly after rebooting the Fusionhub becomes unlicensed.
This was a reboot for a firmware upgrade to 8.1
Reaffirming that this is still an issue on DO. I created the VM and FusionHub, shut it down for the Thanksiving weekend, and upon turning it back on it now says âVirtual machine server changedâ and provides no options to do anything. 8.1.0 build 4940.
I am still having the issue too. A simple reboot of a VM and the FusionHub needs to be recreated.
We found that some recent changes in DigitalOcean break FusionHubâs license checking mechanism.
Unfortunately, that cannot be fixed by just firmware upgrade.
If your DO VM is affected (License invalid after reboot/power-cycle), please setup a new DO VM using this VMDK image and migrate the license to the new VM.
Only DO platform is affected.
So you are saying there will not be a fix?
@mystery, there is a fix. You need to setup a new FusionHub by using the vmdk file provided by Kenny, backup config from the existing FusionHub, migrate the existing FusionHub license to the new FusionHub (instruction has been given in the first post of this forum thread), and restore the config to the new FusionHub.
Hope this helps.
Sorry I misunderstood. I thought those were the steps to recover but it would happen again. Thank you for fixing, I will load the new image when I get a chance.
This is still an issue on DO. It happened today. Installed the image last week. Will now proceed to install the fusionhub-do.vmdk image.