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

8.16.0-SNAPSHOT: standalone to managed migration is broken #14178

Closed
marclop opened this issue Sep 25, 2024 · 3 comments
Closed

8.16.0-SNAPSHOT: standalone to managed migration is broken #14178

marclop opened this issue Sep 25, 2024 · 3 comments
Labels

Comments

@marclop
Copy link
Contributor

marclop commented Sep 25, 2024

Description

The migration of apm-server from standalone to managed mode is broken.

Error: error loading config file: stat apm-server.yml: no such file or directory

Image

Reproduce

Manual

  1. Create APM Server 7.17.25 standalone
  2. Upgrade to 8.16.0-SNAPSHOT
  3. Migrate from standalone to managed mode.
  4. APM Server will break

Image

Smoke test

$ make smoketest/run-version TEST_DIR=./testing/smoke/legacy-standalone-major-managed SMOKETEST_VERSION=8.16.0-SNAPSHOT
-> Running ./testing/smoke/legacy-standalone-major-managed smoke tests for version latest...
-> Running 7.17.25-SNAPSHOT standalone to 8.16.0-SNAPSHOT to 8.16.0-SNAPSHOT managed
-> Adding tfvar stack_version="7.17.25-SNAPSHOT"
-> Adding tfvar integrations_server="false"
-> Applying terraform configuration...
-> APM Server ready!
-> Sending events to APM Server...
-> Asserting legacy ingest pipelines...
-> Asserting legacy index templates...
-> Asserting legacy ILM policies...
-> Asserting apm-7.17.25-error-* contains expected documents...
-> Asserted 1 error.id=9876543210abcdeffedcba0123456789 exists
-> Asserting apm-7.17.25-span-* contains expected documents...
-> Asserted 1 span.id=1234567890aaaade exists
-> Asserting apm-7.17.25-transaction-* contains expected documents...
-> Asserted 1 transaction.id=4340a8e0df1906ecbfa9 exists
-> Asserting apm-7.17.25-metric-* contains expected documents...
-> Asserted 1 transaction.type=request exists
-> Adding tfvar stack_version="8.16.0-SNAPSHOT"
-> Adding tfvar integrations_server="false"
-> Applying terraform configuration...
-> APM Server ready!
-> Sending events to APM Server...
-> Asserting ingest pipelines...
-> Asserting logs-apm.error-* contains expected documents...
-> Asserted 1 error.id=9876543210abcdeffedcba0123456789 exists
-> Asserting traces-apm-* contains expected documents...
-> Asserted 1 span.id=1234567890aaaade exists
-> Asserting traces-apm-* contains expected documents...
-> Asserted 1 transaction.id=4340a8e0df1906ecbfa9 exists
-> Asserting metrics-apm.internal-* contains expected documents...
-> Asserted 1 transaction.type=request exists
-> Upgrading APM Server 8.16.0-SNAPSHOT to managed mode...
-> Waiting for 90 seconds for the APM Server to become available...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (1/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (2/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (3/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (4/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (5/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (6/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (7/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (8/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, retrying (9/10)...
{"ok":false,"message":"The requested resource is currently unavailable."}
-> APM Server isn't ready to receive events, maximum retries exceeded
make: *** [smoketest/run-version] Error 1
@marclop marclop added the bug label Sep 25, 2024
@marclop
Copy link
Contributor Author

marclop commented Sep 25, 2024

Discovered when working on fixing the smoke tests: #14176

@marclop
Copy link
Contributor Author

marclop commented Sep 25, 2024

This was already reported in elastic/elastic-agent#5615, and it seems like the issue has been identified. I will leave open until it's fixed.

@marclop
Copy link
Contributor Author

marclop commented Oct 18, 2024

This has now been resolved.

@marclop marclop closed this as completed Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant