Configdrive can't be bigger than 64MB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ironic-python-agent |
Triaged
|
Medium
|
Mario Villaplana |
Bug Description
When Nova generates a configdrive with the "iso9660" format (default) it doesn't contain a specific size. Only when the format is "vfat" the configdrive will be 64MB[1] and that's for legacy reasons[2].
Right now IPA is hardcoding the size of the configdrive partiton on 64MB[3] we need to make it flexible so that if a configdrive generate with the "iso9660" format is bigger than 64MB we don't break IPA.
[1] https:/
[2] http://
[3] https:/
Changed in ironic: | |
importance: | Undecided → Medium |
tags: | added: agent |
Changed in ironic: | |
status: | New → Triaged |
Changed in ironic: | |
assignee: | nobody → Mario Villaplana (mario-villaplana-j) |
affects: | ironic → ironic-python-agent |
summary: |
- IPA: Configdrive can't be bigger than 64MB + Configdrive can't be bigger than 64MB |
tags: | removed: agent |
I have a fix up in my fork that looks like it works:
https:/ /github. com/supermari0/ ironic- python- agent/commit/ bf3349f4c9a5696 a280d2665a0c573 3f1aa12f5f
It seems like depending on the hardware, though, that I sometimes get this message when creating the partition:
"Warning: The resulting partition is not properly aligned for best performance."
This happens when using a small configdrive (<1MB), when the code creates a 1 MB partition.
Any ideas for how to better calculate an optimal alignment before creating the partition? I thought partitioning in increments of 1MB would always be considered "optimal" but apparently I'm wrong.