Comment 11 for bug 1302158

I meant to comment on the status earlier, apologies for my delay. The bug has resolved itself on my end, as I expected. There seems to be a lag between the final release and updated pxe files that causes it. I'm not positive. I think if it does resurface it will be short lived and only during new releases (when you're deploying a new release).

I'll be waiting longer in the future before testing maas with newest releases. Hope this helps someone else who observes this. Note this is different than what Guy outlined above.