Openshift 3.1 provider appears to be broken

Developers
#1

Seem to be still experiencing the issues discussed in https://github.com/openshift/origin/issues/5973.

Hoping someone can help with a work around?

Methods to reproduce

  1. Install OpenShift Origin v3.1 using byo playbook
  2. Deploy ManageIQ Capablanca (capablanca-1.20160209142121_d9bbf5f)
  3. Configure Kubenetes service account
  1. Ensure additional permissions have been applied as per previous issue. https://github.com/openshift/origin/issues/5973

ERROR

[KubeException]: User "system:serviceaccount:management-infra:management-admin" cannot list all componentstatuses in the cluster  Method:[rescue in block in refresh]

Software Versions

  • origin-sdn-ovs-1.1.1.1-0.git.0.ce0e67f.el7.centos.x86_64
  • origin-node-1.1.1.1-0.git.0.ce0e67f.el7.centos.x86_64-
  • origin-master-1.1.1.1-0.git.0.ce0e67f.el7.centos.x86_64
  • origin-clients-1.1.1.1-0.git.0.ce0e67f.el7.centos.x86_64
  • origin-1.1.1.1-0.git.0.ce0e67f.el7.centos.x86_64

Related

#2

Hi @seasonal_coder the issue that you’re seeing is not related to https://github.com/openshift/origin/issues/5973

The issue is https://github.com/openshift/origin/issues/5865 which is closed but not resolved, because it has been moved to https://github.com/openshift/origin/issues/3667

Those are error messages reporting that OpenShift has still not addressed the component statuses issue but anyway they’re not affecting the inventory collection (which completes successfully anyway).