Skip to content

e2e: Ensure Consul client is running before starting Nomad service. #24964

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.

Sign up for GitHub

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

Merged
jrasell merged 1 commit into from
Jan 28, 2025
Merged

e2e: Ensure Consul client is running before starting Nomad service. #24964

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions e2e/terraform/provision-infra/provision-nomad/etc/consul.d/consul.service
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ Requires=network-online.target
After=network-online.target

[Service]
Type=notify
Restart=on-failure
Environment=CONSUL_ALLOW_PRIVILEGED_PORTS=true
WorkingDirectory=/etc/consul.d
Expand Down
6 changes: 6 additions & 0 deletions e2e/terraform/provision-infra/provision-nomad/etc/nomad.d/nomad-client.service
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@ After=network-online.target
StartLimitIntervalSec=0
StartLimitBurst=3

# Nomad and Consul are started very closely together. This helps ensure Consul
# is already running before Nomad starts and avoids having to SIGHUP the Nomad
# clients in order to reload the Consul fingerprints.
Wants=consul.service
After=consul.service

[Service]
User=root
ExecReload=/bin/kill -HUP $MAINPID
Expand Down
Loading