Created attachment 1548084 [details]
clusterlogging and elasticsearch operator logs

Description of problem:

Updating resource limits for ES in the clusterlogging CR does not trigger a new ES deployment.   The change is successfully propagated to the elasticsearch CR but the ES operator does not seem to notice the change and does not trigger a new deployment.

Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-03-25-180911


How reproducible: Always (?).   I saw a new deployment trigger at least once, but on current builds I can reliably reproduce the issue.


Steps to Reproduce:
1. Create a default clusterlogging deployment.   clusterlogging operator and  CRs are in the openshift-logging namespace and the elasticsearch operator is in the openshift-operators namespace
2. oc edit clusterlogging instance and add the following to resources:      
     resources:
        limits:
          cpu: "4"
          memory: 24Gi
        requests:
          cpu: "1"
          memory: 24Gi


3. Verify that the elasticsearch CR is updated with the new requests/limits

Actual results:

No new ES deployment is triggered


Expected results:

ES operator notices the change to the ES CR and triggers a new deployment


Additional info:

clusterlogging and ES operator pod logs attached