Can't send PATCH request to Target with PODM API to set InitiatorIQN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS RSD |
Invalid
|
Critical
|
Priyank Durugkar | ||
Intel-rsd |
Confirmed
|
High
|
Priyank Durugkar |
Bug Description
When Allocating a node with remote storage there isn't a way to set the InitiatorIQN for the Target. It defaults to "ALL", which is causing a mismatch with the target Portal IPs. This is blocking MAAS from being able to deploy a remote target.
The node's remote storage target is:
root@maas-dev:~# curl -s -k -u admin:admin -X GET https:/
{
"@odata.context" : "/redfish/
"@odata.id" : "/redfish/
"@odata.type" : "#RemoteTarget.
"Id" : "83",
"Name" : "iSCSI Remote Target",
"Description" : "iSCSI Remote Target description",
"Status" : {
"State" : "Enabled",
"Health" : "OK",
"HealthRollup" : "OK"
},
"Type" : null,
"Addresses" : [ {
"iSCSI" : {
"TargetLUN" : [ {
"LUN" : 1,
}
} ],
"TargetIQN" : "iqn.io.
"
"
}
} ],
"Initiator" : [ {
"iSCSI" : {
"
}
} ],
"Oem" : { },
"Links" : {
"Oem" : { }
}
"@odata.context" : "/redfish/
"@odata.id" : "/redfish/
"@odata.type" : "#RemoteTarget.
"Id" : "83",
"Name" : "iSCSI Remote Target",
"Description" : "iSCSI Remote Target description",
"Status" : {
"State" : "Enabled",
"Health" : "OK",
"HealthRollup" : "OK"
},
"Type" : null,
"Addresses" : [ {
"iSCSI" : {
"TargetLUN" : [ {
"LUN" : 1,
}
} ],
"TargetIQN" : "iqn.io.
"
"
}
} ],
"Initiator" : [ {
"iSCSI" : {
"
}
} ],
"Oem" : { },
"Links" : {
"Oem" : { }
}
When SSH'ing into the node after commissioning we see that the target is iqn.blvt2 instead of the expected iqn.io.
ubuntu@
10.1.0.100:3260,1 iqn.blvt2
This is blocking nodes with remote storage from being deployed.
description: | updated |
Changed in maasrsd: | |
assignee: | nobody → Priyank Durugkar (priyankd) |
Changed in maasrsd: | |
status: | Confirmed → Fix Released |
Changed in maasrsd: | |
status: | Fix Released → Invalid |
Hi Newell,
PODM by default sets "ALL" as InitiatorIQN for iSCSI Targets, which causes that only an iSCSI client with Initiator "ALL" can discover/connect to them.
A quick solution would be to change "ALL" to an empty string in the PODM's request which creates iSCSI Targets. This way created iSCSI Targets would have no InitiatorIQN assigned, and clients with any Initiator could discover/connect to them.
A more complex solution would be to add a possibility to assign a custom InitiatorIQN for iSCSI Targets when allocation a new node from PODM. This fix would require more time and effort to implement.
Is the quick solution sufficient to enable you, or the second is required?
Best Regards,
Tomasz