Project

General

Profile

Bug #50423

Allow LUN ID of 0 in new UI

Added by Sebastien BLANCHET over 1 year ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Lola Yang
Category:
GUI (new)
Target version:
Seen in:
Severity:
New
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

Description

In the new GUI, the form iSCSI Associated Target does not accept LUN ID = 0

Expected behaviour

In the new GUI, the form iSCSI Associated Target should accept LUN ID = 0, as the Legacy GUI does.

Step to reproduce

  1. Login to the new GUI
  2. in Storage | Pools, create a zvol foo
  3. in Sharing | Block (iSCSI) | Targets, create a target target
  4. in Sharing | Block (iSCSI) | Extents, create a LUN lun0 and associate it to zvol foo
  5. in Sharing | Block (iSCSI) | Associated Targets, associate extent lun0 to target with LUN ID = 0
  6. the LUN ID line becomes red, and we cannot click on SAVE

On the Legacy UI, the same procedure works for LUN ID = 0

LUN0.gif (11.4 KB) LUN0.gif Sebastien BLANCHET, 10/09/2018 07:39 AM
qlogic_fastutil.jpg (83.1 KB) qlogic_fastutil.jpg Sebastien BLANCHET, 10/09/2018 09:15 AM
Screen Shot 2018-10-26 at 2.57.54 PM.png (27.1 KB) Screen Shot 2018-10-26 at 2.57.54 PM.png Bonnie Follweiler, 10/26/2018 11:59 AM
34107
34121
36990

History

#1 Updated by Sebastien BLANCHET over 1 year ago

I have just checked the Nighthly. The bug is still present in FreeNAS-11.3-MASTER-201810090851

#2 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to Lola Yang
  • Target version changed from Backlog to 11.2-RC2

#3 Updated by Dru Lavigne over 1 year ago

  • Category changed from GUI (new) to Documentation
  • Assignee changed from Lola Yang to Warren Block

Sebastien: the behavior for auto-assigning has changed for 11.2, we'll get that added to the docs.

Doc team: For the new UI: If LUN ID is not provided the next one available will be statically assigned (the old UI did this if you set the LUN to 0).

#4 Updated by Sebastien BLANCHET over 1 year ago

34121

You are right: the new UI documentation says that the LUN ID must be between 1 and 1023.
https://doc.freenas.org/11.2/sharing.html#iscsi-target-extent-config-tab

Therefore I cannot reach LUN ID=0 in the new UI as I did with the Legacy UI.
In the Legacy UI, I can reach LUN ID if I specify LUN ID=0 and this ID is not used yet.

It is not a really a bug, you can close the ticket.

#5 Updated by Warren Block over 1 year ago

  • Assignee changed from Warren Block to Aaron St. John

#6 Updated by William Grzybowski over 1 year ago

Its a bug. LUN ID 0 should be allowed.

#7 Updated by Dru Lavigne over 1 year ago

  • Category changed from Documentation to GUI (new)
  • Assignee changed from Aaron St. John to Lola Yang

#8 Updated by Lola Yang over 1 year ago

  • Status changed from Unscreened to In Progress

#9 Updated by Dru Lavigne over 1 year ago

  • Subject changed from iSCSI Associated Target form does not accept LUN ID = 0 to Allow LUN ID of 0 in new UI
  • Status changed from In Progress to Ready for Testing
  • Needs Merging changed from Yes to No

#10 Updated by Bonnie Follweiler over 1 year ago

36990

Test Passed in FreeNAS-11.2-INTERNAL29
(screenshot provided

#11 Updated by Timothy Moore II over 1 year ago

  • Needs Doc changed from Yes to No

#12 Updated by Timothy Moore II over 1 year ago

  • Needs Merging changed from No to Yes

#13 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done
  • Needs Merging changed from Yes to No

Also available in: Atom PDF