More input from my side. This only happens when using SVM tunneling. The returned msid is incorrect:
curl -X GET "https://192.168.202.190/api/storage/volumes?fields=name,style,type,msid" -H "X-Dot-SVM-Name: svm0"
{
"records": [
{
},
{
"uuid": "387a6e6e-174c-11ef-8b43-000c2966c17d",
"name": "flex1",
"style": "flexgroup",
"type": "rw",
"msid": 2150247879,
"_links": {
"self": {
"href": "/api/storage/volumes/387a6e6e-174c-11ef-8b43-000c2966c17d"
}
}
}
],
"num_records": 2,
"_links": {
"self": {
"href": "/api/storage/volumes?fields=name,style,type,msid"
}
}
}
Without tunneling, the msid is correct:
curl -X GET "https://192.168.202.190/api/storage/volumes?fields=name,style,type,msid"
{
"records": [
{
},
{
"uuid": "387a6e6e-174c-11ef-8b43-000c2966c17d",
"name": "flex1",
"style": "flexgroup",
"type": "rw",
"msid": 2150247878,
"_links": {
"self": {
"href": "/api/storage/volumes/387a6e6e-174c-11ef-8b43-000c2966c17d"
}
}
}
],
"num_records": 2,
"_links": {
"self": {
"href": "/api/storage/volumes?fields=name,style,type,msid"
}
}
}
Additionally, there seems to be some caching causing inconsistent results.