Comment 6 for bug 1773445

So, i digg into this, and here's what i found:

The problem is indeed with dbus upgrade from 7.4 to 7.5, and the official response to fix the problem is: reboot the system, because nobody would make a live upgrade in production.
The workaround I found is restart dbus before certmonger service start. Also, notice there are several other services that fails, we just notice this in certmonger (dnsmasq also has the same problem).
I submit a PR to certmonger puppet module [1] since it's not part of openstack module.

IF the PR is approved, then we need to pin the puppet-certmonger rpm package to point to the new commit in rdo. According jpena that will not be a problem.