Skip to content

[9.1] fix: Add sync check for saved objects for trained models. (#237812)#238356

Merged
kibanamachine merged 4 commits intoelastic:9.1from
kibanamachine:backport/9.1/pr-237812
Oct 15, 2025
Merged

[9.1] fix: Add sync check for saved objects for trained models. (#237812)#238356
kibanamachine merged 4 commits intoelastic:9.1from
kibanamachine:backport/9.1/pr-237812

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…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 kibanamachine added the backport This PR is a backport of another PR label Oct 9, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) October 9, 2025 22:14
@efegurkan
Copy link
Member

@elasticmachine merge upstream

@efegurkan
Copy link
Member

@elasticmachine merge upstream

@kibanamachine kibanamachine merged commit eeaa07d into elastic:9.1 Oct 15, 2025
12 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
indexManagement 675.5KB 675.8KB +247.0B

History

cc @efegurkan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

3 participants