Description of problem: Create serviceinstance via YAML will make overview page go wrong Version-Release number of selected component (if applicable): v3.9.0-0.15.0 How reproducible: Always Steps to Reproduce: 1. Create **empty** project 2. create serviceinstance by 'Import YAML/JSON', could use this yaml file: https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/svc-catalog/serviceinstance-template.yaml (change the param INSTANCE_NAMESPACE to your project name) 3. check overview page and provisioned service page Actual results: 3. overview page only show "The filter is hiding all resources. Clear Filter" provisioned service page will see the created serviceinstance Expected results: 3 Should also see the serviceinstance on overview page Additional info:
I've fixed one problem in this PR: https://github.com/openshift/origin-web-console/pull/2635 The instances were not showing up correctly when the corresponding service class did not exist. But the symptoms I saw were a little different: I didn't get the filter hiding everything message, but the normal empty state message. In your environment, do you have the ansible service broker installed with this service class and service plan?
Commits pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/f913823d4668ef3fc9e82f8c17ca5f7701c31777 Bug 1532182 - Handle missing service class for instance Avoid display problems on the overview when a service instance references a non-existent service class or service plan. https://github.com/openshift/origin-web-console/commit/733c230fde5b23e43e9235b579385e5157799cd2 Merge pull request #2635 from spadgett/missing-service-class Automatic merge from submit-queue. Bug 1532182 - Handle missing service class for instance Avoid display problems on the overview when a service instance references a non-existent service class or service plan. /kind bug /assign @jwforres
3.7 fix for missing service class reference: https://github.com/openshift/origin-web-console/pull/2636
Adding need info flag for this question: In your environment, do you have the ansible service broker installed with this service class and service plan?
Just a standalone serviceinstance created by that mentioned yaml file, non-existent service class or service plan for it.
Checked this issue in OCP v3.9.0-0.24.0, could create via YAML file successfully.
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/RHBA-2018:0636