73e9c5c27e
This has not been hit for a year (on stg; three years on prod). I *think* it would only be hit if we ran the test on an Everything image, but as the test is now specifically associated with the Server install DVD, that doesn't seem likely to happen. If we somehow *do* hit ext4 pre-selected again, this can still be handled simply by adding an alternate anaconda_blivet_part_fs_ext4 needle which matches on ext4 already being selected; that avoids the need to keep an alternate code path around. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
|---|---|---|
| .. | ||
| help | ||
| identification | ||
| install_destination | ||
| install_process | ||
| install_source | ||
| lang_select | ||
| main_hub | ||
| network | ||
| package_selection | ||
| partitioning | ||
| universal | ||
| vnc | ||
| initialsetup_finish_configuration-20200116.json | ||
| initialsetup_finish_configuration-20200116.png | ||
