Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1
Opened: Dec 29, 2023 Severity: 4-Minor
Provisioning fails due to /appdata being too small. admin@(ip-172-31-1-41)(cfg-sync Standalone)(Active)(/Common)(tmos)# load sys config merge from-terminal sys provision afm { level nominal } sys provision asm { level nominal } sys provision avr { level nominal } sys provision fps { level nominal } sys provision ltm { level nominal } ^D ltm log: Nov 23 05:05:00 localhost.localdomain notice logger[28697]: /usr/bin/mcpd -dbmem 512 -listen 127.0.0.1 -forceload -f ==> /usr/bin/bigstart enable pgadmind Nov 23 05:05:00 localhost.localdomain notice logger[28699]: /usr/bin/mcpd -dbmem 512 -listen 127.0.0.1 -forceload -f ==> /usr/bin/bigstart start pgadmind Nov 23 05:05:18 localhost.localdomain info postgres[28701]: [1-1] LOG: ending log output to stderr Nov 23 05:05:18 localhost.localdomain info postgres[28701]: [1-2] HINT: Future log output will go to log destination "syslog". Nov 23 05:05:18 localhost.localdomain info postgres[28782]: [2-1] LOG: database system was shut down at 2023-11-23 05:05:17 PST Nov 23 05:05:18 localhost.localdomain err postgres[28783]: [2-1] FATAL: the database system is starting up Nov 23 05:05:18 localhost.localdomain info postgres[28701]: [2-1] LOG: database system is ready to accept connections Nov 23 05:05:18 localhost.localdomain info postgres[28787]: [2-1] LOG: autovacuum launcher started Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28801]: Invoked as: /usr/bin/mprov.pl (pid=28790) --file /var/run/config/.mprov.temp --quiet --list Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Fetching TMM count.' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Number of TMMs = 4' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Fetching TMM thread count.' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Number of TMM threads = 4' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Processing lvm test' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'lvm test complete' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'getDiskMiB_Available: 19833' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'getDiskMiB_Potential: 21075' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'There are NO extra disks.' Nov 23 05:05:19 localhost.localdomain warning mprov:28790:[28790]: 'Disk limit exceeded. 24238 MB are required to provision these modules, but only 19833 MB are available.- will mark potential space as free and retry..' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Changing available disk space from 19833 to 21075' Nov 23 05:05:19 localhost.localdomain err mprov:28790:[28790]: 'Disk limit exceeded. 24238 MB are required to provision these modules, but only 21075 MB are available.' Nov 23 05:05:19 localhost.localdomain info mprov:28790:[28790]: 'Provisioning (validation) failed.' Nov 23 05:05:19 localhost.localdomain err mcpd[4601]: 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. 24238 MB are required to provision these modules, but only 21075 MB are available.' 01071008:3: Provisioning failed with error 1 - 'Disk limit exceeded. 24238 MB are required to provision these modules, but only 21075 MB are available.'
The provisioning fails due to /appdata being too small for the provided modules.
Deploy "F5 BIG-IP VE - ALL (BYOL, 1 Boot Location)" in AWS and provision several modules (for example AFM, ASM, AVR, FPS, LTM).
Due to the number of modules that need to be provisioned, expand the /appdata volume. The steps for expanding volume for /appdata are captured in this article - https://my.f5.com/manage/s/article/K14952
None