Project

General

Profile

Bug #15413

Ungraceful Update without a Gateway set

Added by Michael Dexter over 4 years ago. Updated about 4 years ago.

Status:
Closed: Duplicate
Priority:
Nice to have
Assignee:
William Grzybowski
Category:
GUI (new)
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

If a LAN IP is set but no gateway and presumably DNS servers, one gets a traceback rather than a graceful error about not being able to reach the update servers when clicking Update: Check Now

Request Method: GET
Request URL: http://192.168.1.210/system/update/check/
Software Version: FreeNAS-9.10-STABLE-201605021851 (35c85f7)
Exception Type: URLError
Exception Value:
<urlopen error [Errno 51] Network is unreachable>
Exception Location: /usr/local/lib/freenasOS/Configuration.py in TryGetNetworkFile, line 638
Server time: Wed, 18 May 2016 15:36:13 -0700
Traceback

<Traceback>

Suggestion: A message that FreeNAS cannot connect to the update server

Screen shot attached.

FreeNAS-9.10-NoNetUpdate.tiff (339 KB) FreeNAS-9.10-NoNetUpdate.tiff Michael Dexter, 05/18/2016 03:37 PM

Related issues

Has duplicate FreeNAS - Bug #12047: Updater needs more verbose output for error conditionsResolved2015-10-23

History

#1 Updated by William Grzybowski over 4 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have
  • Target version set to 261

#2 Updated by William Grzybowski over 4 years ago

  • Status changed from Screened to Closed: Duplicate

#3 Updated by William Grzybowski over 4 years ago

  • Has duplicate Bug #12047: Updater needs more verbose output for error conditions added

#4 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from 261 to N/A

Also available in: Atom PDF