Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR increases the
/
filesystem from 4.5GiB to 10GiB and the/var
filesystem from 2GiB to 12GiBThe root filesystem change is needed so that upgrades can be performed by using
bin/update
as described in #219. In this case the new gems being installed in/opt/rubies/ruby-2.3.1/lib/ruby/gems
were filling up the space on the root filesystem. It should be noted that after upgrading the appliance, we can runbundle clean --force
to remove old versions of updated gems and reclaim some space.The
/var
filesystem change is needed so that we can use embedded ansible. Both the rpm and docker versions require more space. The rpm version has an explicit check which requires at least 10GiB of free space on the/var
partition. We currently ignore that check here, but it isn't checking without reason, so we would like to stop doing that.Additionally the container version of embedded ansible (AWX) which is being developed in ManageIQ/manageiq#16205 will need more space in
/var
for the docker daemon.Adding WIP until my test build finishes.