Write the description below
After fixing the puppet runs on the acme-chief VMs inside cloud vps, it seems that the service keyholder-proxy fails to start:
dcaro@paws-acme-chief-01:~$ sudo run-puppet-agent Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Info: Caching catalog for paws-acme-chief-01.paws.eqiad.wmflabs Info: Applying configuration version '(6a09b15c8b) David Caro - openstack::...vms::common: Use ensure_packages' Notice: The LDAP client stack for this host is: sssd/sudo Notice: /Stage[main]/Profile::Ldap::Client::Labs/Notify[LDAP client stack]/message: defined 'message' as 'The LDAP client stack for this host is: sssd/sudo' Notice: /Stage[main]/Keyholder/Systemd::Service[keyholder-proxy]/Service[keyholder-proxy]/ensure: ensure changed 'stopped' to 'running' (corrective) Info: /Stage[main]/Keyholder/Systemd::Service[keyholder-proxy]/Service[keyholder-proxy]: Unscheduling refresh on Service[keyholder-proxy] Notice: Applied catalog in 8.98 seconds