Case 1: Installing with outdated foreman-answers.yaml scenario leads to Broken DB, AD integration lost, all proxies are disconnected etc.
Case 2: Installing with “–dont-save-answers” leads to broken DNS/DHCP features on the smart proxy and potentially other changes are made to current setup.
Expected outcome:
Wondering how could we generate a new foreman-answers.yaml file from the current setup. Currently we need to enable httpboot without breaking the instance.
The short answer (and you won’t like it) is: you can’t. If we could generate the answers from the systems, we wouldn’t need to store them
But maybe you could (for now) get away with just doing everything manually? From your description I gather you essentially want to do foreman-installer --foreman-proxy-httpboot true, correct?
If I am not totally mistaken, the only real thing this parameter does is to edit /etc/foreman-proxy/settings.d/httpboot.yml to read:
:enabled: true
:root_dir: /var/lib/tftpboot
And then to restart the foreman-proxy service. You can try doing this yourself and see if that helps for you current issue?
Long term you’ll still need a working answers file, but at least you can get HTTPBoot working?