-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Metricbeat Python docker-compose system tests are failing with KeyError: 'ContainerConfig' #38539
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
@lalit-satapathy could we have someone to investigate here please? |
CC: @shmsr are these any module specific issues or any structural outside problems. We can not have so many failures on different modules. |
Attempt to fix elastic#38539
Skipping the test does not fix this failure: #38665 It and other tests still fail in the setup phase:
|
I suspect the docker version in the CI runners may have been upgraded, causing this: https://askubuntu.com/questions/1508129/docker-compose-giving-containerconfig-errors-after-update-today The Docker compose Python package we use hasn't been updated since 2021 https://pypi.org/project/docker-compose/ and has probably fallen out of support upstream. |
Yes, I also saw the same askUbuntu thread yesterday but so far no luck. Also, there are more errors. Example:
Trying (hit and trial) all here: #38629 @cmacknz If the version of docker-compose and Python SDK are matching (v1.x) don't you think it should ideally work irrespective of the support? It's been deprecated for a long time. Also, I see a lot of changes have been made in #38605 and #37827. Could it be related? Because suddenly there are a lot of issues in the CI. For example, CI was passing for this PR last week but right now it is not. |
The first commit to main I can see failing with this specific metricbeat Python integration test failure is https://beats-ci.elastic.co/job/Beats/job/beats/job/main/2431/ which isn't even a change to Metricbeat. The same change is also the first appearance of the problem in 8.13 (https://beats-ci.elastic.co/job/Beats/job/beats/job/8.13/68/) which is very odd because it is a change to Packetbeat that doesn’t change anything to do with CI: https://github.com/elastic/beats/pull/38223/files |
In 8.12 the failure also started happening after https://beats-ci.elastic.co/job/Beats/job/beats/job/8.12/169/ so this does not correlate to changes in Beats at all. It correlates with the date March 21st around 9:30 PM EDT. |
This is almost certainly going to turn out to be related to an underlying build infrastructure change given it doesn't correlate to a change in Beats but rather to a specific time. I've asked the ingest eng prod team if they can help track down the source of the problem. |
The nginx test failure in the Go integration tests is also in 7.17 but the Python tests don't fail there which is even weirder https://beats-ci.elastic.co/job/Beats/job/beats/job/7.17/1067/ |
@cmacknz Thanks for helping with this. Will wait for a response from ingest eng prod team. |
Confirmed that the Docker version in the Jenkins runner was bumped and seems to have triggered this. We believe the fastest fix is going to be rewriting our Python compose Class to use https://github.com/gabrieldemarmiesse/python-on-whales?tab=readme-ov-file which interacts with compose from the CLI instead of depending on the obsolete docker V1 API.
|
Yes, python-on-whales appears to be a good solution! |
Closing this as outdated - cc @pierrehilbert |
💔 Tests Failed
Expand to view the summary
Build stats
Start Time: 2024-03-21T21:27:39.162+0000
Duration: 152 min 27 sec
Test stats 🧪
Test errors
Expand to view the tests failures
> Show only the first 10 test failures
Build&Test / metricbeat-pythonIntegTest / test_jolokia_jmx – metricbeat.tests.system.test_autodiscover_jolokia.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_dashboards – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_export_config – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_export_ilm_policy – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_export_index_pattern – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_export_index_pattern_migration – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_export_template – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_index_management – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_start_stop – metricbeat.tests.system.test_base.Test
Expand to view the error details
Expand to view the stacktrace
Build&Test / metricbeat-pythonIntegTest / test_metricsets_0_stats – metricbeat.module.beat.test_beat.Test
Expand to view the error details
Expand to view the stacktrace
Steps errors
Expand to view the steps failures
metricbeat-goIntegTest - mage goIntegTest
mage goIntegTest
metricbeat-goIntegTest - mage goIntegTest
mage goIntegTest
metricbeat-goIntegTest - mage goIntegTest
mage goIntegTest
metricbeat-pythonIntegTest - mage pythonIntegTest
mage pythonIntegTest
metricbeat-pythonIntegTest - mage pythonIntegTest
mage pythonIntegTest
metricbeat-pythonIntegTest - mage pythonIntegTest
mage pythonIntegTest
Error signal
Error "hudson.AbortException: script returned exit code 1"
The text was updated successfully, but these errors were encountered: