-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hiveaps don't survive autoupdate to new releases (from v2019/v2021) #3181
Comments
Update: I have no clue why they went offline then unless they weren't able to reactivate wifi (for meshing) after trying to install the sysupgrade. (which probably gets tried every hour) |
Apparently it's a bug in the autoupdater: The Image check fails after all network has stopped, but network isn't started again after the failure, so the device is left without any network connectivity. |
the actual issue is described in #2742 as @kpanic23 already wrote. you have to act manually on site. |
ok, then this issue will remain open for the HiveAP 121. |
hm, this issue is simply not true as they "survive" it other than stated. regarding known issues: you can answer it yourself by looking at the past release notes ;-) |
Technically they do. The problem is that the autoupdater stops networking before the update, aborts because of image version mismatch and just exits without re-enabling networking. This results in the node fully running but without any network connectivity. I've removed the image from our update server, so the nodes don't get stuck every hour again trying to upgrade. |
@kpanic23 This was fixed with freifunk-gluon/packages@0648b2d |
Ah, great! |
oh wow, and reported by myself over 5 years ago... |
@Djfe can we close this issue? |
In Aachen we lost 100% of our Hive APs during migration to newer releases.
5x HiveAP 121
2x HiveAP 330
the 330s were lost on update from v2019 to v2021.
They are both installed at the same spot but we only managed to find one so far.
A powercycle was enough to bring it back to live.
We lost it again a couple days later on the update from v2021 to v2023.1.
The 121s updated just fine from v2019 to v2021 but were lost a couple days later, when we rolled out v2023.1 for them.
We haven't really gotten hands on the devices, yet.
But we wanted to let people know about this issue :)
If we get hands on, then we'll retest our migration and watch logs and we will also test v2023.2
The text was updated successfully, but these errors were encountered: