Merge lp:~nuclearbob/utah/desktop-resolvconf into lp:utah
Status: | Merged |
---|---|
Approved by: | Javier Collado |
Approved revision: | 771 |
Merged at revision: | 770 |
Proposed branch: | lp:~nuclearbob/utah/desktop-resolvconf |
Merge into: | lp:utah |
Diff against target: |
121 lines (+13/-13) 3 files modified
utah/provisioning/baremetal/bamboofeeder.py (+5/-6) utah/provisioning/baremetal/cobbler.py (+4/-4) utah/provisioning/provisioning.py (+4/-3) |
To merge this branch: | bzr merge lp:~nuclearbob/utah/desktop-resolvconf |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Dimitri John Ledkov (community) | Disapprove | ||
Javier Collado (community) | Approve | ||
Review via email:
|
Description of the change
This change makes all desktop installs copy resolv.conf from the installer environment into the target environment before running chroot commands. We've been doing this for a while on physical machine installs, and it works well to allow package installation to take place as part of the latecommand.
Unfortunately, that is not the only problem with the current code. Now that we have a utah-common package, the client installation fails since we don't install that as well. I'll be submitting a separate proposal for that shortly. We could test them together, but even in the absence of that fix, this one should get ssh installed and fail on client installation, unlike the current code on virtual machine desktop installs, which fails to connect to the machine after it reboots following the install.
I've tested the code and it works fine. Anyway, I've got a couple of questions:
Could the `/etc/resolv.conf` file in the host machine be broken in some way
that it's unusable in the guest machine?
Should we remove the lines that append `apt-get install` commands to
`/etc/rc.local`?