"RestClient.get “https://registry.example.com:9090/pulp/api/v2/repositories/”
I have a forklift devel and separate smart-proxy up and running. The above URL 404s on the smart-proxy UI page. The status URL 200s fine.
Also of note that the dir /var/lib/pulp/content was not created at install so I manually created that per advice on IRC.
Any suggestions of where I should look for fix to this?
Any thoughts here appreciated. Below are my box definitions, devel and
registry.
Should server be trying to communicate with smart-proxy pulp on port :9090?
Wondering which side to look on for the problem, the server or smart-proxy.
devel:
primary: true
box: centos7
ansible:
group: ‘devel’
variables:
ssh_forward_agent: true
katello_devel_github_username: “thomasmckay”
#foreman_installer_options: “–foreman-proxy-tftp=true”
#foreman_installer_module_prs: “katello/katello/189”
#katello_repositories_environment: staging
foreman_installer_options: “–skip-puppet-version-check”
playbook:
- ‘playbooks/devel.yml’
- ‘user_playbooks/setup.yml’
- ‘user_playbooks/setup_devel.yml’
memory: 8192
cpus: 2
disk_size: 80
sshfs:
host_path: ‘/home/thomasmckay/code’
guest_path: ‘/home/vagrant/code’
options: ‘-o allow_other’
domain: example.com
networks:
- type: ‘private_network’
options:
ip: 192.168.123.230
libvirt__network_name: example-com
registry:
box: centos7
ansible:
playbook:
- ‘playbooks/foreman_proxy_content_dev.yml’
- ‘user_playbooks/setup.yml’
group: ‘foreman-proxy-content’
server: ‘devel’
domain: example.com
networks:
- type: ‘private_network’
options:
ip: 192.168.123.231
libvirt__network_name: example-com