Adam Williamson 186678e98b Make log upload work when installed system hits emergency mode ... Summary: This is to handle cases like #1414904 , where the system boots to emergency mode. We really need logs to try and debug this. Test Plan: Force a test to hit emergency mode somehow (right now you can just run base_services_start on Rawhide over and over until you hit #1414904, but there's probably an easier way to do it, I think there's a systemd boot arg to tell it which target to boot for e.g.) and check logs get uploaded. Also check this doesn't break log upload for a 'normal' failure. Reviewers: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Reviewed By: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1103		2017-02-01 12:30:21 +01:00
..
anaconda.pm	Move all remaining utility functions into exporter modules	2017-01-17 23:15:44 -08:00
anacondatest.pm	Move all remaining utility functions into exporter modules	2017-01-17 23:15:44 -08:00
fedoradistribution.pm	drop our implementation of script_run in favour of os-autoinst	2016-10-20 09:24:48 -07:00
freeipa.pm	Move all remaining utility functions into exporter modules	2017-01-17 23:15:44 -08:00
installedtest.pm	Make log upload work when installed system hits emergency mode	2017-02-01 12:30:21 +01:00
packagetest.pm	drop our implementation of script_run in favour of os-autoinst	2016-10-20 09:24:48 -07:00
tapnet.pm	Move all remaining utility functions into exporter modules	2017-01-17 23:15:44 -08:00
utils.pm	Fix check_release, menu_launch_type, start_cockpit	2017-01-26 14:32:42 +01:00