I have encountered this bug in my current deployment. This scenario occurs on deployment when vault is related to the manila-ganesha application but it also re-occurs when the signed cert from the CSR is uploaded into vault.
The workaround mentioned by Yoshi does indeed resolve the issue:
juju run --unit manila-ganesha/leader -- sudo systemctl unmask manila-share
I have encountered this bug in my current deployment. This scenario occurs on deployment when vault is related to the manila-ganesha application but it also re-occurs when the signed cert from the CSR is uploaded into vault.
The workaround mentioned by Yoshi does indeed resolve the issue:
juju run --unit manila- ganesha/ leader -- sudo systemctl unmask manila-share