ef78e7d01c
re-run snap-preseed in inject-subiquity-snap.sh
2021-01-06 14:04:50 +13:00
7381df63d5
Merge pull request #859 from mwhudson/lp-1896497
...
use -report_el_torito as_mkisofs option of xorriso to find command to repack ISO
2020-11-04 15:30:26 +13:00
449ad839aa
update integration tests
2020-11-04 10:57:22 +13:00
d7a070962b
fix shell quoting
2020-11-04 09:30:52 +13:00
8987ab792c
use -report_el_torito as_mkisofs option of xorriso to find command to repack ISO
2020-10-28 16:32:24 +13:00
8cfa8c64d4
scripts/test-this-branch.sh: install needed dependencies
2020-08-22 14:11:52 -03:00
dca298a815
inject-subiquity-snap: recalculate MD5 for installer.squashfs
...
The inject-subiquity-snap.sh script rebuilds the installer.squashfs filesystem, but does not recalculate its MD5 hash.
This leads to an error message during bootup process, complaining about one of the files being damaged, that file
being installer.squashfs.
This commit introduces an extra step to recalculate the MD5 hash of the installer.squashfs and write it into
md5sum.txt, as well as to remove the GPG signature of the installer filesystem, since it's invalid anyway.
2020-08-02 18:05:34 +02:00
d9cea264f1
clean up the xorriso arguments in inject-subiquity-snap a bit
2020-07-22 15:06:29 +12:00
bbfcdd7b25
sort installer cloud config after 90_dpkg.cfg
2020-06-16 13:55:30 +12:00
2ddde49a43
use the "None" datasource for on-first-boot configuration
...
Using the NoCloud source meant that a filesystem label of "cidata"
(probably containing autoinstall config) could override the cloud-init
nocloud seed subiquity wrote and then users would not get created. So
instead write cloud config directly that hardcodes using the
DataSourceNone source and config for it.
https://bugs.launchpad.net/subiquity/+bug/1879103
2020-06-15 15:07:03 +12:00
99ad097306
snapcraft.yaml fixery
2020-05-21 11:54:49 +12:00
a6d98f29e6
change languagelist format a bit, add some special cases
2020-05-21 11:54:49 +12:00
5cb37acefc
make some language lists at snap build time
2020-05-21 11:54:49 +12:00
3c98f68fcf
use a real locale in examples/autoinstall.yaml
2020-05-21 10:49:42 +12:00
2e85a2ecd6
i18n: add scripts to help with translation updates.
...
Signed-off-by: Dimitri John Ledkov <xnox@ubuntu.com>
2020-05-06 13:22:13 +01:00
ba106bbbed
tests
2020-05-05 23:05:59 +12:00
f814d9514f
use more general context machinery to feed install events to progress view
2020-05-04 19:05:42 +12:00
4564871ad2
fix tests
2020-05-04 15:28:42 +12:00
8a84e470c5
make sure the size of a partition gets set to int
2020-05-04 14:16:03 +12:00
f8eef1d16a
fix Subiquity.restart dry-run path now we actually hit that in runtests.sh
2020-04-29 19:46:17 +12:00
05ca96d7ba
run netplan generate --root .subiquity after each integration test
2020-04-29 19:39:10 +12:00
670c9c838a
add test for locale: in autoinstall file
2020-04-20 20:34:08 +12:00
18e4d977e9
fix autoinstall refresh code to (a) match docs (b) work
2020-04-19 22:48:27 +12:00
e91f8bbf89
fix for omitting identity section when passing user-data
2020-04-19 21:44:09 +12:00
e3ec05a6c1
always include partition number in curtin config
2020-04-14 10:21:29 +12:00
96a6dfd010
add integration-style test for reusing an existing partitions
2020-04-14 09:50:56 +12:00
be146972da
fix travis
2020-04-07 21:37:42 +12:00
b0302484d2
fix tty check for autoinstalls
2020-04-07 20:34:38 +12:00
467257ff9a
hack for testing in lxd
2020-04-02 11:11:25 +13:00
9a68ce91c1
fix not supplying snaps in autoinstall, oops
2020-04-02 10:47:47 +13:00
c1c33dee03
add a simple integration test for autoinstall
2020-04-02 10:22:08 +13:00
897fe56213
Try overriding zfs-mount.service
2020-03-05 16:53:35 +00:00
cbaab430a3
Switch script to use python3, as python is no longer available
...
I guess good luck to the Jenkins CI?
2020-01-29 18:00:54 +00:00
683d1932ac
have replayed curtin runs create a log file too
2019-11-21 14:55:23 +13:00
ae033101e6
code for uploading to daisy
2019-11-21 14:54:35 +13:00
e8a9cdf4f8
have dry-run install failures replay events from a real failure
2019-11-21 11:25:43 +13:00
0141defa01
changes suggested in review
2019-11-08 09:47:34 +13:00
65a961be1a
do not run the 100T raid tests, mdadm fails with SIGPIPE
2019-11-08 09:31:51 +13:00
5d8c983448
make raid-size-tests.py a tiny bit friendlier
2019-11-08 09:31:51 +13:00
fde1c53141
sort raid devices consistently when computing size and when serializing
2019-11-08 09:30:22 +13:00
233965b376
fix raid size calculation when sizes of devices in array vary
...
It turns out mdadm computes the headroom based on the first device in
the array, which means that the order of the devices matters!
2019-11-08 09:22:59 +13:00
6b5e7adcf6
add some explanation to raid-size-tests.py
2019-11-08 09:22:59 +13:00
5da663fede
raid-size-tests.py: run in tmpfs, clean up better
...
ext4 limits files to a measly 16TiB!
2019-11-08 09:22:59 +13:00
679b611077
add tests of get_raid_size against reality
2019-11-08 09:22:59 +13:00
ca02972195
add a controlled way to make various things fail
...
In dry-run mode, treat SUBIQUITY_DEBUG as a comma-separated list of
things to fail:
* install-fail: curtin install fails
* copy-logs-fail: the postinstall copying of logs fails
* bpfail-full: full block device probing fails
* bpfail-restricted: restricted block device probing fails
In addition, control-u makes the UI crash in dry-run mode.
(This is all for testing of crash report generation but does not depend
on that).
2019-11-04 10:43:29 +13:00
0501a1d33b
inject-subiquity-snap: fix the ppc64 edge iso volume name
2019-10-08 11:29:31 +02:00
627ecadf6b
inject-subiquity-snap: add support for ppc64 iso images
2019-10-08 10:37:12 +02:00
fb6ea590a5
still create a subiquity-debug.log symlink
2019-09-30 16:21:42 +13:00
7c1154b758
create one log file per invocation
...
Log to subiquity-debug.log.$PID instead of just subiquity-debug.log.
When we implement error reports we'll obviously attach the log to the
error report. There's no point adding log messages from previous runs of
subiquity.
2019-09-30 13:47:56 +13:00
a23c554af3
test-this-branch.sh: fix the ISO file name
2019-08-22 14:41:38 +02:00
Michael Hudson-Doyle