Bug 1732698: Fix fetching node count from elastichsearch status #498
Conversation
openshift-ci-robot
added
bugzilla/severity-low
|
@periklis: This pull request references Bugzilla bug 1732698, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
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. |
|
/assign @jcantrill |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ewolinetz, periklis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@periklis: All pull requests linked via external trackers have merged: openshift/cluster-logging-operator#498. Bugzilla bug 1732698 has been moved to the MODIFIED state. In response to this:
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. |
Bug 1732698: Fix fetching node count from elastichsearch status
This PR addresses the node count reporting for elasticsearch nodes in the CLO status field. In detail on a setup with more than three nodes the elasticsearch-operator will create more than one deployments. Thus picking up the node count from the spec is not the correct approach.