Describe the bug
The psm_service_name variable in defaults>main.yml is incorrect, which causes automation to stop mid-way. The PSM service name should be cyber-ark privileged session manager, NOT cyberark privileged session manager.
To Reproduce
Steps to reproduce the behavior:
run PSM automation
psm software is installed, sets the psm_exists variable, however since the service name is spelled wrong, it stops here. As the psm service name doesn't match whats in the playbook.3.
Expected behavior
Using the correct PSM service name allows the PSM install pb to move on/work correctly.
Screenshots
n/a
Environment(please complete the following information):
Ansible version - n/a
Deployment environment - on-prem, but would impact all.
Version [e.g. 22] - v12.6 PSM installs
Additional context
If the PSM service name changes in newer PSM versions, maybe the pb can be adjusted to check for either service naming, old or new.
Describe the bug The psm_service_name variable in defaults>main.yml is incorrect, which causes automation to stop mid-way. The PSM service name should be cyber-ark privileged session manager, NOT cyberark privileged session manager.
To Reproduce Steps to reproduce the behavior:
Expected behavior Using the correct PSM service name allows the PSM install pb to move on/work correctly.
Screenshots n/a
Environment(please complete the following information):
Additional context If the PSM service name changes in newer PSM versions, maybe the pb can be adjusted to check for either service naming, old or new.