Project

General

Profile

Bug #36913

Avoid traceback if disk in iSCSI extent does not exist

Added by Lola Yang about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Severity:
Low Medium
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

request: http://localhost:4200/api/v1.0/services/iscsi/extent/?limit=0
response: {"error_message": "Sorry, this request could not be processed. Please try again later."}

screen shot attached.

Associated revisions

Revision d3e7a64f (diff)
Added by William Grzybowski about 2 years ago

fix(api): avoid traceback if disk in iscsi extent does not exist Ticket: #36913

Revision ba0d4143 (diff)
Added by William Grzybowski about 2 years ago

fix(api): avoid traceback if disk in iscsi extent does not exist Ticket: #36913

History

#1 Updated by Lola Yang about 2 years ago

  • File debug.tgz added

#2 Updated by William Grzybowski about 2 years ago

  • Status changed from Unscreened to Not Started
  • Target version changed from Backlog to 11.2-BETA2
  • Severity changed from New to Low Medium

#3 Updated by William Grzybowski about 2 years ago

  • Status changed from Not Started to Ready for Testing

https://github.com/freenas/freenas/pull/1498

Acceptance Criteria

A disk has to be used as a iscsi extent and then removed from the machine. You should still be able to see the iSCSI Extent datagrid.

#4 Updated by Dru Lavigne about 2 years ago

  • Subject changed from iscsi extent rest call error to Avoid traceback if disk in iscsi extent does not exist
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#5 Updated by Dru Lavigne about 2 years ago

  • File deleted (debug.tgz)

#6 Updated by Michael Reynolds about 2 years ago

  • Status changed from Ready for Testing to Passed Testing

Created an iSCSI Device Extent
shut down FreeNAS
removed the data disk
booted back up
the iSCSI extent is still there and no traceback
There is nothing to indicate there is an issue
the Extent can be edited to point to a new device

#7 Updated by Michael Reynolds about 2 years ago

  • Needs QA changed from Yes to No

#8 Updated by Dru Lavigne about 2 years ago

  • Subject changed from Avoid traceback if disk in iscsi extent does not exist to Avoid traceback if disk in iSCSI extent does not exist
  • Status changed from Passed Testing to Done

Also available in: Atom PDF