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.x builds are failing #4059

Closed
ycombinator opened this issue Oct 29, 2024 · 1 comment
Closed

8.x builds are failing #4059

ycombinator opened this issue Oct 29, 2024 · 1 comment
Assignees
Labels
Team:Automation Label for the Observability productivity team

Comments

@ycombinator
Copy link
Contributor

I just manually triggered the 8.x buildkite pipeline — https://buildkite.com/elastic/fleet-server/builds/5446 — and it fails one of the test cases for the TestAgentInstallSuite (complete logs) like so:

=== RUN   TestAgentInstallSuite/TestAPMInstrumentationPolicy
--
  | agent_install_test.go:416:
  | Error Trace:	/opt/buildkite-agent/builds/bk-agent-prod-gcp-1730158375640266840/elastic/fleet-server/testing/e2e/agent_install_test.go:416
  | Error:      	Received unexpected error:
  | exit status 1
  | Test:       	TestAgentInstallSuite/TestAPMInstrumentationPolicy
  | Messages:   	elastic-agent install failed. command: /usr/bin/sudo /tmp/e2e-agent_install_test/elastic-agent-8.17.0-SNAPSHOT-linux-x86_64/elastic-agent install --fleet-server-es=http://localhost:9200 --fleet-server-service-token=AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuMTo5ZEJEQjQzNVR4NmZxWVpXbko0MDR3 --fleet-server-insecure-http=true --fleet-server-host=0.0.0.0 --fleet-server-policy=fleet-server-apm --non-interactive, exit_code: 1, output: Installing in non-interactive mode.
  | [=== ] Service Started  [6s] Elastic Agent successfully installed, starting enrollment.
  | [=== ] Waiting For Enroll...  [6s] {"log.level":"info","@timestamp":"2024-10-28T23:47:10.048Z","log.origin":{"function":"github.com/elastic/elastic-agent/internal/pkg/agent/cmd.(*enrollCmd).daemonReloadWithBackoff","file.name":"cmd/enroll_cmd.go","file.line":483},"message":"Restarting agent daemon, attempt 0","ecs.version":"1.6.0"}
  | {"log.level":"info","@timestamp":"2024-10-28T23:47:12.061Z","log.origin":{"function":"github.com/elastic/elastic-agent/internal/pkg/agent/cmd.waitForFleetServer.func1","file.name":"cmd/enroll_cmd.go","file.line":826},"message":"Fleet Server - Error - failed version compatibility check with elasticsearch (Agent: 8.17.0-SNAPSHOT, Elasticsearch: 8.16.0): unsupported version","ecs.version":"1.6.0"}
  | Error: fleet-server failed: timed out waiting for Fleet Server to start after 2m0s
  | For help, please see our troubleshooting guide at https://www.elastic.co/guide/en/fleet/8.17/fleet-troubleshooting.html

The notable error is this:

Fleet Server - Error - failed version compatibility check with elasticsearch (Agent: 8.17.0-SNAPSHOT, Elasticsearch: 8.16.0): unsupported version

I believe this is happening because of this line, which should point to 8.17.0-xxxxxxxx-SNAPSHOT but is instead pointing to 8.16.0-xxxxxxxx-SNAPSHOT:

ELASTICSEARCH_VERSION=8.16.0-02af53da-SNAPSHOT

That line is supposed to be kept up to date by automation PRs such as this example (this one is targeting the main branch, which points to 9.0.0). However, we have not seen such automation PRs targeting the 8.x branch. I believe this might be happening because the list returned by

filter:
runs-on: ubuntu-latest
timeout-minutes: 1
outputs:
matrix: ${{ steps.generator.outputs.matrix }}
steps:
- id: generator
uses: elastic/oblt-actions/elastic/active-branches@v1
does not contain 8.x. @v1v could you help look into this please? Thanks!

@ycombinator ycombinator added the Team:Automation Label for the Observability productivity team label Oct 29, 2024
@v1v
Copy link
Member

v1v commented Oct 29, 2024

. @v1v could you help look into this please? Thanks!

This is now fixed. 8.x was considered a valid minor version and was removed as we only supported up to 2 active 8 minor versions.

This might not be true anymore with the new release cadence model - but that's another thing we have not planned yet in our end to be supported - release team might provide an official source of truth for the current active branches (still waiting for their feedback)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Automation Label for the Observability productivity team
Projects
None yet
Development

No branches or pull requests

2 participants