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

[Ingest-Management]: Integration data does not appear under default config (copy) page, after creating a copy of default configuration. #620 #72927

Closed
ph opened this issue Jul 22, 2020 · 1 comment · Fixed by #73128
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@ph
Copy link
Contributor

ph commented Jul 22, 2020

Kibana version:
Kibana: 7.9 BC2

Elasticsearch version:
Elasticsearch: 7.9 BC2

Agent version:
Agent: 7.9 BC2

Browser version:
Windows 10, Chrome

Original install method (e.g. download page, yum, from source, etc.):
From 7.9 BC2

Description
[Ingest-Management]: Integration data does not appear under default config (copy) page, after creating a copy of default configuration.

Preconditions

  1. Kibana 7.9 BC2 cloud environment should be available.
  2. Agent should be enrolled on environment.

Steps to Reproduce

  1. Open the Kibana 7.9 BC2 cloud environment in browser, then click Ingest Manager>Configuration tab.
  2. Click "Action>Copy Config" option next to Default configuration and notice that "Copy Default agent Configuration" pop up will appear.
  3. Click on "Copy Configuration" button and notice that a new default config will created with "Copy" tag.
  4. Click on "Default Config (copy)" name and navigate to respective page.
  5. Observe that integration data not appears under integration tab.
  6. Then click on "Action>Edit Integration" option next to any empty row and observe that error appears.

Test data
N/A

Impacted Test case id
N/A

Actual Result
[Ingest-Management]: Integration data does not appear under default config (copy) page, after creating a copy of default configuration

Expected Result
Appropriate Integration data should appear under default config (copy) page, after creating a copy of default configuration.

What's working
N/A

What's not working
Also, Error is displayed when user try to edit the integration from "Action" Menu displayed next to empty rows not having integration data.

Screenshot
1.
Copyconfig_issue

Copyconfig_issue2

Console Logs
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-P5polb1UreUSOe5V/Pv7tc+yeZuJXiOi/3fqhGsU7BE='), or a nonce ('nonce-...') is required to enable inline execution.

bootstrap.js:43 ^ A single error about an inline script not firing due to content security policy is expected!
kbn-ui-shared-deps.js:453 INFO: 2020-07-22T09:37:35Z
Adding connection to https://c74fb756b4644a129000dfd6f89057b7.us-central1.gcp.foundit.no:9243/elasticsearch

@ph ph assigned skh Jul 22, 2020
@ph ph added the Team:Fleet Team label for Observability Data Collection Fleet team label Jul 22, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@ph ph added the bug Fixes for quality problems that affect the customer experience label Jul 22, 2020
@ph ph assigned jen-huang and unassigned skh Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants