3e800998 broke storage writing in two cases: regular live installs and ostree installs. The old write_storage_late check checked for flags.livecdInstall and ksdata.ostreesetup.seen as well as ksdata.method.method == "liveimg". The new check in writeStorageLate() dropped those two, only keeping the method check. The method is only 'liveimg' when doing a kickstart-driven install with the 'liveimg' parameter, which is a fairly niche case - the method is not 'liveimg' on a regular live install (it's 'harddrive').
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/209
ostree is optional and may not be included in the environment that
anaconda is running in, so only check the version if it is actually
going to be used.
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/216
3e800998 broke storage writing in two cases: regular live installs and ostree installs. The old write_storage_late check checked for flags.livecdInstall and ksdata.ostreesetup.seen as well as ksdata.method.method == "liveimg". The new check in writeStorageLate() dropped those two, only keeping the method check. The method is only 'liveimg' when doing a kickstart-driven install with the 'liveimg' parameter, which is a fairly niche case - the method is not 'liveimg' on a regular live install (it's 'harddrive').
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/209
This was left in by mistake. The whole point of the env_add parameter to
startProgram was to not have to do this.
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/202