ansible_plays/shrink_lv
1
0
Fork 0
Code Issues 1 Pull Requests Activity

Defined bigboot_size_target ahead of time - AAP bug; try 2?
All checks were successful
Ansible Code Pipeline / Ansible-Development-Pipeline (ansible-dev-centos9) (push) Successful in 15s
Ansible Code Pipeline / Ansible-Development-Pipeline (ansible-dev-debian11) (push) Successful in 13s
Ansible Code Pipeline / Ansible-Development-Pipeline (ansible-dev-debian12) (push) Successful in 13s
Ansible Code Pipeline / Ansible-Development-Pipeline (ansible-dev-fedora39) (push) Successful in 14s

Browse Source
This commit is contained in:
Chris Hammer 2024-02-17 22:54:30 -05:00
parent bca1a3af41
commit 1465bdb9a4
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
bigboot-v3.yml
View File

@ -4,6 +4,9 @@
become: false
gather_facts: true
vars:
bigboot_target_size: "{{ bigboot_size }}"
tasks:
- name: Capture boot device details
ansible.builtin.import_tasks: tasks/capture_boot_device_details.yml

4
group_vars/all
View File

@ -2,7 +2,3 @@
# Default size for Bigboot if otherwise
# not defined
bigboot_size: 1G
# Set initial size target
# (AAP bug?)
bigboot_size_target: "{{ bigboot_size }}"