Bug #8870

Webgui incorrectly reports "The system is on the latest version".

Added by Steve Wheeler over 2 years ago. Updated 5 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:
Release Notes:


In some circumstances the dashboard can report that the system is on the latest version when in fact the pkg system is unable to connect to the repos.

This falsely implies good connectivity when it should report "Unable to check for updates".

It's not clear exactly when this happens but I have seen it at first boot of a fresh install.

Associated revisions

Revision 6701a859 (diff)
Added by Renato Botelho 6 months ago

Fix #8870

When it's not possible to check if a new version is available for any
reason, show a proper message instead of keep using cached information


#1 Updated by → luckman212 over 2 years ago

Yep I hit this one a couple of days ago, on whatever snap was latest as of 9/5

pkg goes braindead in some way if there's a connectivity problem via the default route. In my case I was configuring a new SG-3100 for a remote site. I set the WAN interface to the static IP of the remote site so I could ship it out "plug n play" -- but in order to run updates and grab the openvpn export package I programmed opt1 as a temporary DHCP WAN via my mobile hotspot.

Even after making opt1 the default gw, as well as making use of PiBa's new "default gw via gateway group" feature, pkg remained borked and said "you're on the latest version" and was unable to view anything in Package Manager either until a full reboot.

I wish I had more time to play around and figure out why but that day I had to get it out the door...

#2 Updated by Steve Wheeler about 2 years ago

  • Target version set to 48

#3 Updated by Jim Pingle about 2 years ago

  • Target version changed from 48 to 2.5.0

#4 Updated by Jim Pingle over 1 year ago

  • Category changed from Web Interface to Upgrade

#5 Updated by Steve Beaver 6 months ago

  • Assignee set to Renato Botelho

#6 Updated by Steve Beaver 6 months ago

Issue still exists

#7 Updated by Renato Botelho 6 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#8 Updated by Max Leighton 5 months ago

  • Status changed from Feedback to Resolved

Tested in

2.5.0-DEVELOPMENT (amd64)
built on Thu Oct 29 07:01:19 EDT 2020

Received "Unable to check for updates" instead of "Up to date" as seen on 2.4.5p1

Marking the ticket resolved.

Also available in: Atom PDF