Hmm, I'm having some problem following quite how that change to uUyuni-configure.py is effecting that cloning though I'll assume it is somehow. But then how does the client register through the proxy and know to use the proxy instead of the main server? Doesn't something need to change in the bootstrap script(s) so the client is aware of the proxy? Is that done by changing the HOSTNAME variable in the script from the Uyuni server to the Uyuni proxy? Or is it done by the settings in client-config-overrides.txt, or both? And if it's done by the latter, what should those changes look like? Because those settings seem to be good for httpProxy but do seem like they would work for http/https, but would they work for the salt minion proxy as well?
-----Original Message----- From: Cedric Bosdonnat email@example.com Sent: Tuesday, July 5, 2022 11:12 PM To: firstname.lastname@example.org Cc: Paul-Andre Panon email@example.com Subject: Re: Where is mgr-bootstrap on a containerized proxy?
There will be no mgr-bootstrap for containerized proxy and for now the bootstrap scritps are failing with it. A fix is to mirror all of the /pub folder on the proxy for containers. There is a PR for it that I tested locally:
I'll need to create some test images for Uyuni for you to test it, unless you build the images yourself ;)
Kind regards -- Cédric
On Wed, 2022-07-06 at 02:13 +0000, Paul-Andre Panon via Uyuni Users wrote:
After some brow sweat figuring out that a firewalld IP range overlap between zone sources was breaking routing for a containerized proxy, I'm ready to try to follow up with setting up some bootstrap scripts on the proxy. However I can't seem to find mgr-bootstrap to do so because it doesn't appear to be in the container host path. How does one generate bootstrap scripts on a containerized proxy?