crio is running on this node and is having issues.  There are stack traces in the journal.  I extracted the last 24hrs of journal from the node for debugging:

http://file.rdu.redhat.com/sjenning/bz1505354-node.log

Routing to Containers for further investigation.

Created attachment 1342360 [details]
CRIO Journal log

I have opened https://github.com/kubernetes-incubator/cri-o/pull/1053 which should be tested to see if it fixes the godbus panic.

The updated godbus library does seem to fix the panic.

This is fixed in cri-o 1.0.1

Checked with:
# openshift version 
openshift v3.7.0-0.188.0
kubernetes v1.7.6+a08f5eeb62
etcd 3.2.8

crio version 1.0.2
commit: "29077fa6fbd85f0ca9c453ab1bf1ff7b02bc3f5c"

And can not reproduce this issue. So verify this.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:3188