Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk Space Failure on PAYG-Good 25Mbps Images #45

Open
jonesy1234 opened this issue Sep 4, 2023 · 1 comment
Open

Disk Space Failure on PAYG-Good 25Mbps Images #45

jonesy1234 opened this issue Sep 4, 2023 · 1 comment

Comments

@jonesy1234
Copy link

Describe the bug

While using the base settings for both failover and autoscaling the F5 instance fails due to a lack of diskspace.

Expected behavior

Successful deployment of the cloudformation stack

Current behavior

Stack rolls back dependant on roll back behaviour as no cfn-init completed signal is received.

Possible solution

Adjust the size of /appdata to cater for the extension installation

Steps to reproduce

Provision the stacks using the default parameters.

Screenshots

admin@(ip-10-0-1-5)(cfg-sync )(INOPERATIVE)(/Common)(tmos)# 
Broadcast message from systemd-journald@ip-10-0-1-5 (Sun 2023-09-03 17:27:39 PDT):

load_config_files[10277]: "/usr/bin/tmsh -n -g -a load sys config partitions all " - failed. -- 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. 20338 MB are required to provision these modules, but only 30 MB are available.'
.
Unexpected Error: Loading configuration process failed.

2023 Sep  3 17:27:39 ip-10-0-1-5 load_config_files[10277]: "/usr/bin/tmsh -n -g -a load sys config partitions all " - failed. -- 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. 20338 MB are required to provision these modules, but only 30 MB are available.'

Broadcast message from systemd-journald@ip-10-0-1-5 (Sun 2023-09-03 17:28:19 PDT):

logger[12084]: Re-starting named

Context

Trying to use the functionality created here to assess if using F5 in AWS is a valid / desired use case for a production workload.

Your Environment

Using all defaults in this repo for autoscale and failover.

Have tried with the following VE images

  • 17.1.0.2-0.0.2**PAYG-Good 25Mbps
  • 16.1.3.5-0.0.5**PAYG-Good 25Mbps
@mikeshimkus
Copy link
Collaborator

Hi @jonesy1234, since this solution provisions ASM WAF, it requires a BEST or BEST PLUS image. Check the answer here for more info: #33 (comment)
thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants