-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kibana API saved object export/import issue. #123406
Comments
Created this is a separate issue to not muddy the waters in the other issue, We saw it submit, says is succeeded, but most of the saved objects never shows up. |
@dclassen-maxar is working this issue more closely then me. |
Pinging @elastic/kibana-core (Team:Core) |
Thanks for the ping and creating a new issue for the saved objects import/export bug. We'll investigate and report back. |
Description rephrased: Bug Kibana version: Server OS version: Original install method (e.g. download page, yum, from source, etc.): Describe the bug: @dclassen-maxar, please let us know if this describe the issue properly and if "missing" means that the saved objects aren't listed in the saved objects list view or that they don't get imported at all. |
Branching this off from where we made an initial comment as the issue looked similar
@asazallesmilner are you importing the saved objects into the same space as they were exported from? we have tried going between two different clusters into the same space.
The logs given in the issue's description don't give us much to go on here, we ideally need verbose logs.
The steps to reproduce also don't mention exporting an importing saved objects so we need more info on how you came across the bug please.
For example:
cluster already has minimal data
both are 7.16. But one is 7.16.1 and other was 7.16.2
same permissions
same license
yes
etc...
Deployment is different, one is k8s/eck, the other is cloud.
Some spaces DID get dashboards when we tried this but we have no idea what made a difference.
Originally posted by @TinaHeiligers in #120422 (comment)
The text was updated successfully, but these errors were encountered: