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

flag provided but not defined: -environment #14280

Closed
carsonip opened this issue Oct 7, 2024 · 2 comments · Fixed by #14310
Closed

flag provided but not defined: -environment #14280

carsonip opened this issue Oct 7, 2024 · 2 comments · Fixed by #14310
Assignees
Labels

Comments

@carsonip
Copy link
Member

carsonip commented Oct 7, 2024

APM Server version (apm-server version): 8.x branch, 9.0 branch

Description of the problem including expected versus actual behavior:

On startup, apm-server will fail to start if --environment is passed. This causes docker images to fail as the entrypoint runs apm-server with --environment=container.

Steps to reproduce:

Please include a minimal but complete recreation of the problem,
including server configuration, agent(s) used, etc. The easier you make it
for us to reproduce it, the more likely that somebody will take the time to
look at it.

  1. go run ./x-pack/apm-server --environment=container -e

Provide logs (if relevant):

flag provided but not defined: -environment
Usage of /tmp/go-build943970858/b001/exe/apm-server:
  -E value
        Configuration overwrite
  -N    Disable actual publishing for testing
  -c value
        Configuration file, relative to path.config (default beat.yml)
  -cpuprofile string
        Write cpu profile to file
  -httpprof string
        Start pprof http server
  -memprofile string
        Write memory profile to this file
  -path.config value
        Configuration path
  -path.data value
        Data path
  -path.home value
        Home path
  -path.logs value
        Logs path
  -plugin value
        Load additional plugins
  -strict.perms
        Strict permission checking on config files (default true)
exit status 2
@carsonip carsonip added the bug label Oct 7, 2024
@carsonip carsonip self-assigned this Oct 7, 2024
@carsonip
Copy link
Member Author

carsonip commented Oct 7, 2024

git bisect shows that the bad commit is 7efa6d5 which is from #14214

carsonip added a commit that referenced this issue Oct 9, 2024
Unblock 8.x backport of #14292 to fix #14280. Reverting beats instead of
bumping beats to avoid #14297.
carsonip added a commit to carsonip/apm-server that referenced this issue Oct 9, 2024
Unblock elastic#14292 to fix elastic#14280. Reverting beats instead of
bumping beats to avoid elastic#14297.
carsonip added a commit that referenced this issue Oct 9, 2024
This reverts commit 7f85cd6.

Unblock #14292 to fix #14280. Reverting beats instead of
bumping beats to avoid #14297.
carsonip added a commit that referenced this issue Oct 9, 2024
This reverts commit e258527.

Unblock #14292 to fix #14280. Reverting beats instead of
bumping beats to avoid #14297.
@carsonip carsonip reopened this Oct 9, 2024
carsonip added a commit that referenced this issue Oct 9, 2024
This reverts commit 7efa6d5.

Require beats bump / revert #14310 (8.x: #14309 )
Part of #14280
mergify bot pushed a commit that referenced this issue Oct 9, 2024
This reverts commit 7efa6d5.

Require beats bump / revert #14310 (8.x: #14309 )
Part of #14280

(cherry picked from commit 01237c4)
mergify bot added a commit that referenced this issue Oct 9, 2024
… (#14314)

This reverts commit 7efa6d5.

Require beats bump / revert #14310 (8.x: #14309 )
Part of #14280

(cherry picked from commit 01237c4)

Co-authored-by: Carson Ip <[email protected]>
@carsonip
Copy link
Member Author

carsonip commented Oct 9, 2024

Closing as #14292 and its 8.x backport #14314 are merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant