[Fixed in 2.3.0] api/v2/devices/<device_id>/backups not working

[swong]

Hi there,

I have been using APIv2 to backup all configs from Unimus to my local file system for a while.

It was working well with 2.0.9 until we upgraded to 2.2 on 11-Sep and then the APIv2 not working for me.

I confirmed I can backup al latest config via api/v2/devices/backups/latest but I got page not found due to the device id not found.

-bash-4.2$ curl -s -H 'accept: application/json' -H 'Authorization: Bearer <our_token>' 'https://<our_server>/api/v2/devices/2/backups/latest'
{"timestamp":1664425593923,"code":404,"error":"Not Found","message":"Device with id 2 not found"}

Regards,
Tung

[Vik@Unimus]

Hello,

Thank you for the report. I can confirm this is a bug. We have already identified the cause and fixed it. The fix will be available in the next release (it will be most likely a beta release for 2.3.0). As soon as that happens, I will update this thread.

[swong]

Thanks for your update!

[smallsam]

I just hit this bug, fairly sure it was on the 2.2.3 to 2.2.4 upgrade.

Is a 2.2.3 downgrade or 2.2.5 release an option, I'd rather not take a 2.3 beta to fix this. It seems like it was an unintended regression.

[Vik@Unimus]

In this case, yes, it is possible to downgrade. When we talk 2.2.4, it is possible to downgrade to whether 2.2.3 or 2.2.2 at most. If you run Unimus on Windows, you could just download an older version of the installer, whether one for 2.2.2 or 2.2.3

https://download.unimus.net/unimus/2.2.2/Installer.exe
https://download.unimus.net/unimus/2.2.3/Installer.exe

and run it. As for Linux, same applies, but with the exception that you would be only replacing Unimus binary

https://download.unimus.net/unimus/2.2.2/Unimus.jar
https://download.unimus.net/unimus/2.2.3/Unimus.jar

in the /opt/unimus folder.

In either case, I would recommend backing up Unimus DB in beforehand, just in case, and stopping Unimus first before doing either of above.

[smallsam]

Thanks. We successfully downgraded to 2.2.3.

[Vik@Unimus]

Hello Everyone,

The fix for this bug is out and available starting now with 2.3.0-Beta1 and onward. You can find more information in our Beta branch thread

viewtopic.php?f=4&t=1599

If you are running Unimus on Windows, then feel free to just download and run the installer.
In case Unimus is deployed on Linux, then unless you are running it already, I would first recommend upgrading to the latest stable version (https://unimus.net/download, currently 2.2.4), stopping Unimus service afterwards, downloading the new executable (.jar file) from the Beta download page and replacing the existing binary in /opt/unimus folder with the new one.

If you get a chance, give it a try and let us know if it worked as expected, or in case you encounter any other issue.