Problem:
I just installed a fresh Katello 4/Foreman 2.4 and after adding my company certificate and restarting Pulp will no longer start?
# pulp status
Error: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /pulp/api/v3/docs/api.json (Caused by SSLError(CertificateError("hostname 'localhost' doesn't match either of '*.services.com', 'services.com'",),))
Expected outcome:
Pulp starts.
Foreman and Proxy versions:
Foerman 2.4.0 and Katello 4.0
Foreman and Proxy plugin versions:
Openscap, Dynflow, Ansible, SSH, Pulpcore, TFTP, Puppet CA, Puppet, BMC, Logs, and Registration 2.4.0
Distribution and version:
Centos 7.9
Other relevant data:
This is a brand new installation
# systemctl status -l pulpcore-resource-manager.service
● pulpcore-resource-manager.service - Pulp Resource Manager
Loaded: loaded (/etc/systemd/system/pulpcore-resource-manager.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2021-05-20 11:22:33 CEST; 2s ago
Process: 12258 ExecStart=/usr/libexec/pulpcore/rq worker -w pulpcore.tasking.worker.PulpWorker -n resource-manager -c pulpcore.rqconfig --disable-job-desc-logging (code=exited, status=1/FAILURE)
Main PID: 12258 (code=exited, status=1/FAILURE)
Tasks: 0
CGroup: /system.slice/pulpcore-resource-manager.service
May 20 11:22:33 foreman.cloudboxservices.com systemd[1]: Unit pulpcore-resource-manager.service entered failed state.
May 20 11:22:33 foreman.cloudboxservices.com systemd[1]: pulpcore-resource-manager.service failed.
hammer ping just seemed to hang so I have just started a rebuild from my Ansible playbook to try to recreate the VM from scratch which will take approx 1 hour. I will try your suggestions then.
The strange part is that I built another VM using the playbook and that one is fine. The only change I made since then was to swap out the cockpit self-signed cert for the wildcard one.