Description of problem: When you cancel installer right after start for whatever reason, or if it was hardly killed by OOM, it might happen that the satellite.yaml file will get corrupted and eventually the content might be replaced by default content set in Kafo::Configuration::DEFAULT. Version-Release number of selected component (if applicable): 6.2.7+ How reproducible: This is very tricky and the installer has to be killed when it is writing into @config_file. Actual results: File will be corrupted and the content will be replaced in next run of installer Expected results: File will be intacted Additional info: I would suggest adding some fail-safe, like transactional write with double buffer, so the original file will not be replaced/rewritten until the write to the new one will be finished. See method save_configuration(configuration) in Kafo::Configuration where the config save is implemented.
Created redmine issue http://projects.theforeman.org/issues/19096 from this bug
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
I am opting to close this, if this continues to happen through some reproducible and supported path please re-open.