If this problem still exists when upgrading from 3.4 to 3.5 or 3.5 to 3.6 the workaround is to manually disable the excluders prior to running the upgrade. atomic-openshift-docker-excluder unexclude