Project

General

Custom queries

Profile

Actions

Regression #15880

open

Upgrade available LED not set before branch is selected.

Added by Steve Wheeler 5 months ago. Updated 2 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Upgrade
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.03
Affected Architecture:

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 \
    )

Actions #1

Updated by Luiz Souza 5 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.

Actions #2

Updated by Jordan G 3 months ago

tested with 25.03.b.20250120.1851 using 6100 as hardware - without the newer update branch selected the indicator light flashes amber to show a newer version is available

Actions #3

Updated by Jordan G 2 days 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

Actions

Also available in: Atom PDF