public_git/freenas-proxmox
1
0
Fork 0
mirror of https://github.com/TheGrandWazoo/freenas-proxmox.git synced 2026-10-20 18:57:04 +02:00
Code Issues Projects Releases Wiki Activity

Change iscsi_lunid values of 'undef' to 0 (zero)

Browse Source 
- In FreeNAS 11.1 it seems like a Lun of 0 becomes 'Auto'. When the API
returns the targent_to_extent data any Lun of "Auto" become 'undef' and
causes issues and errors in the syslog. This change corrects this
behavior. Have tested with adding, detaching, removing and "Moving Disk"
functions of Proxmox version 5.1-51.
This commit is contained in:
Kevin Scott Adams
2018-04-18 13:53:29 -04:00
parent 6931f4a232
commit af42dfd008
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
perl5/PVE/Storage/LunCmd/FreeNAS.pm
+9
View File
@@ -359,6 +359,15 @@ sub freenas_iscsi_get_target_to_extent {
if ($code == 200) {
my $result = decode_json($client->responseContent());
syslog("info","FreeNAS::API::get_target_to_extent() : sucessfull");
# If 'iscsi_lunid' is undef then it is set to 'Auto' in FreeNAS
# which should be '0' in our eyes.
# This gave Proxmox 5.x and FreeNAS 11.1 a few issues.
foreach my $item (@$result) {
if (!defined($item->{'iscsi_lunid'})) {
$item->{'iscsi_lunid'} = 0;
syslog("info", "FreeNAS::API::get_target_to_extent() : change undef iscsi_lunid to 0");
}
}
return $result;
} else {
freenas_api_log_error($client, "get_target_to_extent");