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

Sensu client to be configured with IP from specific interface #4

Open
epcim opened this issue Sep 8, 2016 · 0 comments
Open

Sensu client to be configured with IP from specific interface #4

epcim opened this issue Sep 8, 2016 · 0 comments

Comments

@epcim
Copy link
Member

epcim commented Sep 8, 2016

Sensu client should be forced to be configured with IP from specific interface (ie: eth0). In the example below is the IP changed once new interface was added. Other example, If node has keepalived, once the VIP address is on the node and salt-call is run, the VIP might, or actually is, pick-up as client address.

[INFO    ] Executing state file.managed for /etc/sensu/conf.d/client.json
[INFO    ] Fetching file from saltenv 'base', ** skipped ** latest already in cache u'salt://sensu/files/client.json'
[INFO    ] Fetching file from saltenv 'base', ** skipped ** latest already in cache u'salt://linux/map.jinja'
[INFO    ] Fetching file from saltenv 'base', ** skipped ** latest already in cache u'salt://sensu/map.jinja'
[INFO    ] File changed:
--- 
+++ 
@@ -5,7 +5,7 @@
     "fqdn": "ctl01.os1.xxx.local",
     "cluster": "default",
     "graphite_name": "ctl01_os1_xxx_local",
-    "address": "10.200.50.21",
+    "address": "10.1.35.21",
     "keepalive": {
       "thresholds": {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant