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

[update-collection-v3] Misleading warning "Tracing config migrated" #435

Open
andrzej-stencel opened this issue Jan 20, 2023 · 0 comments
Open
Labels
bug Something isn't working update-collection-v3

Comments

@andrzej-stencel
Copy link
Contributor

Version: v2.17.0

The warning "Tracing config migrated" is output even when there's no tracing config.

Steps to reproduce

  1. Prepare basic user-values.yaml file:
sumologic:
  accessId: xxx
  accessKey: yyy
  clusterName: zzz
  1. Run the migration tool ./update-collection-v3 -in user-values.yaml -out v3.yaml

Expected output

There should be no warning in the console output from the migration tool

Actual output

$ ./update-collection-v3 -in user-values.yaml -out v3.yaml                                                                                                                       
WARNING! Tracing config migrated to v3, please check the output file. For more details see documentation: https://github.com/SumoLogic/sumologic-kubernetes-collection/blob/main/docs/v3-migration-doc.md#tracinginstrumentation-changes
2023/01/20 14:15:32 Successfully migrated the configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working update-collection-v3
Projects
None yet
Development

No branches or pull requests

1 participant