qa - vault test failures on focal

[Adam Stokes]

Analyzer: https://jenkaas.s3.amazonaws.com/519381f1-6985-4d2a-b9cd-7637078b43d5/index.html
Crashdump: https://jenkaas.s3.amazonaws.com/519381f1-6985-4d2a-b9cd-7637078b43d5/artifacts.tar.gz

Traceback:

Traceback (most recent call last):
File "lib/charms/layer/vaultlocker.py", line 94, in encrypt_device
mkfs_xfs(mapped_device)
File "/var/lib/juju/agents/unit-kubernetes-master-0/.venv/lib/python3.8/site-packages/charmhelpers/contrib/storage/linux/utils.py", line 128, in mkfs_xfs
check_call(cmd)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-kubernetes-master-0/charm/reactive/kubernetes_master.py", line 2631, in create_secure_storage
vaultlocker.create_encrypted_loop_mount(encryption_conf_dir)
File "lib/charms/layer/vaultlocker.py", line 177, in create_encrypted_loop_mount
encrypt_device(device_name, str(mount_path), uuid)
File "lib/charms/layer/vaultlocker.py", line 108, in encrypt_device
raise VaultLockerError('Error configuring VaultLocker') from e

[Cory Johns (johnsca)]

Actual error from mkfs.xfs is: agsize (1024 blocks) too small, need at least 4096 blocks

I think this minimum size depends on the physical block size of the device, so it may vary by deployment which is perhaps why we haven't hit this before. The size is configurable, but the helper function doesn't capture or surface the error message so we can't detect if the problem is with the size, and there's no way currently for the user to change the size.

[Joseph Borg (joeborg)]

Fix https://github.com/charmed-kubernetes/layer-vaultlocker/pull/1

[Cory Johns (johnsca)]

Cherry-pick to stable: https://github.com/charmed-kubernetes/layer-vaultlocker/commit/42dbb6a22be7e066b46aedf47fcefe80d6a0f34f