Repository navigation
Close gaps between Ansible Playbook and install.sh #241
Description
Bug Report
Description
Currently, the setup of Fireactions uses two different methods to set up the thin pool. While technically both work is extremely confusing when debugging and finding both methods (at least for a novice like me).
Expected Behavior
The project uses a single method to provision the devicemapper thin pool.
Current Behavior
Thin Pools are set up in different locations with different parameters.
Possible Solution
Merge the two solutions and align them.
Steps to Reproduce (for bugs)
-
Install using Ansible Playbook
-
Fireactions doesn't start successfully (see Add setting up devmapper thin pool fireactions-images#42)
-
Setup thin pool manually
-
Install using install.sh script
-
See thin pool being set up via lvm
Your Environment
- Fireactions version: 0.3.0
- OS: openSUSE Leap 15.6
Activity
SchoolGuy commentedon May 4, 2025
Another issue is the different notation of the GitHub Secret key in the config file.
SchoolGuy commentedon May 4, 2025
Next issue that is a gap between the script and Ansible Playbook is the fact that after the Ansible Playbook no kernel is downloaded.