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:
3. Verify that the elasticsearch CR is updated with the new requests/limits
No new ES deployment is triggered
ES operator notices the change to the ES CR and triggers a new deployment
clusterlogging and ES operator pod logs attached
Verified on the elasticsearch operator pushed to quay.io today:
Media Type: application/vnd.docker.distribution.manifest.v1+prettyjws
Created: 5h ago
Image Size: 5 layers (size unavailable)
Layers: -- sha256:68cddb23acfeddaee12b95b560b510d2ce2643a3c6a892d9df10da63a3089e78
Changed CPU and memory requests/limits and the ES cluster rolled out again, node-by-node.
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.