Thibault Richard

Testing.

We are seeing some flaky PR builds with this error: ```json { "log.level": "info", "@timestamp": "2022-07-28T12:51:03.391Z", "log.logger": "e2e-qrwqu", "message": "Deploying monitoring", "service.version": "0.0.0-SNAPSHOT+00000000", "service.type": "eck", "ecs.version": "1.4.0" } { "log.level":...

TestFleetCustomLogsIntegrationRecipe is flaky

2

`TestFleetCustomLogsIntegrationRecipe` failed because the Agent isn't well configured by FleetServer because Kibana couldn't add the [Fleet Server on ECK policy] due to a 502 Bad Gateway error response from the...

TestAgentVersionUpgradeToLatest8x/ES_data_should_pass_validations is flaky

1

``` === RUN TestAgentVersionUpgradeToLatest8x/ES_data_should_pass_validations Retries (30m0s timeout): ............................................. step.go:43: Error Trace: utils.go:88 Error: Received unexpected error: elasticsearch client failed for https://test-agent-upgrade-kvwd-es-internal-http.e2e-svc9x-mercury.svc:9200/_data_stream/logs-elastic_agent.filebeat-default: 404 Not Found: {Status:404 Error:{CausedBy:{Reason: Type:} Reason:no such index...

TestAgentVersionUpgradeToLatest8x is failing

3

`TestAgentVersionUpgradeToLatest8x` failed 3 times recently: - 2022-01-24T02:37:22.702Z | [cloud-on-k8s-e2e-tests-snapshot-versions/499](https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-snapshot-versions/499/testReport/github/com_elastic_cloud-on-k8s_test_e2e_agent/TestAgentVersionUpgradeToLatest8x_Elasticsearch_cluster_health_should_not_have_been_red_during_mutation_process/) - 2022-02-07T02:27:38.791Z | [cloud-on-k8s-e2e-tests-snapshot-versions/509](https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-snapshot-versions/509/testReport/github/com_elastic_cloud-on-k8s_test_e2e_agent/TestAgentVersionUpgradeToLatest8x_Elasticsearch_cluster_health_should_not_have_been_red_during_mutation_process/) - 2022-02-08T02:44:08.234Z | [cloud-on-k8s-e2e-tests-gke-k8s-versions/649](https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-gke-k8s-versions/649/testReport/junit/github/com_elastic_cloud-on-k8s_test_e2e_agent/Run_tests_for_different_k8s_versions_in_GKE___1_21___TestAgentVersionUpgradeToLatest8x_Elasticsearch_cluster_health_should_not_have_been_red_during_mutation_process/) The cluster health is seen as red during the upgrade from the current...

agent.TestSystemIntegrationRecipe is flaky

2

`TestSystemIntegrationRecipe` failed this night. This may be related to the upgrade of the stack version to 7.17.0. - https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-aks/930/testReport/ - https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-kind-k8s-versions/666/testReport/ ``` === RUN TestSystemIntegrationRecipe/ES_data_should_pass_validations Retries (30m0s timeout): .................................................... step.go:43:...

Once the Elastic documentation is published with main instead of [master](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-quickstart.html), we have to replace all references to `www.elastic.co/guide/en/cloud-on-k8s/master` by `www.elastic.co/guide/en/cloud-on-k8s/main`. This is a remaining task following #5017.

Depending on how you choose to install ECK, the operator Pod doesn't have the same labels. Using Helm: - `app.kubernetes.io/instance: elastic-operator` - `app.kubernetes.io/name: elastic-operator` Using all-in-one YAML manifest: - `control-plane:...

Filebeat is OOMKilled. ``` === RUN TestFilebeatAutodiscoverRecipe/ES_data_should_pass_validations Retries (30m0s timeout): ............................................. step.go:43: Error Trace: utils.go:87 Error: Received unexpected error: hit count should be more than 0 for /*beat*/_search?q=kubernetes.pod.name:fb-autodiscover-pjj9 Test: TestFilebeatAutodiscoverRecipe/ES_data_should_pass_validations...

Update the status of unmanaged resource

1

When we exclude an Elastic resource from being managed by the operator using the `eck.k8s.elastic.co/managed=false` annotation ([documentation](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-eck.html#k8s-beta-to-ga-rolling-restart)), the status subresource reported is no longer updated by the operator and may...