Comment 5 for bug 1543233

fuel-agent raised an exception regarding Invalid Boundaries due to partition' boundaries alignment done by parted.

Under certain circumstances due to that alignment, the end of particular partition could cross 1M boundary. And due to actual partition' bounderies being rounded up, fuel-agent mistakenly assumes that partition couldn't fit within provided boundaries and raises errors.WrongPartitionSchemeError.

In addition to that, parted always creates a relatively huge 1.5M gap prior the first partition on this particular combination of h/w (HP Gen9 and raid). However, it looks unrelated to the original issue, unless one will care that first partition becomes 2M smaller than expected.

In order to mitigate aligning related issue, i proposed to add 1M room between partitions. I will test it against h/w and will post the result here.

Bad news is the issue with partition alignment is floating around and only occurs under very specific conditions. It looks like it depends only generated partitioning layout. Provided snapshot indicates that few nodes were provisioned smooth and without errors.

Probably, the change is too high to reproduce the issue under every version of fuel. As only partitioning layout matters. I think it's critical and we need to fix it ASAP and arrange backported fixes for updates for all supported version of fuel.