b6c263a5dc
When an underlying block device (or driver) only supports 4KB IO, this can cause some issues with aspects like using an ISO9660 filesystem which can only support a maximum of 2KB IO. The agent will now attempt to mount the filesystem *before* deleting the supplied file, and should that fail it will mount the configuration drive file from the ramdisk utilizing a loopback, and then extract the contents of the ramdisk into a newly created VFAT filesystem which supports 4KB block IO. Closes-Bug: #2028002 Change-Id: I336acb8e8eb5a02dde2f5e24c258e23797d200ee
13 lines
634 B
YAML
13 lines
634 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes a failure case where a deployed instance may be unable to access
|
|
the configuration drive post-deployment. This can occur when block
|
|
devices only support 4KB IO interactions. When 4KB block IO sizes
|
|
are in use, the ISO9660 filesystem driver in Linux cannot be used
|
|
as it is modeled around a 2KB block. We now attempt to verify, and
|
|
rebuild the configuration drive on a FAT filesystem when we cannot
|
|
mount the supplied configuration drive. Operators can force the agent
|
|
to write configuration drives using the FAT filesystem using the
|
|
``[DEFAULT]config_drive_rebuild`` option.
|