Last Modified: Oct 24, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: May 26, 2017
Related AskF5 Article: K27056204
cpcfg fails with errors similar to the following: info: Getting configuration from HD1.3 info: Copying configuration to HD1.1 info: Applying configuration to HD1.1 error: status 256 returned by command: F5_INSTALL_MODE=install F5_INSTALL_SESSION_TYPE=hotfix chroot /mnt/tm_install/23102.e3MAZU /usr/local/bin/im -force /var/local/ucs/config.ucs info: >++++ result: info: Extracting manifest: /var/local/ucs/config.ucs info: /shared: Not enough free space info: 6144 bytes required info: 0 bytes available info: /var/local/ucs/config.ucs: Not enough free disk space to install! info: Operation aborted.
You cannot use cpcfg on a chassis platform.
Only on a chassis platform running 12.1.x or 13.0.x.
Save a UCS from the source volume, reboot to the destination volume, then load that UCS file.
cpcfg could incorrectly calculate the amount of free space available, refusing to do the copy unless the /shared filesystem had sufficient space to do the copy. This has been resolved and this free space calculation is done correctly.