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

Defined bigboot_size_target ahead of time - AAP bug?
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 15s

Browse Source
This commit is contained in:
Chris Hammer 2024-02-17 22:52:36 -05:00
parent 8eec5d34d4
commit bca1a3af41
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
group_vars/all
View File

@ -3,9 +3,6 @@
# not defined # not defined
bigboot_size: 1G bigboot_size: 1G
# We use padding just to ensure there's # Set initial size target
# available space to expand /boot to. # (AAP bug?)
# bigboot_size_target: "{{ bigboot_size }}"
# By default the value is 1.05, or 5%
# greater than bigboot_size
bigboot_shrink_padding: 1.05