scarlet niche
First of all this is only failing in one cluster and for one backend. It works for the other backend in the same cluster.
$ tridentctl create backend --debug -f backend1.json
or
$ tridentctl update backend backend-nosnap --debug -f backend1.json
both exit with the following after a delay of 2m and 10-15seconds:
Error: error communicating with Trident REST API; Post "http://127.0.0.1:8000/trident/v1/backend": EOF
command terminated with exit code 1
At the same time we see a message like this in trident-main container of the trident controller:
time="2023-09-14T18:53:07Z" level=warning msg="error deleting export policy: error deleting export policy: API status: failed, Reason: Ruleset is in use by a volume, Code: 13001" logLayer=core requestID=bc5ff9c1-3905-4b83-ab33-bf7f345dd3ef requestSource=REST workflow="backend=update"
The backend json is simple:
{
"autoExportCIDRs": [
"10.x.0.0/16"
],
"autoExportPolicy": true,
"backendName": "backend-nosnap",
"defaults": {
"snapshotPolicy": "none"
},
"labels": {
"name": "backend-nosnap"
},
"managementLIF": "xxxxt",
"password": "yyyy",
"storageDriverName": "ontap-nas-economy",
"storagePrefix": "zzzz",
"username": "vsadmin",
"version": 1
}
And all of those values are already the same on the existing backend. The other backend file only differs by name, snapshotPolicy, and storageDriver, and it applies in 7 seconds.
Any ideas what to check?