Skip to content
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

[profiling] unable to load page error when onboarding using version 8.14.0 #9845

Closed
endorama opened this issue May 13, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@endorama
Copy link
Member

This bug has been reported internally, opening a public issue for awareness and tracking resolution.

When opening Universal profiling "Add profiling data" page the user is met with a Unable to load page error:
Screenshot 2024-05-12 at 18 46 15

Affected integrations:

  • Universal profiling collection, version: 8.14.0

Affected Kibana versions: 8.12 up to 8.12.2, 8.13 up to 8.13.4, 8.14 (development)

The reported browser error is this:

Objects are not valid as a React child (found: object with keys {id, isSecretRef}). If you meant to render a collection of children, use an array instead.

The secret token is rendered as [object Object] on the other screens as per: sudo pf-host-agent-8.13.4-linux-x86_64/pf-host-agent -project-id=1 -secret-token=[object Object] -collection-agent=REDACTED.profiling.europe-west2.gcp.elastic-cloud.com:443

The root cause is PR #9806 which introduced secrets field in the Universal profiling collector integration.
The cause for this behavior is in the Onboarding UI which uses that field to display a guided onboarding process for user and is receiving an unexpected data type.

@endorama endorama added the bug Something isn't working label May 13, 2024
endorama added a commit to elastic/kibana that referenced this issue May 14, 2024
…3305)

Reverts #182915

We discovered that bundling the new version of Universal Profiling
Collector in Kibana results in broken UI (more details
elastic/integrations#9845).

Reverting the PR will allow fleet to bundle older package versions while
we work in providing a long term fix.
@trungcle
Copy link

I have a customer who facing this error in version 8.13, is there any workaround or fix yet? or SLA?
thanks

@endorama
Copy link
Member Author

@trungcle the fix has been merged and should be available. We have reports of the issue being now fixed.

@endorama
Copy link
Member Author

I'm going to close this bug has it has been fixed in integration version 8.14.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants