Bug 1394619

Hi Peter, --scenario=installer is not a valid combination.  Did you intend for it to be satellite or capsule?

(In reply to Brad Buckingham from comment #1)
> Hi Peter, --scenario=installer is not a valid combination.  Did you intend
> for it to be satellite or capsule?

Sorry, you're correct. I wrote the wrong thing. I meant --sceario=satellite. I'm trying to find the correct way to run the installer adding more features to the capsule/satellite without overwriting the external settings I've already done (and lost several times).

Hi Stephen, can you assist Peter? Thanks!

Can you explain the external DNS setup more? How are you configuring it and what are you configuring?

Not sure the BZ is the right place for this. But here's the background. I did a clean install of Sat 6.2. After installation I wanted DNS and DHCP to use the current DNS/DHCP so I set them up as external services, but when I added tftp using the satellite-installer --scenario=satellite it wiped (reset) my external settings. I also need to setup IPA integration which also requires running the satellite-installer and which will again wipe my external setup. 

Since I have to run the installer to do minor upgrades too, I don't want to loose my settings. Hence this BZ.

I would suspect this is more a support issue and not a bug, but I'm happy to help...  I need more details by what you mean by "set them up as external services"


Are you running bind on the satellite server or external to it?


How'd you configure the external services? Are you editing files in /etc/foreamn-proxy by hand? (You shouldn't do this, there's installer options to configure all of it)

(In reply to Stephen Benjamin from comment #6)
> I would suspect this is more a support issue and not a bug, but I'm happy to
> help...  I need more details by what you mean by "set them up as external
> services"

Pretty sure this is a bug - not a "how to use it". After running satellite-installer, the dhcp and dns foreman-proxy services are disabled. 

> 
> Are you running bind on the satellite server or external to it?

External. 

> 
> How'd you configure the external services?

Following: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-5-configuring-external-services


> Are you editing files in
> /etc/foreamn-proxy by hand? (You shouldn't do this, there's installer
> options to configure all of it)

Well, that's what the documentation tells us to do. Maybe that's the problem? What's the better way to do it?

Yes, that's the problem the documentation is incorrect.

All of the DNS settings in /etc/foreman-proxy/dns.yml and any other serivces like DHCP, etc are controllable through installer flags.  Editing it directly will wipe it out on the next installer run.


The docs say:

---
:enabled: true
:dns_provider: nsupdate
:dns_key: /etc/rndc.key
:dns_server: 192.168.38.2
:dns_ttl: 86400

But really you should use

satellite-installer --foreman-proxy-dns=true
--foreman-proxy-dns-provider=nsupdate
--foreman-proxy-dns-managed=false
--foreman-proxy-keyfile=/etc/rndc.key
--foreman-proxy-dns-ttl=86400

And this will make the changes permament.

You can see the --help for any other options you might need.

Refiling this under documentation.

Thank you for raising this bug.

Hello Stephen

Am I correct in thinking the step "Restart the proxy. " is now redundant?

IIRC, if you run the installer script I think it restarts or reloads everything so you have a running system at the end.


Thank you

(In reply to Stephen Wadeley from comment #14)
> The change I made was in:
> 
>  "Configuring Capsule Server with External DNS" [1]
> 
> 
> but now I see the same problem in:
> 
>  "Configuring Capsule Server with External DHCP" [2]
> 
> wrt the DHCP configs

My understanding and direction on this issue has been that _no_ changes should be made directly to the configuration files, but instead use the "satellite-installer" and it's options to change configuration.

If you can, add a warning that installer can overwrite lots of configuration files and it's recommended to do --dry-run first.

(In reply to Lukas Zapletal from comment #20)
> If you can, add a warning that installer can overwrite lots of configuration
> files and it's recommended to do --dry-run first.

there is also:

 Bug 1221217 - [RFE] Document installer's puppet nature and that changes would be overwritten

(In reply to Lukas Zapletal from comment #20)
> If you can, add a warning that installer can overwrite lots of configuration
> files and it's recommended to do --dry-run first.

[root@rhel7-2-sat6-1 ~]# satellite-installer --foreman-proxy-dhcp=true --dry-run
[root@rhel7-2-sat6-1 ~]# satellite-installer --help | grep dry

(In reply to Stephen Wadeley from comment #22)
> (In reply to Lukas Zapletal from comment #20)
> > If you can, add a warning that installer can overwrite lots of configuration
> > files and it's recommended to do --dry-run first.
> 
> [root@rhel7-2-sat6-1 ~]# satellite-installer --foreman-proxy-dhcp=true
> --dry-run
> [root@rhel7-2-sat6-1 ~]# satellite-installer --help | grep dry

sorry, pasted to quickly

[root@rhel7-2-sat6-1 ~]# satellite-installer --dry-run
ERROR: Unrecognised option '--dry-run'

Sorry it's

-n, --noop                    Run puppet in noop mode? (default: false)

(In reply to Lukas Zapletal from comment #25)
> Sorry it's
> 
> -n, --noop                    Run puppet in noop mode? (default: false)

See the second paragraph just published here:

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-3-installing-satellite-server#installing_satellite_connected_parent

Ok, it's always good to provide -n and -v to see the changes on the console rather than finding that in logs.

Hello


These changes are now live on the customer portal

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-5-configuring-external-services


Thank you