fix: Add sync check for saved objects for trained models.#237812
Merged
efegurkan merged 2 commits intoelastic:mainfrom Oct 9, 2025
Merged
fix: Add sync check for saved objects for trained models.#237812efegurkan merged 2 commits intoelastic:mainfrom
efegurkan merged 2 commits intoelastic:mainfrom
Conversation
efegurkan
added
release_note:fix
Team:Search
backport:version
kapral18
reviewed
Oct 9, 2025
| forceSaveMappings, | ||
| saveMappings, | ||
| saveMappingsLoading, | ||
| setErrorsInTrainedModelDeployment, |
Contributor
There was a problem hiding this comment.
if you remove this, update type signature please as well please or better restore as it was, we will handle this later
Member
Author
There was a problem hiding this comment.
I will restore back. My linter was complaining thats why I removed it.
While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object.
efegurkan
force-pushed
the
syncCheck-on-semantic-retry
branch
from
7749bb0 to
3e3579e
Compare
kapral18
approved these changes
Oct 9, 2025
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
|
Contributor
|
Starting backport for target branches: 9.1, 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 9, 2025
…7812) ## Summary While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object. Before: https://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8 After: https://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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 - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save `semantic_text` fields during deployment without forcing. (cherry picked from commit f485bd3)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 9, 2025
…7812) ## Summary While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object. Before: https://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8 After: https://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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 - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save `semantic_text` fields during deployment without forcing. (cherry picked from commit f485bd3)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Oct 10, 2025
) (#238357) # Backport This will backport the following commits from `main` to `9.2`: - [fix: Add sync check for saved objects for trained models. (#237812)](#237812) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-10-09T22:06:22Z","message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Search","backport:version","v9.1.0","v9.2.0","v9.3.0"],"title":"fix: Add sync check for saved objects for trained models.","number":237812,"url":"https://github.com/elastic/kibana/pull/237812","mergeCommit":{"message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.2"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/237812","number":237812,"mergeCommit":{"message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46"}}]}] BACKPORT--> Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co>
kibanamachine
added
the
backport missing
Contributor
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
1 similar comment
Contributor
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
kibanamachine
added a commit
that referenced
this pull request
Oct 15, 2025
) (#238356) # Backport This will backport the following commits from `main` to `9.1`: - [fix: Add sync check for saved objects for trained models. (#237812)](#237812) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-10-09T22:06:22Z","message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Search","backport:version","v9.1.0","v9.2.0","v9.3.0"],"title":"fix: Add sync check for saved objects for trained models.","number":237812,"url":"https://github.com/elastic/kibana/pull/237812","mergeCommit":{"message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","9.2"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/237812","number":237812,"mergeCommit":{"message":"fix: Add sync check for saved objects for trained models. (#237812)\n\n## Summary\n\nWhile a model is deploying we prevent user to use an infenence endpoint\nin mappings editor with a modal. The modal either asks for a force\nwriting (which would end up working eventually) or there is a try again\nbutton if user wants to wait.\n\nThe try again button wouldn't work because the status of the models are\nchecked and synced to the Saved Objects only when Trained Models page is\nvisited or refresh button is pressed.\n\nThis commit adds sync call to the try again button so we are certain\nthat we get the latest data from the Saved Object.\n\n\n\n\nBefore:\n\n\nhttps://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8\n\nAfter:\n\n\nhttps://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195\n\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- [x] 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- [x] 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- [x] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n\n## Release note\nIndex management mappings editor now syncs model deployment status\ncorrectly. This fixes a case where user couldn't save `semantic_text`\nfields during deployment without forcing.","sha":"f485bd3ec018dce0181cfdab93b69f02b7adfc46"}}]}] BACKPORT--> --------- Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kibanamachine
added
v9.1.6
and removed
backport missing
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
…7812) ## Summary While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object. Before: https://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8 After: https://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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 - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save `semantic_text` fields during deployment without forcing.
nickpeihl
pushed a commit
to nickpeihl/kibana
that referenced
this pull request
Oct 23, 2025
…7812) ## Summary While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object. Before: https://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8 After: https://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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 - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save `semantic_text` fields during deployment without forcing.
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Oct 27, 2025
…7812) ## Summary While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait. The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed. This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object. Before: https://github.com/user-attachments/assets/aac31225-7708-4d6b-85a2-5a3cd5ceace8 After: https://github.com/user-attachments/assets/bea62bad-6cca-4b56-a771-f17b72780195 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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 - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ## Release note Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save `semantic_text` fields during deployment without forcing.
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
While a model is deploying we prevent user to use an infenence endpoint in mappings editor with a modal. The modal either asks for a force writing (which would end up working eventually) or there is a try again button if user wants to wait.
The try again button wouldn't work because the status of the models are checked and synced to the Saved Objects only when Trained Models page is visited or refresh button is pressed.
This commit adds sync call to the try again button so we are certain that we get the latest data from the Saved Object.
Before:
Screen.Recording.2025-10-07.at.12.45.30.mov
After:
Screen.Recording.2025-10-07.at.12.51.12.mov
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.Release note
Index management mappings editor now syncs model deployment status correctly. This fixes a case where user couldn't save
semantic_textfields during deployment without forcing.