Comment 9 for bug 1729584

Sorry I missed the patch you posted earlier until the bug update today.. I tested the patch and it fixes the situation in #2.

Confirmed @ the disk_info['mapping'] comment. None appear to have bood_index=0. We have quite a few boot from volume instances in the env, and only a few had this occur. The one in particular that I am testing with was created in Kilo timeframe. I wonder if something was not mapped quite right back then which has carried through the various upgrades. Anyway it seems like an edge case, and the patch does fix it. Thank you!