[Fleet] allow integration rollback if not all package policies are upgraded#253646
Merged
juliaElastic merged 3 commits intoelastic:mainfrom Feb 19, 2026
Merged
Conversation
juliaElastic
added
release_note:enhancement
backport:version
botelastic
bot
added
the
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
nchaulet
reviewed
Feb 18, 2026
x-pack/platform/plugins/shared/fleet/server/services/package_policy.ts
Outdated
Show resolved
Hide resolved
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
History
|
Contributor
|
Starting backport for target branches: 9.3 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 19, 2026
…graded (elastic#253646) ## Summary Closes elastic#250846 Removed the requirement for all integration policies to be on the upgraded version to allow rollback. Instead, allow rollback if integration policies are either on the previous version or have a previous version saved. To verify: - Add an integration with 2 policies - Upgrade base integration and then 1 integration policy - Verify that rollback is available and succeeds <img width="1074" height="506" alt="image" src="https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be" /> <img width="1071" height="742" alt="image" src="https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8" /> <img width="1075" height="432" alt="image" src="https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c" /> <img width="1071" height="834" alt="image" src="https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f" /> <img width="1807" height="461" alt="image" src="https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit c3da711)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
chrisbmar
pushed a commit
to chrisbmar/kibana
that referenced
this pull request
Feb 19, 2026
…graded (elastic#253646) ## Summary Closes elastic#250846 Removed the requirement for all integration policies to be on the upgraded version to allow rollback. Instead, allow rollback if integration policies are either on the previous version or have a previous version saved. To verify: - Add an integration with 2 policies - Upgrade base integration and then 1 integration policy - Verify that rollback is available and succeeds <img width="1074" height="506" alt="image" src="https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be" /> <img width="1071" height="742" alt="image" src="https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8" /> <img width="1075" height="432" alt="image" src="https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c" /> <img width="1071" height="834" alt="image" src="https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f" /> <img width="1807" height="461" alt="image" src="https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
kibanamachine
added a commit
that referenced
this pull request
Feb 19, 2026
…are upgraded (#253646) (#253907) # Backport This will backport the following commits from `main` to `9.3`: - [[Fleet] allow integration rollback if not all package policies are upgraded (#253646)](#253646) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-02-19T08:30:51Z","message":"[Fleet] allow integration rollback if not all package policies are upgraded (#253646)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/250846\n\nRemoved the requirement for all integration policies to be on the\nupgraded version to allow rollback.\nInstead, allow rollback if integration policies are either on the\nprevious version or have a previous version saved.\n\nTo verify:\n- Add an integration with 2 policies\n- Upgrade base integration and then 1 integration policy\n- Verify that rollback is available and succeeds\n\n<img width=\"1074\" height=\"506\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be\"\n/>\n<img width=\"1071\" height=\"742\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8\"\n/>\n<img width=\"1075\" height=\"432\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c\"\n/>\n<img width=\"1071\" height=\"834\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f\"\n/>\n<img width=\"1807\" height=\"461\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c3da711954997636279b330276db3dcdb2db3f0f","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Fleet","backport:version","v9.4.0","v9.3.1"],"title":"[Fleet] allow integration rollback if not all package policies are upgraded","number":253646,"url":"https://github.com/elastic/kibana/pull/253646","mergeCommit":{"message":"[Fleet] allow integration rollback if not all package policies are upgraded (#253646)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/250846\n\nRemoved the requirement for all integration policies to be on the\nupgraded version to allow rollback.\nInstead, allow rollback if integration policies are either on the\nprevious version or have a previous version saved.\n\nTo verify:\n- Add an integration with 2 policies\n- Upgrade base integration and then 1 integration policy\n- Verify that rollback is available and succeeds\n\n<img width=\"1074\" height=\"506\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be\"\n/>\n<img width=\"1071\" height=\"742\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8\"\n/>\n<img width=\"1075\" height=\"432\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c\"\n/>\n<img width=\"1071\" height=\"834\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f\"\n/>\n<img width=\"1807\" height=\"461\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c3da711954997636279b330276db3dcdb2db3f0f"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/253646","number":253646,"mergeCommit":{"message":"[Fleet] allow integration rollback if not all package policies are upgraded (#253646)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/250846\n\nRemoved the requirement for all integration policies to be on the\nupgraded version to allow rollback.\nInstead, allow rollback if integration policies are either on the\nprevious version or have a previous version saved.\n\nTo verify:\n- Add an integration with 2 policies\n- Upgrade base integration and then 1 integration policy\n- Verify that rollback is available and succeeds\n\n<img width=\"1074\" height=\"506\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be\"\n/>\n<img width=\"1071\" height=\"742\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8\"\n/>\n<img width=\"1075\" height=\"432\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c\"\n/>\n<img width=\"1071\" height=\"834\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f\"\n/>\n<img width=\"1807\" height=\"461\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a\"\n/>\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"c3da711954997636279b330276db3dcdb2db3f0f"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com>
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
…graded (elastic#253646) ## Summary Closes elastic#250846 Removed the requirement for all integration policies to be on the upgraded version to allow rollback. Instead, allow rollback if integration policies are either on the previous version or have a previous version saved. To verify: - Add an integration with 2 policies - Upgrade base integration and then 1 integration policy - Verify that rollback is available and succeeds <img width="1074" height="506" alt="image" src="https://github.com/user-attachments/assets/64d70aeb-69ff-48b3-b921-f2478a9915be" /> <img width="1071" height="742" alt="image" src="https://github.com/user-attachments/assets/601f8ad1-155e-4140-aee8-4505977c5ad8" /> <img width="1075" height="432" alt="image" src="https://github.com/user-attachments/assets/1b2417c0-f5ea-4f53-8837-ff725fdbf53c" /> <img width="1071" height="834" alt="image" src="https://github.com/user-attachments/assets/c2a9c88b-5231-43b0-a96c-a5a90ba87d5f" /> <img width="1807" height="461" alt="image" src="https://github.com/user-attachments/assets/32e6dbf9-d6c4-41cb-a302-47a4d663cc7a" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #250846
Removed the requirement for all integration policies to be on the upgraded version to allow rollback.
Instead, allow rollback if integration policies are either on the previous version or have a previous version saved.
To verify:
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.