Closed elastic-vault-github-plugin-prod[bot] closed 1 month ago
/test
/test
@michel-laterman could you please have a look here to tell me if we need to force merge? We can't bump Elastic Agent without Fleet Server as you can imagine. cc @ycombinator
The e2e tests failed because it wasn't able to find the image that is used. I think we should be good to merge; we can rebase off the 8.15 branch to get the latest image used in the e2e tests to pass
buildkite test this
The e2e tests failed because it wasn't able to find the image that is used.
@michel-laterman which image are you referring to? If I run docker pull docker.elastic.co/cloud-release/elastic-agent-cloud:8.15.0-5b8c47c1-SNAPSHOT
locally, it succeeds.
It looks to me the build is failing on this line because it can't find the source file to copy: https://github.com/elastic/fleet-server/blob/35eaa675b02f093d09daf61eb59a4b52cae4ec48/dev-tools/e2e/Dockerfile#L6-L7
=> ERROR COPY --chmod=0755 --chown=elastic-agent cover/fleet-server-8.15.0-SNAPSHOT-linux-x86_64/fleet-server ./data/elastic-agent-72b0ef/c 0.0s
--
| ------
| > COPY --chmod=0755 --chown=elastic-agent cover/fleet-server-8.15.0-SNAPSHOT-linux-x86_64/fleet-server ./data/elastic-agent-72b0ef/components/fleet-server:
| ------
...
ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 447ce277-c51f-4775-92ec-569521784958::jb5btwh6olhabwsv4upyy2bop: failed to walk /var/lib/docker/tmp/buildkit-mount1211093400/cover/fleet-server-8.15.0-SNAPSHOT-linux-x86_64: lstat /var/lib/docker/tmp/buildkit-mount1211093400/cover/fleet-server-8.15.0-SNAPSHOT-linux-x86_64: no such file or directory
I think this is failing to build the custom elastic-agent docker image we use for tests.
Currently it is failing because the command has --chown=elastic-agent cover/fleet-server-8.15.0-SNAPSHOT-linux-x86_64/fleet-server
; but we expect the version to be 8.15.1
because this pr bumps the version number, but the .env file does not reflect the new version until this is merged
I think we need to force merge this
@michel-laterman Sure, I have force merged this PR but I have a couple of questions to better understand what's going on:
8.14.1
in the same was as they are on this PR. Why did the E2E tests succeed on that one but aren't on this one?8.15
branch the same way it is on this PR until an 8.15.1
snapshot is released and the .env
file is updated with it's version?
Updates references to the new release 8.15.1.
Merge after the release 8.15.0.