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

Build 1038 for 7.17 with status FAILURE #38159

Closed
elasticmachine opened this issue Mar 3, 2024 · 2 comments
Closed

Build 1038 for 7.17 with status FAILURE #38159

elasticmachine opened this issue Mar 3, 2024 · 2 comments
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@elasticmachine
Copy link
Collaborator

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-03-03T03:30:03.888+0000

  • Duration: 62 min 32 sec

Test stats 🧪

Test Results
Failed 1
Passed 2431
Skipped 204
Total 2636

Test errors 1

Expand to view the tests failures

Extended / x-pack/metricbeat-cloud / TestFetch – github.com/elastic/beats/v7/x-pack/metricbeat/module/mssql/performance
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestFetch
    Found orphan containers (metricbeat_7_17_19_a0fd851038-snapshot_ibmmq_1, metricbeat_7_17_19_a0fd851038-snapshot_enterprise_search_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... 
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... error
    
    ERROR: for metricbeat_7_17_19_a0fd851038-snapshot_mssql_1  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    
    ERROR: for mssql  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    Encountered errors while bringing up the project.
        performance_integration_test.go:28: failed to start service "mssql: exit status 1
    Found orphan containers (metricbeat_7_17_19_a0fd851038-snapshot_ibmmq_1, metricbeat_7_17_19_a0fd851038-snapshot_enterprise_search_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... 
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... error
    
    ERROR: for metricbeat_7_17_19_a0fd851038-snapshot_mssql_1  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    
    ERROR: for mssql  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    Encountered errors while bringing up the project.
        performance_integration_test.go:28: failed to start service "mssql: exit status 1
    Found orphan containers (metricbeat_7_17_19_a0fd851038-snapshot_ibmmq_1, metricbeat_7_17_19_a0fd851038-snapshot_enterprise_search_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... 
    Creating metricbeat_7_17_19_a0fd851038-snapshot_mssql_1 ... error
    
    ERROR: for metricbeat_7_17_19_a0fd851038-snapshot_mssql_1  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    
    ERROR: for mssql  Cannot create container for service mssql: Conflict. The container name "/metricbeat_7_17_19_a0fd851038-snapshot_mssql_1" is already in use by container "271afe19938d80d9d783afe5841af1915d15b9b7bd5c53714eebaa800213d2d3". You have to remove (or rename) that container to be able to reuse that name.
    Encountered errors while bringing up the project.
        performance_integration_test.go:28: failed to start service "mssql: exit status 1
        modules.go:111: failed to create new MetricSet 1 error: could not create connection to db: error doing ping to db: Unable to open tcp connection with host "172.18.0.2:1433": dial tcp 172.18.0.2:1433: connect: connection refused
    --- FAIL: TestFetch (25.88s)
     
    

Steps errors 2

Expand to view the steps failures

x-pack/metricbeat-cloud - mage build test
  • Took 18 min 2 sec . View more details here
  • Description: mage build test
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error "hudson.AbortException: script returned exit code 1"

@elasticmachine elasticmachine added automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Mar 3, 2024
@elasticmachine
Copy link
Collaborator Author

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@pierrehilbert
Copy link
Collaborator

Temporary failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

No branches or pull requests

2 participants