Skip to content

Instantly share code, notes, and snippets.

Created May 14, 2015 22:45
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save anonymous/a93b8fb397d949ac56d9 to your computer and use it in GitHub Desktop.
Save anonymous/a93b8fb397d949ac56d9 to your computer and use it in GitHub Desktop.
root@saltCastle:/srv/salt# salt '*' mine.get 'roles:appserver' network.ip_addrs grain
appserver01:
----------
appserver01:
- 104.236.105.114
appserver02:
- 104.236.118.78
appserver03:
- 45.55.218.184
appserver02:
----------
appserver01:
- 104.236.105.114
appserver02:
- 104.236.118.78
appserver03:
- 45.55.218.184
nginx-rproxy:
----------
appserver01:
- 104.236.105.114
appserver02:
- 104.236.118.78
appserver03:
- 45.55.218.184
It seems appserver01, appserver02, and nginx-rproxy all remember the IP of appserver03, even though it is no longer running and doesn't exist.
root@saltCastle:/srv/salt# salt '*' mine.flush
appserver01:
True
appserver02:
True
nginx-rproxy:
True
Trying to flush the mine contents
root@saltCastle:/srv/salt# salt '*' mine.get 'roles:appserver' network.ip_addrs grain
nginx-rproxy:
----------
appserver03:
- 45.55.218.184
appserver01:
----------
appserver03:
- 45.55.218.184
appserver02:
----------
appserver03:
- 45.55.218.184
It seems they all flushed everything for the servers still running, but left the info for appserver03.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment