Fixes for a few openQA dev setup bugs

While prepping for my demo to the testing team, I ran into a few issues.
These did not come up earlier as I was using an incomplete method for
nuking my local openQA install to test this automation.

- Check for Postgres data directory now correctly checks for a `base`
  dir rather than its parent `data` (which can exist but be empty if
  Postgres has been installed but not initialized
- firewalld service is named `http`, not `httpd`
- Automation now "logs in" to web UI, allowing fifloader.py to execute
This commit is contained in:
Al Bowles 2021-09-02 08:45:26 -05:00
parent d2b9157848
commit 2891c562c8

View File

@ -33,7 +33,7 @@
- name: Check for non-empty postgres data directory
stat:
path: /var/lib/pgsql/data
path: /var/lib/pgsql/data/base
register: postgres_data_dir
- name: If postgresql is not already running, initialize database
@ -68,7 +68,7 @@
permanent: true
state: enabled
loop:
- httpd
- http
- openqa-vnc
- name: Permit VNC traffic for local workers
@ -103,6 +103,11 @@
group: "{{ openqa_group }}"
mode: "0775"
# fifloader.py will fail if the Demo user is not logged in
- name: Authenticate to web UI the first time
uri:
url: "http://{{ openqa_host }}/login"
- name: Run fifloader.py
command: ./fifloader.py -l -c templates.fif.json templates-updates.fif.json
changed_when: "1 != 1"