-
Notifications
You must be signed in to change notification settings - Fork 42
No datastreams are listed on Fleet #1274
Comments
I'm currently bisecting the test execution between four kibana commits. I've built and pushed Kibana images for those commits, only for AMD, as the APM-CI job is only building the AMD image. For that reason, CI builds below will contain errors for all ARM stages. But we do not care, as we want to verify if the image breaks the tests, never mind whether it is AMD or ARM. ❌ 1st commit: 4a941565502547f96bab72786e1ac11f61f19558 (elastic/kibana#101828)
TAGS="fleet_mode_agent && install && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE KIBANA_VERSION=pr101828 DEVELOPER_MODE=true make -C e2e/_suites/fleet functional-test UPDATE: this image contains the failed TAGS="fleet_mode_agent && revoke-token && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE DEVELOPER_MODE=true KIBANA_VERSION=pr101828 ELASTIC_APM_ACTIVE=false make -C e2e/_suites/fleet functional-test ❌ 2nd commit: cd5cd65fb2ec04ed63fcbc6b87f1fdb7333bee72 (elastic/kibana#102219)
TAGS="fleet_mode_agent && install && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE KIBANA_VERSION=pr102219 DEVELOPER_MODE=true make -C e2e/_suites/fleet functional-test UPDATE: this image contains the failed TAGS="fleet_mode_agent && revoke-token && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE DEVELOPER_MODE=true KIBANA_VERSION=pr102219 ELASTIC_APM_ACTIVE=false make -C e2e/_suites/fleet functional-test 3rd commit: 35cc59b571d19fe52eff17777a4613fd867ff928 (elastic/kibana#101835)
TAGS="fleet_mode_agent && install && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE KIBANA_VERSION=pr101835 DEVELOPER_MODE=true make -C e2e/_suites/fleet functional-test 4th commit: 6df58dd7ca53b43c2f143823ebbe51083618032b (elastic/kibana#101752)
TAGS="fleet_mode_agent && install && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE KIBANA_VERSION=pr101752 DEVELOPER_MODE=true make -C e2e/_suites/fleet functional-test Will post results here. |
It's weird: I've tested with an old Kibana image ( I'm going to locally bisect the elastic-agent image, updating the fleet-server agent and see if the problem comes from there: docker pull docker.elastic.co/observability-ci/elastic-agent:pr-26260-amd64
docker tag docker.elastic.co/observability-ci/elastic-agent:pr-26260-amd64 docker.elastic.co/observability-ci/elastic-agent:8.0.0-SNAPSHOT UPDATE: It is difficult to bisect, because fleet server is trying to validate a binary that is trying to install locally. This is the log output of the fleet-server:
|
Mmm, trying previous step with a clean environment, removing all services in the compose file, and now fleet-server starts properly. But unfortunately the revoke test still fails:
So if the fleet-server is from 8 days ago, when the tests were supposed to be passing, and the tests actually fail, I'd say it's because of another piece of the stack: it seems it's not kibana, it seems it's not fleet-server. Let's check with the agent. I'm gonna bisect the agent, although I'm seeing problems with the packaging job not producing the |
Could this be an elasticsearch change? Maybe the query has changed? |
This is due to the way we currently bring up Kibana, the environment variable |
@adam-stokes and @mdelapenya did #1281 fix this as well? |
No, that was not a solution and this issue is still under investigation. We'll post here more work about it |
I logged a product team bug for this, thanks so much for noting it Manu in slack. def sounds like the same issue:
|
This looks to have been fixed, will wait for @mdelapenya to verify but our tests are passing again |
the duplicate issue was re-tested and found fixed - let's not wait, i'm closing it out. there are other reasons for the tests to fail, if they still are, and we should do new tickets. : / thanks Adam. |
Fixed in elastic/kibana#104415 |
The step
system package dashboards are listed in Fleet
is failing because it does not faind any data stream in the max timeout (3min).It fails on Centos and Debian, in both AMD and ARM.
Steps to reproduce
1 Run:
$ TAGS="fleet_mode_agent && install && centos" TIMEOUT_FACTOR=3 LOG_LEVEL=TRACE DEVELOPER_MODE=true ELASTIC_APM_ACTIVE=false make -C e2e/_suites/fleet functional-test
Expected behaviour: the scenario passes
Current behaviour:
--- Failed steps:
The text was updated successfully, but these errors were encountered: