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

[Fleet]: Error popup under Fleet tab on upgrading Kibana from 7.17.5>8.4.0 having APM integration in Elastic Cloud agent policy #137938

Closed
ghost opened this issue Aug 3, 2022 · 6 comments · Fixed by #138094
Labels
bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@ghost
Copy link

ghost commented Aug 3, 2022

Kibana version: 7.17.5 upgraded to 8.4.0 BC1 Kibana Cloud Environment.

Host OS and Browser version: All, All

Build details:
VERSION: 7.17.5 upgraded to 8.4.0 BC1.
BUILD: 54999
COMMIT: 58f7eaf
ARTIFACT LINK: https://staging.elastic.co/8.4.0-91109cf0/summary-8.4.0.html

Preconditions:

  • 7.17.5 upgraded to 8.4.0 BC1 Kibana Cloud Environment should be available.

Steps to reproduce:

  1. Login to 7.17.5 Kibana environment.
  2. Add Elastic APM integration in Elastic Cloud agent policy.
  3. Upgrade the Kibana to 8.4.0 BC1.

Expected Result:

  • No Error popup should be there under Fleet tab on upgrading Kibana from 7.17.5>8.4.0 having APM integration in Elastic Cloud agent policy

Screenshot:

1

@ghost ghost added bug Fixes for quality problems that affect the customer experience impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Fleet Team label for Observability Data Collection Fleet team labels Aug 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@ghost
Copy link
Author

ghost commented Aug 3, 2022

@dikshachauhan-qasource Please review

@dikshachauhan-qasource
Copy link

Secondary review is done

@juliaElastic
Copy link
Contributor

From the error message it seems to be introduced by #100413
cc @criamico

@criamico
Copy link
Contributor

criamico commented Aug 4, 2022

I was able to reproduce this issue with the same steps, the error is coming from the api/fleet/agents/setup endpoint:
Screenshot 2022-08-04 at 12 08 51

I think that the problem comes from here:

const newFields = {
defaultDownloadSourceId: defaultDownloadSource.id,
...fields,

In fact the parameter in AgentPolicy should be download_source_id, not defaultDownloadSourceId, so this is definitely a bug that escaped me while creating the new service. I'll have a fix for it asap as I'll be in PTO the next two weeks.

@ghost ghost added the QA:Ready for Testing Code is merged and ready for QA to validate label Aug 5, 2022
@ghost
Copy link
Author

ghost commented Aug 23, 2022

Hi @criamico
We have revalidated this issue on latest 7.17.5 > 8.4 BC6 Kibana Cloud environment and found it fixed now.

  • No Error popup is there under Fleet tab on upgrading Kibana from 7.17.5>8.4.0 having APM integration in Elastic Cloud agent policy

Build details:
VERSION: 7.17.5 upgraded to 8.4.0 BC1.
BUILD: 55395
COMMIT: 1922ab0
ARTIFACT: https://staging.elastic.co/8.4.0-3b80811b/summary-8.4.0.html

Screenshot:
Screenshot (18)

Hence, marking this as QA:Validated.

@ghost ghost added QA:Validated Issue has been validated by QA and removed QA:Ready for Testing Code is merged and ready for QA to validate labels Aug 23, 2022
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 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA 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