Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Centos7-katello-devel-stable won't work with centos7-proxy-devel box #1101

Open
johnpmitsch opened this issue Jan 23, 2020 · 0 comments
Open

Comments

@johnpmitsch
Copy link
Contributor

johnpmitsch commented Jan 23, 2020

When spinning up an external foreman proxy, it takes a "server" variable and that is a short hostname which appends on your hypervisor domain namespace.

The stable katello box is pre-installed with katello and then published as a vagrant box. So the hostname is already set and does not use any information from the forklift user's hypervisor. This means that the server hostname on the foreman-proxy box is not set correctly with the stable box.

As an example, the foreman proxy looks for centos7-katello-devel-stable.jomitsch.example.com instead of the actual stable box's hostname centos7-katello-devel-stable.example.com when you specify server: centos7-katello-devel-stable in the ansible variables for the proxy box.

This means that communication between the external foreman-proxy and the stable katello box can not happen at spin-up time

A potential workaround is update /etc/hosts with centos7-katello-devel-stable.example.com, though I haven't tried it personally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant