You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 hostnamecentos7-katello-devel-stable.example.com
when you specifyserver: 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.The text was updated successfully, but these errors were encountered: