[9.1] (backport #8889) Revert [CI] Stable stack version override #8352 and #8528

[mergify]

What does this PR do?

Revert #8352 and #8528

Why is it important?

Team wanted to have a fully automated process for auto-merge if PRs with the bumps passed the CI.

Checklist

• I have read and understood the pull request guidelines of this project.
• 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/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

This is an automatic backport of pull request #8889 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of fb8b883 has failed:

On branch mergify/bp/9.1/pr-8889
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit fb8b88381.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	deleted:    .ci/updatecli/updatecli-bump-stack-version.yml
	deleted:    .github/workflows/bump-stable-snapshot.yml
	modified:   .mergify.yml
	modified:   test_infra/ess/deployment.tf
	deleted:    test_infra/ess/readme.md

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   pkg/testing/ess/create_deployment_csp_configuration.yaml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[swiatekm]

Looks like the e2e test errors are the same as in #8815. We'll need to figure out why these are happening on this stack version - it looks like there's some kind of regression involving ingest pipelines at first glance.

[pkoutsovasilis]

Looks like the e2e test errors are the same as in #8815. We'll need to figure out why these are happening on this stack version - it looks like there's some kind of regression involving ingest pipelines at first glance.

@swiatekm I was just looking at this, could you please create an issue about it and let's discuss it tomorrow in our meeting 🙂

[mergify]

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 71e04fa

Failed CI Steps

• Win2022:sudo:default
• Win2022:sudo:default
• Win2025:sudo:default
• Win2025:sudo:default
• x86_64:sudo: default
• x86_64:sudo: default
• arm:sudo: default
• arm:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default

History

• 💔 Build #23898 failed e911413
• 💔 Build #23811 failed 08eec3b

cc @v1v

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/9.1/pr-8889 upstream/mergify/bp/9.1/pr-8889
git merge upstream/9.1
git push upstream mergify/bp/9.1/pr-8889

[swiatekm]

Looks like the e2e test errors are the same as in #8815. We'll need to figure out why these are happening on this stack version - it looks like there's some kind of regression involving ingest pipelines at first glance.

@swiatekm I was just looking at this, could you please create an issue about it and let's discuss it tomorrow in our meeting 🙂

FYI, I've fixed this in 8630213. It was a problem with the test that happened to be triggered by Kibana enabling spaces by default. I'll port that change to other branches, but here it should be enough to rebase on 9.1.