ITOPSENG-647 put product service file in the default path to allow systemctl mask and other linking operations to work properly

DEVELOPMENT.md

@@ -24,7 +24,7 @@ ways to do this; either directly if packaged, or via pip...
 
     # Ubuntu 19.04+, Debian 10+
     sudo apt-get install pipenv python-dev
-    
+
     # Older versions & RHEL/Amazon Linux, etc.
     sudo apt-get install -y python-pip python-dev
     # Or...
@@ -129,7 +129,7 @@ Some notable files and locations:
   /var/log/ansible-bootstrap.log.
 * The Jira installation is under /opt/atlassian/jira/<version>and symlinked to
   /opt/atlassian/jira/current.
-* The systemd service is configured in /etc/systemd/system/jira.service. Its
+* The systemd service is configured in /usr/lib/systemd/system/jira.service. Its
   stdout can be viewed with systemctl status jira.service and journalctl -u
   jira.service.
 * Other Tomcat logs can be located under /opt/atlassian/jira/current/logs/...
@@ -138,11 +138,11 @@ Some notable files and locations:
 * This repository is configured to run tests on [bitbucket pipelines](https://bitbucket.org/atlassian/dc-deployments-automation/addon/pipelines/home).
     * Pipeline definition is located in the [root of the repository](https://bitbucket.org/atlassian/dc-deployments-automation/src/master/bitbucket-pipelines.yml)
     * Pipeline configuration is generated using Jinja2 and a simple python script. Pipeline generator is located [here](https://bitbucket.org/atlassian/dc-deployments-automation/src/master/pipeline_generator/)
-    * A pipeline configuration is generated by running the following make command 
+    * A pipeline configuration is generated by running the following make command
     ```
      make generate-pipeline > ../bitbucket-pipelines.yml
-    ```  
-    
+    ```
+
 * [Molecule](https://molecule.readthedocs.io/en/stable/) tests are run in batches. A single test is run per batch to optimize for a faster dev feedback loop
 
 * If you create a new role or add a new molecule scenario, then please ensure that you generate a new pipeline configuration by running the make command described above. If a new pipeline configuration is not generated, then the CI may not run any tests as it would fail at a pre-test validate stage.

roles/product_startup/molecule/bitbucket/tests/test_default.py

@@ -7,7 +7,7 @@ testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
 
 
 def test_service_file(host):
-    f = host.file('/etc/systemd/system/bitbucket.service')
+    f = host.file('/usr/lib/systemd/system/bitbucket.service')
     assert f.contains("^ExecStart=/opt/atlassian/bitbucket/current/bin/start-bitbucket.sh -fg --no-search$")
     assert f.contains("^UMask=0027$")
     assert f.contains("^LimitNOFILE=4096$")

roles/product_startup/molecule/default/tests/test_default.py

@@ -7,7 +7,7 @@ testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
 
 
 def test_service_file(host):
-    f = host.file('/etc/systemd/system/jira-software.service')
+    f = host.file('/usr/lib/systemd/system/jira-software.service')
     assert f.contains("^ExecStart=/opt/atlassian/jira-software/current/bin/start-jira.sh -fg$")
     assert f.user == 'root'
     assert f.group == 'root'

roles/product_startup/molecule/synchrony/tests/test_default.py

@@ -7,7 +7,7 @@ testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
 
 
 def test_service_file(host):
-    f = host.file('/etc/systemd/system/synchrony.service')
+    f = host.file('/usr/lib/systemd/system/synchrony.service')
     assert f.contains("^ExecStart=/opt/atlassian/bin/start-synchrony$")
     assert f.contains("^EnvironmentFile=/etc/atl$")
     assert f.contains("^EnvironmentFile=/etc/atl.synchrony$")

roles/product_startup/tasks/main.yml

@@ -3,7 +3,7 @@
 - name: "Install systemd service file"
   template:
     src: "product.service.j2"
-    dest: "/etc/systemd/system/{{ atl_systemd_service_name }}"
+    dest: "/usr/lib/systemd/system/{{ atl_systemd_service_name }}"
     owner: root
     group: root
     mode: 0640