[Help]: Will there be a 5.15.24.20 amd64 released in your repository?

[harryfine]

Controller Version

5.15.24.20

Describe Your Issue or Question

Quick question, not problem. First time using Docker, using Synology Container Manager. Have an OC200 for my Omada network control. It's slow and people say use the software controller and some features may be deprecated on the OC200.

So I'm trying to migrate an Omada controller installation from the OC200 to my new Synology docker Omada container. The question is, the OC200 has version 5.15.24.20 while the Docker container on your site is 5.15.24.18. I've been warned that migration only works if they are the same version. I've already tried it once and it failed using the LATEST image of mbently/omada-controller, I aborted and fortunately was still able to recover on the OC200. But now instead of using the LATEST, I have installed a new container, 5.15.24.18. I'm a bit afraid of trying the migration and it crapping out again.

So my question is, will there be a 5.15.24.20?

Expected Behavior

Would like to see a 5.15.20.20 amd64 in your repositories.

Steps to Reproduce

As above

How You're Launching the Container

Not applicable

Container Logs

Not applicable

MongoDB Logs

Not applicable

Additional Context

Thanks for taking the time to answer this.

[mbentley]

So TP-Link has not released a version that is 5.15.24.20 for the software controller. You can see all of the versions that TP-Link has released here from the last time there was an update: #592

So backup and restore tends to only work on the same version but have you tried to do a Site migration from the OC200 after standing up a container of the latest 5.15.24.18 in Docker? I am not sure exactly how you've been trying the migration so let me know if you're trying something different. This seems to indicate that the same Major.Minor.Patch is needed.

[harryfine]

Hi Matt, and thank you.  My bad.  I downloaded the beta which I guess is the .20. I will wait for your .20. I did try to migrate to your LATEST (not the .18) from the beta .20 and it failed.  I've now installed your .18 but was reluctant to try again, pitting the .18 against the .20.  I will wait unless you tell me it's worth a shot. Can I make a one-time donation to you for your work, I didn't see a link. Harry

[mbentley]

Sorry, not sure I am fully following on which beta you downloaded and just want to make sure we are on the same page. Do you mean that you downloaded the beta for the OC200 or you downloaded the software controller beta in a Docker image? Just checking because the latest beta Docker image is 5.15.24.15 and I see they had a 5.15.20.31 and a 5.15.24 release so I'm assuming that you're talking about the OC200 firmware.

Not sure what you mean by the latest (not the .18) from the beta .20; do you mean you tried the latest beta Docker image of 5.15.24.15?

From my personal experience, backups failed to restore on 5.15.20.18 but starting with 5.15.24.17, they do work. I was in contact with TP-Link support on that so if you have not tried a 5.15.24.* version, I would try to upgrade your OC200 to the 5.15.24 firmware and then start a controller with the latest Docker image which is 5.15.24.18; also currently tagged as 5.15.

[mbentley]

Oh yeah, forgot to reply about donations - nope, I don't have anything for donations and am not really looking for anything. I'm just glad that the image has proven to be helpful to people as I would maintain it for myself regardless of if anyone else was using it.

[harryfine]

I'm on the beta Channel in the OC200. That's how I ended up with the .24.20. By LATEST I was referring to the one tagged as such using the Synology container manager to download the docker image.

[mbentley]

Ah ok, I am not familiar with how Synology container manager updates the images/recipes it provides. Or if I did, I've since forgotten how that's done or who is currently maintaining that. I don't maintain any of the container marketplace offerings from solutions like Synology or other NAS devices that offer similar things as those were all contributed by 3rd parties.

Anyway, if you check to see what version the software controller is when you deploy it and if it's 5.15.24.187 or 5.15.24.18, then it should be good to use for a backup and restore. Depending on the image tag they are using, you may just need to pull the image again to get the latest update.