I have attached the log of pacemaker as well.
In this log, I could see that the pacemaker resource is failing with the following error.
Could not issue start for res_manila_share_manila_share: Unit manila-share.service is masked.
This symptom is seen every time I deploy this environment.
BTW, since Vault is used as TLS termination for API endpoints, the reproducible steps are
1. Deploy OpenStack with Vault
2. Unlock and activate Vault. Before this, hacluster-manila-ganesha is all fine
3. After the relation with Vault is completed, hacluster-manila-ganesha gets stuck. I have waited for more than 30 minutes, but it was still stuck.
I have attached the log of pacemaker as well.
In this log, I could see that the pacemaker resource is failing with the following error.
Could not issue start for res_manila_ share_manila_ share: Unit manila- share.service is masked.
This symptom is seen every time I deploy this environment.
BTW, since Vault is used as TLS termination for API endpoints, the reproducible steps are
1. Deploy OpenStack with Vault manila- ganesha is all fine manila- ganesha gets stuck. I have waited for more than 30 minutes, but it was still stuck.
2. Unlock and activate Vault. Before this, hacluster-
3. After the relation with Vault is completed, hacluster-