1aeb1308ec
convert refresh controller to asyncio apis
2019-12-11 14:40:54 +13:00
372ceed689
some helpers
2019-12-11 14:40:31 +13:00
6d514de5f8
use asyncio apis to load error reports at startup
2019-12-11 14:40:09 +13:00
f805a9d9dd
add a convenience wrapper
2019-12-11 14:39:48 +13:00
864e09cc99
use asyncio event loop and a little asyncio api
2019-12-11 14:39:25 +13:00
d6178d9095
Merge pull request #583 from mwhudson/error-report-ui-tweaks
...
small tweaks to error reporting ui
2019-12-10 11:19:38 +13:00
ed07cd9b4c
small tweaks to error reporting ui
...
* do not present other options while a report is uploading
* clarify what "try again" means when presenting a ui crash
2019-12-10 11:01:38 +13:00
8b08dd5001
Switch snaplist checkbox from () to []
...
In urwid design language () are radio buttons, and [] are checkboxes.
2019-12-06 18:33:18 +00:00
68173131f3
Merge pull request #580 from mwhudson/curtin-master-for-now
...
use curtin master as of today
2019-12-06 09:33:31 +13:00
9c0b215b31
use curtin master as of today
2019-12-06 09:32:52 +13:00
4ce4e8b48f
Merge pull request #577 from mwhudson/error-report-send-to-daisy
...
enable sending reports to daisy
2019-12-06 09:26:21 +13:00
b5ca91e7d6
support cancelling the upload
2019-11-21 14:56:31 +13:00
3ce74d146e
dig a traceback out of a curtin install failure if possible
2019-11-21 14:56:08 +13:00
9a3c524e68
submit the last ~2k of the curtin log to daisy
2019-11-21 14:55:46 +13:00
683d1932ac
have replayed curtin runs create a log file too
2019-11-21 14:55:23 +13:00
0f1f128dc8
ui for sending error reports to daisy
2019-11-21 14:55:01 +13:00
ae033101e6
code for uploading to daisy
2019-11-21 14:54:35 +13:00
e303fab383
Merge pull request #578 from mwhudson/curtin-events-fail
...
have dry-run install failures replay events from a real failure
2019-11-21 11:39:14 +13:00
e8a9cdf4f8
have dry-run install failures replay events from a real failure
2019-11-21 11:25:43 +13:00
5a72d361a7
Merge pull request #576 from mwhudson/unmount-before-probing
...
if /target exists, run curtin umount /target before first disk probe
2019-11-18 03:40:25 -08:00
ec14875a85
if /target exists, run curtin umount /target before first disk probe
...
The installer now lets you restart after an install failure, but unless
we do something like this, the target system still being mounted will
make life confusing.
It's more robust to be defensive and try to unmount at startup rather
than trying to unmount before restarting.
2019-11-18 15:35:56 +13:00
ac071ec9bf
Merge pull request #574 from mwhudson/error-report-ui
...
first cut at error report ui
2019-11-18 12:30:50 +13:00
5c509511f3
read mountinfo in one go
2019-11-18 12:30:17 +13:00
330bbeb024
Merge pull request #575 from mwhudson/no-cache-storage-probe-data
...
stop caching probed storage data
2019-11-13 10:32:02 +13:00
73b53f2bf3
stop caching probed storage data
...
A recent branch carefully called Prober.get_storage() whenever a udev
block device event was seen. But Prober.get_storage() cached the results
from probert rendering that useless. Rip the caching and some other
complexity out of the prober class.
2019-11-13 10:07:51 +13:00
b5ea14f4f1
fake persistent_details in dry-run mode
2019-11-12 11:42:28 +13:00
d550bb139d
design inspired tweaks
2019-11-12 11:33:38 +13:00
d926cc5178
show the report for an install failure when it happens
2019-11-12 11:32:50 +13:00
0affdaf046
present kind-appropriate options when an error occurs
2019-11-12 11:32:22 +13:00
3207170da5
show probe failures on reaching the filesystem screen
2019-11-12 11:31:11 +13:00
615dc1b1dd
show an unseen ui crash on startup
2019-11-08 13:36:30 +13:00
009d0598d0
update error list when report changes (esp. is viewed)
2019-11-08 13:36:30 +13:00
3221b14294
load crash reports from disk on startup
2019-11-08 13:36:30 +13:00
3837780b60
show persistent location of crash report
2019-11-08 13:36:30 +13:00
1d413b6b06
error list view
2019-11-08 13:36:30 +13:00
e93b5111b3
update error view when report is done
2019-11-08 13:36:30 +13:00
50e9dfb324
show error reports on creation (mostly)
2019-11-08 13:36:30 +13:00
6d3f014f7a
simple view of a crash report
2019-11-08 13:36:30 +13:00
a8c1be5b2c
Merge pull request #573 from mwhudson/raid-size-calculation
...
More accurate estimation of the size of a RAID
2019-11-08 10:12: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
d532648794
beef up comments
2019-11-08 09:31:49 +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
53e532e602
add a test from the only bug i can find where the size of the resulting raid is reported
2019-11-08 09:22:59 +13:00
ea9af1cbc0
More accurate estimation of the size of a RAID
...
I found the code in mdadm that decides how much of a device is usable
for data and copied it. It's a bit hairy!
For https://bugs.launchpad.net/subiquity/+bug/1816777 and many similar
bugs.
2019-11-08 09:22:59 +13:00
Michael Hudson-Doyle