It worked after adding both vault:certificates and ceph-dashboard:iscsi-dashboard relations.
Not so sure why the health check from the dashboard didn't work with HTTP, but in any case, this kind of setup steps should be documented appropriately even if it's a limitation from an upstream.
[before adding a vault relation for certificates but after adding the dashboard relation]
It worked after adding both vault:certificates and ceph-dashboard: iscsi-dashboard relations.
Not so sure why the health check from the dashboard didn't work with HTTP, but in any case, this kind of setup steps should be documented appropriately even if it's a limitation from an upstream.
[before adding a vault relation for certificates but after adding the dashboard relation]
# ceph dashboard iscsi-gateway-list | jq . troll.maas" : { service_ url": "http:// admin:XKFUJ7HR@ 192.168. 151.103: 5000" lion.maas" : { service_ url": "http:// admin:XKFUJ7HR@ 192.168. 151.104: 5000"
{
"gateways": {
"new-
"
},
"robust-
"
}
}
}
^^^ using HTTP as expected.
[after adding both vault certificate relation and dashboard relation]
# ceph dashboard iscsi-gateway-list | jq . troll.maas" : { service_ url": "https:/ /admin: XKFUJ7HR@ 192.168. 151.103: 5000" lion.maas" : { service_ url": "https:/ /admin: XKFUJ7HR@ 192.168. 151.104: 5000"
{
"gateways": {
"new-
"
},
"robust-
"
}
}
}
^^^ using HTTPS as expected