Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Health to Logstash Status #7528

Merged
merged 2 commits into from
Feb 5, 2024
Merged

Conversation

robbavey
Copy link
Member

@robbavey robbavey commented Feb 1, 2024

This PR adds a Health column to the LogstashStatus, displaying

  • Green if all pods are ready, and all associations are configured and established
  • Yellow if not all pods are ready, but all associations are configured and established
  • Red if neither of those are true

This closes #7527

This PR adds a Health column to the LogstashStatus, displaying

* Green if all pods are ready, and all associations are configured and established
* Yellow if not all pods are ready, but all associations are configured and established
* Red if neither of those are true
@robbavey robbavey marked this pull request as ready for review February 1, 2024 23:09
@botelastic botelastic bot added the triage label Feb 1, 2024
Copy link
Contributor

@kaisecheng kaisecheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI red because of the missing docs from make generate.

I have tried to run with
cd hack/upgrade-test-harness && go run main.go --from-release=v2110 --to-release=upcoming --log-level=debug
but logstash health is still missing

2024-02-02T12:39:06.611Z	DEBUG	eck-upgrade.fixture	Pod ls-ls-0 is running 8.12.0	{"step": "TestStatusOfResources[v2110]", "step": "CheckLogstash[v2110]"}
2024-02-02T12:39:06.611Z	DEBUG	eck-upgrade.fixture	Status mismatch: want={health:green nodes:1 version:8.12.0} have={health: nodes:1 version:8.12.0}	{"step": "TestStatusOfResources[v2110]", "step": "CheckLogstash[v2110]"}

Edit: The change is good and gives Health: green. Test failed because the command test against the old version of operator. LGTM

@kaisecheng
Copy link
Contributor

kaisecheng commented Feb 2, 2024

My steps to run the test

  1. go to https://container-library.elastic.co/r/eck-dev/eck-operator-mmontgomery to check the latest version
  2. make sure the version of eck-operator-mmontgomery in v2110/install.yaml match. I updated it with 2.11.0-bc3-a63a3049
  3. make sure the version of stack in upcoming/stack.yaml match. I updated it with 8.12.1-SNAPSHOT
  4. run test
    $ cd hack/upgrade-test-harness && go run main.go --from-release=v2110 --to-release=upcoming --log-level=debug
  5. switch to namespace elastic-system to check status

@robbavey
Copy link
Member Author

robbavey commented Feb 2, 2024

@pebrc @thbkrkr @barkbay This is ready for review

@thbkrkr thbkrkr added :logstash >enhancement Enhancement of existing functionality labels Feb 5, 2024
@botelastic botelastic bot removed the triage label Feb 5, 2024
@thbkrkr thbkrkr added the v2.12.0 label Feb 5, 2024
@robbavey
Copy link
Member Author

robbavey commented Feb 5, 2024

Thank you @pebrc! I don't have merge access to this repo, so would you mind hitting the merge button?

@pebrc pebrc merged commit 2812125 into elastic:main Feb 5, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality :logstash v2.12.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade Harness test is broken
4 participants