Project

General

Profile

Actions
Copy link

Regression #15880

open

Upgrade available LED not set before branch is selected.

Added by Steve Wheeler 25 days ago. Updated 25 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Luiz Souza
Category:
Upgrade
Target version:
25.03
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
Copy link
 #1

Updated by Luiz Souza 25 days 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
Copy link

Also available in: Atom PDF