Merge lp:~rodsmith/maas-cert-server/fix-zesty-deploy into lp:~hardware-certification/maas-cert-server/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Jeff Lane | ||||
Approved revision: | 74 | ||||
Merged at revision: | 74 | ||||
Proposed branch: | lp:~rodsmith/maas-cert-server/fix-zesty-deploy | ||||
Merge into: | lp:~hardware-certification/maas-cert-server/trunk | ||||
Diff against target: |
59 lines (+12/-4) 3 files modified
debian/changelog (+6/-0) preseed/curtin_userdata_cert (+3/-2) preseed/curtin_userdata_custom_cert (+3/-2) |
||||
To merge this branch: | bzr merge lp:~rodsmith/maas-cert-server/fix-zesty-deploy | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeff Lane | Approve | ||
Review via email: mp+321917@code.launchpad.net |
Description of the change
This MR fixes bug #1679758, which was blocking deployment of Ubuntu 17.04 zesty beta on MAAS when our custom preseeds were in use. There were two issues:
1) Under zesty, installing canonical-
the installation of mailutils, which in turn causes postfix to
be installed. Unfortunately, postfix requires interaction during
installation, so everything falls apart. Explicitly installing
sendmail along with canonical-
postfix to not be installed, thus working around this issue.
2) The "secureid" mini-script in the preseed was causing something
in /dev to remain open, thus preventing it from being
unmounted at the end of the installation, and the install
would then fail. Adding "sleep 5;" to the end of the
"secureid" mini-script seems to fix this problem.
I've applied these fixes to both the standard and custom preseeds and tested with both, although we probably won't be using custom images with zesty or later.
Please file a checkbox bug (probably plainbox- provider- checkbox) for this. Ultimately, something should not be installing postfix, but is... so that should be investigated upstream as well.
Otherwise, approve