Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-354

Include ClusterOperator status when failing integration tests

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • 3
    • False
    • False
    • Undefined

      In a CI job out of operator#96 with a long UpdateService name, the failing output is not all that helpful:

      === RUN   TestCustomResource
I0129 00:24:41.214186    5083 utils.go:113] Deployment updateservice-operator available (1/1)
I0129 00:25:11.254914    5083 utils.go:134] Service updateservice-operator-metrics available
I0129 00:25:12.399243    5083 utils.go:86] updateservice.updateservice.operator.openshift.io/example created
I0129 00:25:12.421999    5083 utils.go:140] Deleting custom resource
--- FAIL: TestCustomResource (61.35s)
    updateservice_creation_test.go:77: updateservices.updateservice.operator.openshift.io "example-resource-name-more-than-limit" not found
FAIL
FAIL	github.com/openshift/cincinnati-operator/functests	61.360s
FAIL
make: *** [func-test] Error 1
error: failed to execute wrapped command: exit status 2

      Ideally we dump the UpdateService status or some such to aid debugging.

              Unassigned Unassigned
              trking W. Trevor King
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: