Regression #15880
closedUpgrade available LED not set before branch is selected.
100%
Description
With the introduction of opt-in upgrades a user must now select the new version branch to upgrade.
However the script that set's the upgrade LED status is still using only the selected branch so cannot indicate a new version is available before the branch is set.
/etc/rc.update_pkg_metadata:
( \ sleep $sleep_time \ && /usr/local/sbin/${product_name}-upgrade -uf \ && ( \ /usr/local/sbin/${product_name}-upgrade -Uc > ${tmp_version}.tmp \ ; rc=$? \ ; tail -n 1 ${tmp_version}.tmp > $tmp_version \ ; rm -f ${tmp_version}.tmp \ ; echo $rc > ${tmp_version}.rc \ ; if [ $rc -eq 2 ]; then \ /usr/local/sbin/${product_name}-led.sh update 1 \ ; return $rc \ ; fi \ ; /usr/local/sbin/${product_name}-led.sh update 0 \ ; led_update 0 \ ; return 0 \ )
Updated by Luiz Souza 6 months ago
- Status changed from New to Feedback
- Assignee set to Luiz Souza
- % Done changed from 0 to 100
Fixed.
The cron job is now up to date and using the correct API to check for new releases, update the LED state and the version cache.
Updated by Jordan G about 2 months ago
running 25.03.r.20250411.1649 and having 25.07.a.20250411.1649 available as an update on another branch, no indication of update is present via the front panel LEDs
Updated by Georgiy Tyutyunnik 20 days ago
re-tested on
25.03-BETA (amd64)
built on Wed May 7 16:11:00 UTC 2025
FreeBSD 15.0-CURRENT
issue still present - orange LED is active only if upgrade branch is set on Development snapshots (which is the only current branch that offers an upgrade). If you're on the latest in your current set branch the LED does not activate