Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-6179

Report errors when status can't be determined

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • OSSM 3.0-TP1
    • None
    • Project Sail
    • None

      Currently, if an error occurs when the operator tries to determine e.g. the readiness status of the owned resources, it indicates this error in the status of the primary resource, but doesn't return this error to controller-runtime. This means that the resource isn't requeued and thus the status may not get updated until another reconcile is triggered.

      The error should be propagated upwards so that the reconciliation (and thus the status update) is retried.

            mluksa@redhat.com Marko Luksa
            mluksa@redhat.com Marko Luksa
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: