Problem:
system lcsm has foreman 3.2 running on it
there are several foreman proxies running in various environments handling requests to it from clients
My understanding is that lscm upgrade 3.2-3.11 has to be done in steps 3.2->3.3, 3.3->3.4, 3.4->3.5 and so on one level at a time until 3.11 is reached.
Upgrading and Updating Foreman
-
do the proxies have to up be updated similarly at each stage, or can they be done after lcsm has reached 3.11 ie will 3.2 proxy communicate/work with 3.11 ?
-
alternatively does a proxy of 3.11 communicate with a server at 3.2 ? ie do the upgrades the otherw ay around?
-
do the clients need their foreman clients updating similarly at each stage, or can they done after lcsm has been upgraded to 3.11 and after their proxy servers have all been upgraded to 3.11 ?
(TBH Im assumoin and saw clients hinted at elsewhere - Ive been dumped with all of this when somebody left without documenting much at all) -
of can the clienmts be upgraded to 3.11 and still work with foreman proxies/servers at lower levels ?
-
and im really sorry to ask such a dumb qustion. Where are the use of foreman-proxies defined/configured on a client? Because all the baseurls on all clients - including thus the ones that allegedly use a foreman-proxy - are for the main server itself.
Basically it is trivial for me to clone lcsm to eg lcsm2 (different IP), upgrade lcsm2 and eventually flip lcsm2 to be lcsm (turn off lcsm, rebame lcsm2 and change IP) but that isnt really feasible for 5 foreman proxies and multiple clients
Expected outcome:
a smooth and easy transition process.
Foreman and Proxy versions:
all 3.2 currently
Foreman and Proxy plugin versions:
dont understand what this means - sorry (see above caveat)
Distribution and version:
dont understand what this means - sorry (see above caveat)
Other relevant data:
None known/appreciated
didds