[WIP] Temporarily disable failing OLM tests

[spadgett]

It looks like #1172 reenabled some failing OLM tests. Best I can tell, this is not a problem in console or with the tests themselves, but legitimate failures in OLM. I haven't seen the OLM tests pass since the PR merged, and I can reproduce the problems locally on a fresh install.

Here's the error I'm seeing in the install plan:

status:
  catalogSources:
    - installed-community-openshift-operators
  conditions:
    - lastTransitionTime: '2019-02-23T19:39:52Z'
      lastUpdateTime: '2019-02-23T19:39:52Z'
      message: >-
        error creating csv etcdoperator.v0.9.2: an error on the server ("This
        request caused apiserver to panic. Look in the logs for details.") has
        prevented the request from succeeding (post
        clusterserviceversions.operators.coreos.com)
      reason: InstallComponentFailed
      status: 'False'
      type: Installed
phase: Failed

Since two dozen approved console PRs are blocked on this, I'd like to consider disabling the tests for now (and putting /hold on any OLM-related PRs) to unblock the queue.

@alecmerdler @jwforres

[alecmerdler]

Tests are failing because of an accidental CRD validation change to ClusterServiceVersion (I guess the OpenShift apiserver panics when it can't parse regex). Fix is in this PR in OLM.

[spadgett]

Fix is in this PR in OLM.

Thanks, if we have a real fix even better. I'll keep an eye on that PR.

[openshift-ci-robot]

@spadgett: The following test failed for commit 39faacb, say /retest to rerun them:

Test name	Details	Rerun command
ci/prow/console-e2e	link	/test console-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.