Fix UI display bug for iSCSI LUNs
In certain circumstances there are situations where the long-removed "auto" function for iscsi LUN numbering will reassert itself in some kind of edge case. This happens when setting up a new LUN and assigning it to zero. When you click the OK button to add it, the zero is replaced with AUTO. This does not automatically happen for all circumstances. Investigation with Ash revealed the code that is broken creating this:
resource_name = 'services/iscsi/targettoextent'
def dehydrate(self, bundle):
bundle = super(ISCSITargetToExtentResourceMixin, self).dehydrate(
if bundle.obj.iscsi_lunid is None:
bundle.data['iscsi_lunid'] = 'Auto'
bundle.data['iscsi_target'] = bundle.obj.iscsi_target
bundle.data['iscsi_extent'] = bundle.obj.iscsi_extent
bundle.data['iscsi_target'] = bundle.obj.iscsi_target.id
bundle.data['iscsi_extent'] = bundle.obj.iscsi_extent.id
This is on my personal system, so is not accessible via the VPN. If there is anything I can do to assist, please let me know via RC.
The screenshots attached are from FeeNAS 11.1-U1.
Bug fix for iscsi target to extent display where 0 lunid is displayed as auto
#2 Updated by William Grzybowski over 1 year ago
- Status changed from Not Started to Blocked
- Reason for Blocked set to Waiting for feedback
I dont understand, the screenshot clearly shows this does not happen when LUN ID == 0, neither the code says that.
You seem to have a legacy entry with NULL, which means Auto, so what is the issue?
#5 Updated by Dru Lavigne over 1 year ago
- Project changed from TrueNAS to FreeNAS
- Category changed from Middleware to Middleware
- Target version changed from TrueNAS 11.2 to 11.3
- Migration Needed deleted (
- Hide from ChangeLog deleted (
- Support Department Priority deleted (
William: once this is removed in the old UI, please pass to Erin for the new UI.