Merge lp:~smoser/maas-images/trunk.precise-squashfs into lp:maas-images
Proposed by
Scott Moser
Status: | Merged |
---|---|
Merged at revision: | 390 |
Proposed branch: | lp:~smoser/maas-images/trunk.precise-squashfs |
Merge into: | lp:maas-images |
Diff against target: |
12 lines (+1/-1) 1 file modified
meph2/stream.py (+1/-1) |
To merge this branch: | bzr merge lp:~smoser/maas-images/trunk.precise-squashfs |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andres Rodriguez (community) | Approve | ||
Lee Trager (community) | Approve | ||
Review via email: mp+337011@code.launchpad.net |
Description of the change
Always create squashfs image if configured.
For precise in the v3 stream there was no 'squashfs' image created.
This was enabled only if input to the build was '.tar.gz' or 'squashfs'.
As we need a squashfs image for installing precise with maas 2.3+,
we modify the code here to build that image.
Note that this squashfs image is known to not boot with rooturl
as the other squashfs images produced do.
To post a comment you must log in.
I've tested that it builds the squashfs image by: conf/meph- v3.yaml amd64 precise \ server- cloudimg- amd64-root. tar.xz \ output. d/
meph2-build -vv --config=
20180201 precise-
precise-
The squashfs image will be generated in another way:
using 'img2squashfs' from the last built image
Thus, *This change is not strictly necessary*.
However, it is good to have the maas-images code correctly
building the output if we ever needed to do that again.