Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36091

shmsr · 2023-07-17T20:11:11Z

What does this PR do?

CPython 3.0 was released recently which has introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available.

Why is it important?

If we don't fix it CI would keep failing.

Checklist

My code follows the style guidelines of this project
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have made corresponding change to the default configuration files
I have added tests that prove my fix is effective or that my feature works
I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

CPython 3.0 released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporarily fix and this commits needs to be reverted when a proper fix is available.

botelastic · 2023-07-17T20:11:18Z

This pull request doesn't have a Team:<team> label.

mergify · 2023-07-17T20:11:47Z

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

The upcoming major version of the Elastic Stack
The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

elasticmachine · 2023-07-17T21:46:25Z

❕ Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-07-17T20:11:31.144+0000
Duration: 362 min 29 sec

Test stats 🧪

Test	Results
Failed	0
Passed	11074
Skipped	311
Total	11385

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

`Print Message`

Took 0 min 0 sec . View more details here
Description: �[39;49m[INFO] Allocating a worker with the labels 'windows-2022'.�[0m

`Print Message`

Took 0 min 0 sec . View more details here
Description: �[39;49m[INFO] Allocating a worker with the labels 'windows-2022'.�[0m

`Archive the artifacts`

Took 0 min 0 sec . View more details here

`Checks if running on a Unix-like node`

Took 0 min 0 sec . View more details here

`Google Storage Download`

Took 0 min 4 sec . View more details here

`Checks if running on a Unix-like node`

Took 0 min 0 sec . View more details here

`Print Message`

Took 0 min 0 sec . View more details here
Description: �[39;49m[INFO] Allocating a worker with the labels 'rhel-9'.�[0m

`Print Message`

Took 0 min 0 sec . View more details here
Description: �[39;49m[INFO] Allocating a worker with the labels 'windows-2022'.�[0m

`Error signal`

Took 0 min 0 sec . View more details here
Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

`Recursively delete the current directory from the workspace`

Took 0 min 3 sec . View more details here

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.
/package : Generate the packages and run the E2E tests.
/beats-tester : Run the installation tests with beats-tester.
run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

blakerouse

Fixes CI!

shmsr · 2023-07-18T04:01:51Z

Need someone from @elastic/elastic-agent-data-plane and @elastic/obs-cloudnative-monitoring to approve as well.

pierrehilbert · 2023-07-18T05:41:39Z

@bturquet can we have someone in your team to review here please?

CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) # Conflicts: # libbeat/tests/system/requirements.txt # libbeat/tests/system/requirements_aix.txt

efd6 · 2023-07-18T08:17:59Z

Will this be backported to 8.9?

CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac)

…s temporarily (#36093) * Pin PyYAML version to 5.3.1 to avoid CI errors temporarily (#36091) CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) # Conflicts: # libbeat/tests/system/requirements.txt # libbeat/tests/system/requirements_aix.txt * Resolve conflicts --------- Co-authored-by: subham sarkar <subham.sarkar@elastic.co> Co-authored-by: Denis Rechkunov <denis.rechkunov@elastic.co>

…36097) CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) Co-authored-by: subham sarkar <subham.sarkar@elastic.co>

CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) # Conflicts: # libbeat/tests/system/requirements.txt # libbeat/tests/system/requirements_aix.txt # metricbeat/Dockerfile

… temporarily (#36141) * Pin PyYAML version to 5.3.1 to avoid CI errors temporarily (#36091) CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) # Conflicts: # libbeat/tests/system/requirements.txt # libbeat/tests/system/requirements_aix.txt # metricbeat/Dockerfile * Update requirements.txt * Update requirements_aix.txt * Update CHANGELOG-developer.next.asciidoc * Update Dockerfile --------- Co-authored-by: subham sarkar <subham.sarkar@elastic.co> Co-authored-by: Pierre HILBERT <pierre.hilbert@elastic.co>

CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. (cherry picked from commit 46adbac) # Conflicts: # libbeat/tests/system/requirements.txt # libbeat/tests/system/requirements_aix.txt

… temporarily (#36189) Backport from #36091 What does this PR do? CPython 3.0 was released recently which has introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available. Why is it important? If we don't fix it CI would keep failing.

…36091)" This reverts commit 46adbac.

…6091) CPython 3.0 was released recently which appears to have introduced a regression that leads to failures when installing PyYAML (and perhaps other packages too). This is a temporary fix and this commits needs to be reverted when a proper fix is available.

shmsr added the bug label Jul 17, 2023

shmsr requested review from a team as code owners July 17, 2023 20:11

shmsr requested review from gsantoro, devamanv, rdner and fearful-symmetry July 17, 2023 20:11

botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 17, 2023

mergify bot assigned shmsr Jul 17, 2023

Add changelog entry

8a7e558

shmsr enabled auto-merge (squash) July 17, 2023 20:22

rdner added the backport-v7.17.0 Automated backport with mergify label Jul 17, 2023

shmsr mentioned this pull request Jul 17, 2023

x-pack/metricbeat/module/sql: Add option to execute SQL queries for all databases #35688

Merged

9 tasks

andrewkroh approved these changes Jul 17, 2023

View reviewed changes

bhapas approved these changes Jul 17, 2023

View reviewed changes

blakerouse approved these changes Jul 18, 2023

View reviewed changes

rdner approved these changes Jul 18, 2023

View reviewed changes

This was referenced Jul 18, 2023

Build 1720 for main with status FAILURE #36087

Closed

Build 1719 for main with status FAILURE #36086

Closed

gizas approved these changes Jul 18, 2023

View reviewed changes

shmsr merged commit 46adbac into elastic:main Jul 18, 2023
90 checks passed

mergify bot mentioned this pull request Jul 18, 2023

[7.17](backport #36091) Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36093

Merged

shmsr deleted the fix-ci-py-issue branch July 18, 2023 06:54

pierrehilbert added the backport-v8.9.0 Automated backport with mergify label Jul 18, 2023

mergify bot mentioned this pull request Jul 18, 2023

[8.9](backport #36091) Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36097

Merged

shmsr mentioned this pull request Jul 19, 2023

Bump PyYAML's version from 5.3.1 to avoid security risks #36119

Closed

6 tasks

pierrehilbert added the backport-v8.7.0 Automated backport with mergify label Jul 24, 2023

mergify bot mentioned this pull request Jul 24, 2023

[8.7](backport #36091) Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36141

Merged

pierrehilbert added the backport-v8.8.0 Automated backport with mergify label Aug 1, 2023

mergify bot mentioned this pull request Aug 1, 2023

[8.8](backport #36091) Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36189

Merged

v1v mentioned this pull request Aug 8, 2023

Pin PyYAML version to 5.3.1 to avoid CI errors temporarily elastic/apm-integration-testing#1572

Merged

cmacknz added a commit that referenced this pull request Jan 5, 2024

Revert "Pin PyYAML version to 5.3.1 to avoid CI errors temporarily (#…

36edc25

…36091)" This reverts commit 46adbac.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36091

Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36091

shmsr commented Jul 17, 2023 •

edited

Loading

botelastic bot commented Jul 17, 2023

mergify bot commented Jul 17, 2023

elasticmachine commented Jul 17, 2023 •

edited by jenkins-beats-ci bot

Loading

Build stats

Test stats 🧪

`Print Message`

`Print Message`

`Archive the artifacts`

`Checks if running on a Unix-like node`

`Google Storage Download`

`Checks if running on a Unix-like node`

`Print Message`

`Print Message`

`Error signal`

`Recursively delete the current directory from the workspace`

blakerouse left a comment

shmsr commented Jul 18, 2023

pierrehilbert commented Jul 18, 2023

efd6 commented Jul 18, 2023

Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36091

Pin PyYAML version to 5.3.1 to avoid CI errors temporarily #36091

Conversation

shmsr commented Jul 17, 2023 • edited Loading

What does this PR do?

Why is it important?

Checklist

Related issues

botelastic bot commented Jul 17, 2023

mergify bot commented Jul 17, 2023

elasticmachine commented Jul 17, 2023 • edited by jenkins-beats-ci bot Loading

❕ Build Aborted

Build stats

Test stats 🧪

Steps errors

Print Message

Print Message

Archive the artifacts

Checks if running on a Unix-like node

Google Storage Download

Checks if running on a Unix-like node

Print Message

Print Message

Error signal

Recursively delete the current directory from the workspace

🤖 GitHub comments

blakerouse left a comment

Choose a reason for hiding this comment

shmsr commented Jul 18, 2023

pierrehilbert commented Jul 18, 2023

efd6 commented Jul 18, 2023

shmsr commented Jul 17, 2023 •

edited

Loading

elasticmachine commented Jul 17, 2023 •

edited by jenkins-beats-ci bot

Loading

`Print Message`

`Print Message`

`Archive the artifacts`

`Checks if running on a Unix-like node`

`Google Storage Download`

`Checks if running on a Unix-like node`

`Print Message`

`Print Message`

`Error signal`

`Recursively delete the current directory from the workspace`