I've tried with another computer on another MAAS 2.0 server. What I discovered:
- The node was already deployed and running when I started. It had the
"ubuntu" entry set as the default in "efibootmgr" output, suggesting
that when it was last deployed (about a month ago?), the bug existed.
- I redeployed, and it worked as expected.
It's starting to look as if either the bug may have existed for a while but been corrected recently or it's rather inconsistent in the conditions that cause it to appear.
Some more information:
I've tried with another computer on another MAAS 2.0 server. What I discovered:
- The node was already deployed and running when I started. It had the
"ubuntu" entry set as the default in "efibootmgr" output, suggesting
that when it was last deployed (about a month ago?), the bug existed.
- I redeployed, and it worked as expected.
It's starting to look as if either the bug may have existed for a while but been corrected recently or it's rather inconsistent in the conditions that cause it to appear.