Merge lp:~smoser/curtin/trunk.run-in-chroot-revival into lp:~curtin-dev/curtin/trunk
Proposed by
Scott Moser
Status: | Merged |
---|---|
Merged at revision: | 422 |
Proposed branch: | lp:~smoser/curtin/trunk.run-in-chroot-revival |
Merge into: | lp:~curtin-dev/curtin/trunk |
Diff against target: |
65 lines (+41/-0) 2 files modified
curtin/util.py (+10/-0) tests/unittests/test_util.py (+31/-0) |
To merge this branch: | bzr merge lp:~smoser/curtin/trunk.run-in-chroot-revival |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ryan Harper (community) | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Review via email: mp+304271@code.launchpad.net |
Commit message
add support for RunInChroot in curtin.util
In my merge committed to trunk in revno 404, we dropped 'RunInChroot'.
That method was being used from curthooks in maas-images project to
make a chrootable target. In order to support installation of old images
that depend on RunInChroot we need to add the method back.
This does that by just utilizing ChrootableTarget. It also adds
a couple unit tests to ensure that this keeps working.
To post a comment you must log in.
PASSED: Continuous integration, rev:422 /jenkins. ubuntu. com/server/ job/curtin- ci/254/ /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= amd64/254 /jenkins. ubuntu. com/server/ job/curtin- ci/nodes= ppc64el/ 254
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/curtin- ci/254/ rebuild
https:/