Concerning file ownership, my comment was intended to refer to the possibility of putting the files in our package under /etc/maas/preseeds/curtin_userdata (etc.). Keeping them where they've traditionally been in our package and then copying and modifying them via a post-install script avoids the problem of conflicting package "ownership" of the files.
Your patch seems to have worked around the remaining two issues -- maybe they weren't as deep as I'd originally thought, or maybe you're just brilliant, Jeff. ;-) Still, we may need to be alert to possible new problems, should a corner case crop up that's not been tested.
Also, and more importantly, I think we'll still need some ongoing maintenance and updates to the maniacs-setup script and to the maas-cert-server package that may interact with this issue, as noted in my earlier reply.
Concerning file ownership, my comment was intended to refer to the possibility of putting the files in our package under /etc/maas/ preseeds/ curtin_ userdata (etc.). Keeping them where they've traditionally been in our package and then copying and modifying them via a post-install script avoids the problem of conflicting package "ownership" of the files.
Your patch seems to have worked around the remaining two issues -- maybe they weren't as deep as I'd originally thought, or maybe you're just brilliant, Jeff. ;-) Still, we may need to be alert to possible new problems, should a corner case crop up that's not been tested.
Also, and more importantly, I think we'll still need some ongoing maintenance and updates to the maniacs-setup script and to the maas-cert-server package that may interact with this issue, as noted in my earlier reply.