Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2015-10-26

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 trph joined #salt
00:06 subsignal joined #salt
00:12 scoates joined #salt
00:15 quix_ joined #salt
00:22 timoguin joined #salt
00:22 aqua^c joined #salt
00:33 alemeno22 joined #salt
00:34 dthom91 joined #salt
00:35 subsignal joined #salt
00:42 ageorgop joined #salt
00:55 subsigna_ joined #salt
01:06 tomjoad440 joined #salt
01:15 evle joined #salt
01:18 dthom91 joined #salt
01:24 edrocks joined #salt
01:37 bVectr joined #salt
01:49 stanchan joined #salt
01:56 fsteinel_ joined #salt
02:05 ageorgop joined #salt
02:05 Vaelatern How do I refer to two specific hosts? Without a common prefix or anything?
02:07 bVectr Vaelatern: all of these ways: https://docs.saltstack.com/en/develop/topics/targeting/index.html
02:07 Vaelatern Thank you
02:08 sunkist joined #salt
02:08 stanchan joined #salt
02:21 maduro joined #salt
02:25 evidence are there known issue with serving large files over the salt source?
02:26 pirulo joined #salt
02:28 brianvdawson joined #salt
02:29 mapu joined #salt
02:38 mapu joined #salt
02:40 pirulo does any one knows how to install foreman for salt?
02:40 _JZ_ joined #salt
02:47 THE_BOULDER joined #salt
02:48 baweaver joined #salt
02:51 lemur joined #salt
02:53 evle joined #salt
02:57 ^C joined #salt
03:06 kinetic joined #salt
03:08 catpig joined #salt
03:15 bfoxwell joined #salt
03:18 malinoff joined #salt
03:18 malinoff joined #salt
03:19 bfoxwell joined #salt
03:21 bhosmer_ joined #salt
03:34 sunkist joined #salt
03:35 sunkist joined #salt
03:36 dendazen joined #salt
03:37 favadi joined #salt
03:44 ^C hi all
03:44 ^C got an issue with the php-formula - its choosing the wrong context from map.jinja when installing curl
03:45 ^C i've heard that imports are cached, is there a way to clear that cache?
03:45 ^C (actually, thats dealt with by the 'with context' addition...)
03:49 larsfronius joined #salt
03:51 ^C bizarre. all else is mapping to the correct packages for my distro, just not curl
03:52 ^C hahhaaha
03:52 ^C ffs
03:52 ^C f_ing pillar lookup data is overriding it. should have spotted that earlier
04:17 homeshlice joined #salt
04:18 Karan_ joined #salt
05:00 mohae_ joined #salt
05:04 zmalone joined #salt
05:04 TyrfingMjolnir joined #salt
05:07 zmalone joined #salt
05:11 timoguin joined #salt
05:15 kinetic joined #salt
05:24 ronrib joined #salt
05:27 jimklo joined #salt
05:28 rdas joined #salt
05:34 kinetic joined #salt
05:37 impi joined #salt
05:38 favadi joined #salt
05:42 Vaelatern joined #salt
05:52 rbjorklin joined #salt
05:59 Vaelater1 joined #salt
05:59 vaganych joined #salt
06:02 timoguin_ joined #salt
06:04 otter768 joined #salt
06:12 kinetic joined #salt
06:16 ITChap joined #salt
06:16 ITChap Hi
06:16 ITChap When installing from pip is there anyway to get the /etc/salt setup automatically ?
06:17 ITChap or is there any config template available
06:29 anmol joined #salt
06:39 felskrone joined #salt
06:39 jeddi joined #salt
06:41 malinoff joined #salt
06:42 Niamkik joined #salt
06:47 kinetic joined #salt
07:00 dkrae joined #salt
07:02 katyucha joined #salt
07:03 homeshlice is there a tutorial on how to use salt to automate my deployment?
07:22 kinetic joined #salt
07:25 favadi joined #salt
07:28 jb_ joined #salt
07:31 ubikite joined #salt
07:34 impi joined #salt
07:40 pravi joined #salt
07:41 jb_ joined #salt
07:44 carmony joined #salt
07:44 netcho joined #salt
07:45 kawa2014 joined #salt
07:49 rbjorklin joined #salt
07:57 kinetic joined #salt
07:59 rbjorklin joined #salt
08:01 malinoff_ joined #salt
08:02 felskrone joined #salt
08:02 jhauser joined #salt
08:05 otter768 joined #salt
08:06 keimlink joined #salt
08:10 CeBe joined #salt
08:11 markm joined #salt
08:12 mattiasr joined #salt
08:13 eseyman joined #salt
08:14 edulix joined #salt
08:17 linjan_ joined #salt
08:20 cberndt joined #salt
08:23 Grokzen joined #salt
08:27 ggoZ joined #salt
08:35 \ask joined #salt
08:36 kinetic joined #salt
08:36 Guest25336 joined #salt
08:37 kawa2014 joined #salt
08:39 rim-k joined #salt
08:45 OliverUK joined #salt
08:46 mr-op5 joined #salt
08:52 zerthimon joined #salt
08:56 honestly I have this state file: https://gist.github.com/duk3luk3/f87e6cbf0ccab360dbdc that I execute using salt-ssh, and it seems the service restart never happens.
08:56 honestly is this a salt-ssh problem or a "didn't define the watch correctly" problem?
09:02 mattiasr joined #salt
09:03 maveas joined #salt
09:05 trph joined #salt
09:05 trph joined #salt
09:07 thalleralexander joined #salt
09:09 scc joined #salt
09:10 kinetic joined #salt
09:13 Xevian joined #salt
09:15 homeshlice joined #salt
09:21 s_kunk joined #salt
09:30 babilen honestly: Why do you expect a *restart* to take place?
09:31 babilen Or rather: What happens instead?
09:33 thefish joined #salt
09:40 MAHDTech joined #salt
09:45 kinetic joined #salt
09:50 wordsToLiveBy joined #salt
09:51 honestly I expect a restart to take place because that's what a watch on a service.running state is supposed to accomplish.
09:51 wordsToLiveBy left #salt
09:51 honestly given that the watched state has a change, obviously.
09:52 honestly the watched state *has* a change, but I observe nothing happening.
10:06 otter768 joined #salt
10:14 linjan_ joined #salt
10:16 londo joined #salt
10:17 londo joined #salt
10:20 kinetic joined #salt
10:26 favadi joined #salt
10:37 larsfronius joined #salt
10:41 larsfron_ joined #salt
10:42 Grokzen Hi. Have anyone seen the following un-handled exception when running a batch command? https://gist.github.com/Grokzen/bee688aeb4a78598c096
10:50 amcorreia joined #salt
10:53 rotbeard joined #salt
10:54 kinetic joined #salt
10:55 rotbeard hi, is it possible to use variables in/as a for loop list? like {% for name in [ {{ foo }}, {{ bar }} ] %}
10:55 eseyman joined #salt
10:56 Mate rotbeard: yes, but without the {{}}
10:56 Mate like in a python code
10:57 rotbeard thanks Mate.
10:57 saffe joined #salt
11:01 ubikite joined #salt
11:02 honestly babilen: any ideas?
11:09 rubenb joined #salt
11:09 sgargan joined #salt
11:10 babilen honestly: Show me!
11:11 babilen (but then I'm sort of busy, but there's little to do without actual output)
11:12 SunPowered joined #salt
11:15 honestly I have *all* the output
11:16 ubikite1 joined #salt
11:17 ubikite joined #salt
11:18 Anon8 joined #salt
11:18 honestly babilen: http://ix.io/lCW
11:22 SunPowered good morning
11:22 babilen honestly: Mind trying a watch_in in the write-keepalived-conf state? (it looks fine fwiw)
11:23 honestly babilen: the output I gave you already has watch_in
11:24 honestly both give the same (lack of) result
11:24 honestly well, the output says that there *was* a change in the service.running state
11:25 honestly but I'm not seeing the service actually being restarted on the host
11:25 babilen Was it running before? That might be a b0rken init script
11:26 honestly it was running, yes
11:26 babilen Your states are correct (I personally prefer watch_in, but that doesn't make a difference). It is either a genuine problem in salt or something wonky with keepalived's init system integration or salt's treatment of it.
11:26 babilen Try another service
11:27 honestly I will just put a cmd.wait instead of service.running
11:28 babilen Well, it would be nice to know why it doesn't work and fix that
11:29 Anon8 left #salt
11:30 kinetic joined #salt
11:34 honestly too bad -l debug doesn't tell us ;)
11:35 honestly is there anything I can poke so logging of the module execution happens?
11:41 shorty_mu joined #salt
11:43 teryx510 joined #salt
11:43 honestly babilen: seems like salt-ssh doesn't really respect minion logging settings configured using ssh_minion_opts in master config
11:45 breakingmatter joined #salt
11:48 honestly hmmm, interesting
11:48 honestly I cajoled it into logging things
11:49 honestly 2015-10-26 12:48:01,384 [salt.loaded.int.module.cmdmod][INFO    ][17712] Executing command ['service', 'keepalived', 'status'] in directory '/home/erlacher'
11:49 honestly 2015-10-26 12:48:01,389 [salt.loaded.int.module.cmdmod][ERROR   ][17712] Command ['service', 'keepalived', 'status'] failed with return code: 1
11:49 honestly 2015-10-26 12:48:01,389 [salt.loaded.int.module.cmdmod][ERROR   ][17712] output: Usage: /etc/init.d/keepalived {start|stop|restart|reload|force-reload}
11:49 honestly so that's the problem
11:50 honestly which salt could have told me about with a little less prodding necessary >_>
11:51 evle joined #salt
11:55 honestly hmrrgh. cmd.wait doesn't get executed :|
11:58 honestly whelp, that one was an error on my part.
11:59 shorty_mu Hi folks, when running a command like "salt -C 'some-server*' pkg.list_upgrade' is it possible that only servers which have updates are returned? Default seems to be to return something for every server, even if there no updates.
12:00 OverLordCain joined #salt
12:01 honestly what exactly are you trying to achieve?
12:01 N-Mi joined #salt
12:02 shorty_mu honestly: Reducing the ouput. I want to see only servers which have updates (return something).
12:02 eliasp shorty_mu: --state-output=changes might be what you want…
12:02 eliasp shorty_mu: https://docs.saltstack.com/en/latest/ref/cli/salt.html#cmdoption-salt--state-output
12:02 shorty_mu state-output...? Never thought of that. Will give that a try.
12:03 honestly shorty_mu: also this: http://stackoverflow.com/questions/15953082/is-there-a-way-to-display-only-changes-and-errors
12:04 shorty_mu eliasp: Nope to stae_outptut=changes. I still get every hostname printed, even if there are no updates.
12:04 kinetic joined #salt
12:06 shorty_mu --state_output doesn't change the behaviour of "pkg.list_upgrade" at all.
12:06 edulix joined #salt
12:06 shorty_mu I know it works when running a "state.*" command.
12:07 yidhra_ joined #salt
12:07 otter768 joined #salt
12:10 Guest15 joined #salt
12:13 anmol joined #salt
12:14 tmclaugh[work] joined #salt
12:20 OverLordCain joined #salt
12:23 mohan__ joined #salt
12:26 EvaSDK joined #salt
12:27 mohan__ I am trying to download the content from s3, so I am using the s3 module to do it.But the file downloaded is empty can anyone help?
12:31 rotbeard joined #salt
12:33 nicksloan joined #salt
12:35 karlthane joined #salt
12:35 falenn joined #salt
12:39 thefish joined #salt
12:40 sbogg joined #salt
12:43 dthom91 joined #salt
12:43 kinetic joined #salt
12:47 cpowell joined #salt
12:48 lb joined #salt
12:50 BogdanR Can I use include in top.sls ?
12:53 jdubski joined #salt
12:57 shorty_mu left #salt
12:59 DammitJim joined #salt
13:01 averell joined #salt
13:03 subsignal joined #salt
13:07 mpanetta joined #salt
13:08 numkem joined #salt
13:09 pprkut is there a way I can use salt.utils.dictupdate.update from within a jinja2 template?
13:11 bhosmer joined #salt
13:15 andrew_v joined #salt
13:16 usernkey joined #salt
13:16 usernkey hi
13:17 usernkey I'm a new salt user coming from puppet
13:17 usernkey is there any equivalent of geppetto for salt
13:18 kinetic joined #salt
13:18 usernkey I'm looking but I did not find any so far
13:19 ubikite1 joined #salt
13:24 impi joined #salt
13:25 faliarin joined #salt
13:26 kaptk2 joined #salt
13:28 winsalt joined #salt
13:31 quix joined #salt
13:31 Ahlee No, just vim plugins
13:32 flou joined #salt
13:33 jeffpatton1971 joined #salt
13:34 pguinardco joined #salt
13:36 scoates joined #salt
13:38 LM317 joined #salt
13:39 usernkey too bad :) thx
13:40 LM317 hello! just to be sure, when i have something like this in my salt config: http://pastebin.ca/3219674 , production minions only get production files, but development minions would get files from all three roots, whereas files with the same name from development take precedence over ones from production, right?
13:44 edulix joined #salt
13:44 BogdanR Can someone have a look at this issue: https://github.com/saltstack/salt/issues/28289 ?
13:44 perfectsine joined #salt
13:46 babilen usernkey: What does geppetto do in puppet?
13:46 colegatron joined #salt
13:47 OverLordCain joined #salt
13:48 colegatron left #salt
13:48 racooper joined #salt
13:48 colegatron joined #salt
13:49 usernkey it is integrate  with git
13:49 OverLordCain joined #salt
13:49 usernkey syntax highlighting
13:49 breakingmatter joined #salt
13:49 usernkey syntax check
13:50 usernkey autocomplete
13:50 usernkey text editor gui
13:51 nkuttler usernkey: hm, salt is mostly yaml with jinja mixed.. not sure about specific plugins
13:52 nkuttler but you probably want to disable yaml highlighting, that regularly killed my cpu..
13:52 kinetic joined #salt
13:53 usernkey It worked quite good  by my experience and very handy
13:54 usernkey better of vim if you worked on  large project
13:54 usernkey s
13:54 timoguin joined #salt
13:55 TyrfingMjolnir joined #salt
13:55 jdesilet joined #salt
13:56 DammitJim left #salt
13:56 DammitJim joined #salt
13:57 colegatron I have a lot of template files using jinja variable replacement and a pillar file with the variables used in those templates. I am going to use them for my servers with salt states, but I have to send to a remote dev team the templates with the variables replaced in them to they can work locally.
13:57 tapoxi joined #salt
13:58 colegatron Is there someway to do a muti-file multi-variable replacement with salt? (or python+jinja)
14:01 furrowedbrow joined #salt
14:02 tapoxi left #salt
14:05 spiette joined #salt
14:06 hasues joined #salt
14:06 hasues left #salt
14:06 impi joined #salt
14:06 dyasny joined #salt
14:08 otter768 joined #salt
14:09 teebes joined #salt
14:12 Brew joined #salt
14:14 timoguin_ joined #salt
14:17 zmalone joined #salt
14:18 edulix joined #salt
14:19 orionx joined #salt
14:21 murrdoc joined #salt
14:21 rdas joined #salt
14:25 honestly colegatron: make a "localhost" minion and deploy files to it
14:25 honestly that's the stupid and simple solution :)
14:26 colegatron does salt recognizes site.some.other.route.variable like variables in the yaml?
14:27 kinetic joined #salt
14:28 murrdoc joined #salt
14:29 sroegner joined #salt
14:33 timoguin joined #salt
14:34 colegatron honestly: do you mean I can simply write in the template {{ what.ever.variable }} and salt will replace it directly?? I thought salt do not resolve the dot concatenated variables
14:34 anotherZero joined #salt
14:34 honestly colegatron: uh what
14:34 honestly colegatron: let me pastebin a mildly complex config file template for you ;)
14:34 bastion1704 joined #salt
14:35 colegatron https://paste.debian.net/318160/
14:35 honestly http://ix.io/lD2/jinja
14:36 honestly you need to access the variables properly
14:36 bangir joined #salt
14:36 honestly either access pillar directly from your template
14:36 murrdoc joined #salt
14:36 honestly or inject pillar content into the template context
14:40 colegatron honestly: as you can see, I'm fairly new to saltstack.. :-/  I am provisioning a couple of servers now with it, but I can't see that easy to do that :-(
14:42 honestly colegatron: read this: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.managed
14:42 honestly err, start reading at the top
14:43 lexter joined #salt
14:44 honestly and this: https://docs.saltstack.com/en/latest/ref/states/vars.html
14:44 yidhra_ https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.managed
14:45 honestly yeah i just linked that.
14:45 OliverUK Hiya, doing reading on how Salt can help me but a question has come up on something I have read.  Can Salt monitor the *version* of a file on lots of hosts, when one host has a newer version all of the rest of the hosts are told to update?
14:46 OliverUK *version* can be anything, filename, date, some string inside it etc
14:46 OliverUK Thanks in advance :-)
14:48 colegatron honestly: tnx. I am currently using some variable replacements with {{ salt['pillar.get']('key1:key2:key3', 'failover_value') }} but I can't see any example using plain {{ key1.key2.key3 }}
14:48 rotbeard joined #salt
14:50 adelcast1 joined #salt
14:51 _JZ_ joined #salt
14:52 otter768 joined #salt
14:52 adelcast1 joined #salt
14:53 ALLmightySPIFF joined #salt
14:55 dthom91 joined #salt
14:55 deus_ex joined #salt
14:55 drwx joined #salt
14:55 drwx joined #salt
14:56 tanta_g joined #salt
14:56 mage_ what's the "best" approach for: "I would like the local IP address of the machine on which the sls is deployed" .. ?
14:57 mage_ a custom pillar which check the local ifs + check ip ?
14:57 kinetic joined #salt
14:58 mage_ s/pillar/grain
14:58 honestly colegatron where are the variables supposed to come from?
14:59 honestly mage_ you already have that in grains
14:59 Akhter joined #salt
14:59 mage_ yep
14:59 honestly where do you want the ip address to go?
14:59 riftman joined #salt
15:00 mage_ in a jinja template
15:00 honestly colegatron: what is this variables.yml file?
15:00 DammitJim joined #salt
15:00 tapoxi joined #salt
15:00 colegatron honestly: is is a pillar file
15:00 honestly okay
15:01 honestly to get values out of the pillar you need to get them from the pillar
15:01 honestly I'm not sure if pillar.key1.key2 would work
15:01 honestly but it *should*
15:01 tapoxi hi everyone, trying to learn salt-ssh. I'd like to ssh into my existing minions to turn them back on after a minion upgrade (d'oh!) but it seems I can't target everything in the cache. how do I use this? salt-ssh -i --roster cache '*' --user=root --askpass service.available salt-minion
15:02 honestly it's not the recommended way to access the pillar but if that's what you want...
15:02 mage_ maybe I could just use __salt__['grains.get']('ipv4:0')
15:02 colegatron honestly: yup, as per your example I think the thing is to set the variables in the right context. what by other way I do not know how to do it, honestly :-)
15:02 honestly mage_ yes, that should work
15:02 rdas joined #salt
15:03 honestly colegatron: yes, I've taken to using context everywhere
15:03 honestly almost none of my template files access the pillar directly
15:03 Akhter joined #salt
15:03 colegatron honestly: mmmm "using context everywhere" not sure if I understand what you mean
15:03 mage_ honestly: same here, it's the first one
15:04 mage_ maybe I could wrap this in a function
15:05 honestly mage_ why? as I said, where do you want the ip to go?
15:05 numkem joined #salt
15:05 honestly you just want salt to tell it to you?
15:05 colegatron I think I've read 'context' somewhere in the doc, but not sure if it is something about salt or about python itself, googling.
15:05 mage_ honestly: I'm generating a Paste deploy file for Pyramid
15:05 honestly colegatron it's a feature of the file.managed state
15:06 honestly mage_ so just put {{ __salt__['grains.get']('ipv4:0') }} into your template?
15:06 mage_ so it must go in the [server:main] section
15:06 mage_ yep that's what I plan to do :)
15:06 honestly good then :P
15:07 colegatron honestly: yup, to override the context, but my doubt is 'what is the context and where it comes from?' (sorry, maybe it is a too simple python question)
15:07 mage_ except that all my config is already wrapped in a webapp_config() function
15:07 mage_ to keep my template "clean"
15:07 honestly colegatron: this is the statefile that uses the template I pasted earlier: http://ix.io/lD5/jinja
15:11 chiui joined #salt
15:12 clintberry joined #salt
15:12 otter768 joined #salt
15:13 debian112 joined #salt
15:13 RedundancyD joined #salt
15:14 sdm24 joined #salt
15:14 colegatron honestly: so, afaik, your {{ salt['pillar.get']('keepalived') }} is a structure like my 'site' in https://paste.debian.net/318160/  is that right?
15:15 tanta_ge joined #salt
15:16 colegatron sorry, afaik/afaiu
15:21 honestly yeah
15:24 arthurlutz joined #salt
15:24 arthurlutz any idea when 2015.8.1  https://docs.saltstack.com/en/latest/topics/releases/2015.8.1.html will be released ?
15:24 zmalone it's already released arthurlutz
15:24 arthurlutz zmalone: missing on pypi and debian/ubuntu packages
15:25 zmalone https://repo.saltstack.com/apt/ubuntu/ubuntu14/2015.8/
15:25 zmalone https://repo.saltstack.com/apt/debian/2015.8/
15:25 anmol joined #salt
15:25 merlin` zmalone: http://repo.saltstack.com/apt/debian/latest/
15:25 merlin` # apt-cache policy salt-common
15:25 merlin` salt-common: Installed: 2015.8.0+ds-2 Candidate: 2015.8.1+ds-1
15:25 jfindlay arthurlutz: that would be my fault, just a second
15:26 arthurlutz zmalone: am pointing to http://repo.saltstack.com/apt/ubuntu/ubuntu14/
15:26 arthurlutz https://pypi.python.org/pypi/salt points to 2015.8.0 too
15:26 zmalone arthurlutz: they changed the repo paths, so that now 404s if it's your repo
15:26 arthurlutz even if 2015.8.1 exists
15:26 zmalone you need /apt/ubuntu/ubuntu14/latest or /apt/ubuntu/ubuntu14/2015.8
15:27 zmalone look in http://repo.saltstack.com/apt/ubuntu/ubuntu14/2015.8/
15:27 zmalone there is no 2015.8.0 in those repos now
15:27 TooLmaN joined #salt
15:27 jfindlay arthurlutz: https://pypi.python.org/pypi?name=salt&version=2015.8.1&:action=display
15:28 arthurlutz zmalone: got it
15:28 zmalone unfortunately it wasn't really announced in advance.
15:28 Heartsbane joined #salt
15:29 arthurlutz zmalone: any reason not to have a redirect ?
15:29 zmalone I have no idea what went into that thought
15:30 zmalone (I'm not a saltstack employee, I just live with their decisions and don't complain too much about my free software)
15:30 colegatron honestly: tnx for your help.
15:31 colegatron every day I am more sure saltstack was the right election. his community is awesome.
15:31 flou joined #salt
15:33 pravka joined #salt
15:37 winsalt is anyone here running 2015.8 on windows 2012R2?
15:38 alemeno22 joined #salt
15:42 jdesilet joined #salt
15:43 jeffpatton1971 joined #salt
15:43 dthom91 joined #salt
15:44 RedundancyD joined #salt
15:45 flou joined #salt
15:51 stevednd joined #salt
15:52 sirex joined #salt
15:52 kinetic joined #salt
15:53 yuhl_work___ joined #salt
15:53 yuhl_work___ hello, I'm unable to use ipv6 on salt stack
15:53 sirex left #salt
15:55 jfindlay arthurlutz: I don't really like the current setup either, once our packaging processes settle down, we will revisit the repo paths and setup something more stable and tenable
15:57 arthurlutz jfindlay: zmalone: thanks for the explanations, hope it stabilizes ;-)
15:58 jeffpatton1971 joined #salt
16:03 edulix joined #salt
16:04 flou joined #salt
16:06 flou1 joined #salt
16:07 tapoxi left #salt
16:08 pravka joined #salt
16:08 shadowbeast joined #salt
16:12 merlin` it's normal when setup.py test fail on fresh devlop branch?
16:14 dthom91 joined #salt
16:14 bhosmer joined #salt
16:15 TranquilityBase joined #salt
16:15 meye1677 joined #salt
16:17 fredvd joined #salt
16:17 rwilliams joined #salt
16:18 rm_jorge joined #salt
16:20 bhosmer joined #salt
16:23 jalbretsen joined #salt
16:24 aparsons joined #salt
16:26 drwx joined #salt
16:26 drwx joined #salt
16:28 alemeno22_ joined #salt
16:29 DammitJim joined #salt
16:29 jemejones joined #salt
16:29 mage_ is it possible when I execute a state file to have some "progress output" instead of all at once at the end ?
16:30 wendall911 joined #salt
16:33 dthom91 joined #salt
16:33 rwilliams Has anyone here used the `cabal` states successfully?
16:36 meye1677 joined #salt
16:36 malinoff joined #salt
16:37 sgargan joined #salt
16:37 tanta_g joined #salt
16:38 ajw0100 joined #salt
16:38 bastion1704 joined #salt
16:38 jeffpatton1971 joined #salt
16:40 robawt joined #salt
16:41 flou joined #salt
16:41 sgargan joined #salt
16:43 jdesilet joined #salt
16:45 sgargan joined #salt
16:45 venu0336 joined #salt
16:46 writtenoff joined #salt
16:46 impi joined #salt
16:47 RandyT_ winsalt: if you are asking if anyone has deployed 2012R2 with 2015.8, I can share that I am not able to. Only 2008 servers.
16:47 RandyT_ winsalt: this seems to be an issue with winexe binary's ability to communicate with 2012 server
16:48 jfindlay winsalt: I've tested 2015.8 on 2012R2
16:48 RandyT_ jfindlay: what is solution to getting winexe to communicate with the 2012 servers?
16:49 chiui joined #salt
16:50 RandyT_ and to be more specific, this would be to deploy winserver 2012 in AWS.
16:51 jfindlay RandyT_: I'm not sure, but I know twangboy was working on an issue related to that
16:51 Ahlee ext_pillar, i have a nested pillar currently. Better to do pillar.get('foo').get('bar'), or to pull it out of __salt__ with __salt__['pillar.get']('foo:bar') ?
16:51 jfindlay I personally was doing a manual minion install
16:52 jfindlay winsalt, RandyT_: https://github.com/saltstack/salt/issues/21256
16:52 bhosmer joined #salt
16:52 jfindlay I think the issue there is that RHEL/CentOS don't ship a new enough version of winexe to work with the newer windowzen
16:53 RandyT_ jfindlay: yes, 2015.8 minion code runs fine. Deployment does not.
16:53 RandyT_ jfindlay: that is my guess regarding the age of winexe. I am at this moment compiling winexe for centos to see if this solves the issue.
16:54 breakingmatter joined #salt
16:54 baweaver joined #salt
16:57 tercenya_ joined #salt
17:00 quix_ joined #salt
17:02 RandyT_ jfindlay: winsalt I think the issue is different from the referenced github issue. I have no problem provisioning Win 2008 servers. The problem occurs when I replace the image with a 2012 server. Nothing else changing in my setup.
17:02 RandyT_ Will see if I can get this newer binary built with Samba4 code.
17:06 winsalt I am using 2012R2 in vmware, I dont have problems with installing salt.  The bug I am looking into now is the win_pkg module failing to identify 64bit registry entries.  Does a pkg.list_pkgs() correctly return all installed software on your 2012 setup?
17:07 jfindlay winsalt: #28218?
17:08 RandyT_ winsalt: I cannot attest to the accuracy just yet, but I do get a listing from 64bit servers running the minion.
17:08 jfindlay where is saltbot when you need it?
17:08 ajw0100_ joined #salt
17:08 jfindlay https://github.com/saltstack/salt/issues/28218
17:08 RandyT_ Working on this actively through the week on the windows component of my deployment
17:09 bhosmer joined #salt
17:10 Grokzen joined #salt
17:14 winsalt yeah jfindley, its that problem.  Something is funky with the pywin32 api  I think
17:15 jbub joined #salt
17:15 winsalt list_pkgs() only returns 32bit applications, which causes pkg.install to fail for 64bit software
17:16 jfindlay winsalt: you're welcome to comment there if you have anything to add
17:16 Grokzen hi. have anyone noticed that file.comment & file.uncomment changes the file permission of the files it edits?
17:17 jfindlay Grokzen: I would file a bug on that if you have a reproducible test case
17:19 * Heartsbane is looking forward to 2015.8.2
17:21 winsalt I posted that issue, I was trying to get some second opinions on whether it is a bug or not.
17:21 traph joined #salt
17:22 dendazen joined #salt
17:22 zmalone Grokzen: that sounds pretty buggy, assuming nothing else changed
17:23 Grokzen zmalone, y, we changed from 2015.5.2 to 2015.5.6 and it started to appear
17:23 Grokzen a file that had 440 permission do have 644 after highstate
17:23 dendazen hey guys, is it possible in salt to parse cli arguments and make them pillars?
17:24 Grokzen and it is only file.comment & file.uncomment that touches that file
17:24 zmalone oh, that could be the result of an old bug
17:24 quix joined #salt
17:24 Grokzen zmalone, do tell :P
17:24 jfindlay dendazen: an easy way to provide pillar data on the command line is `salt minion state.apply my_state pillar="secret: 'too many'"`
17:25 zmalone Grokzen: is it 440 or 420 permissions?
17:25 Grokzen 440
17:25 dendazen wow, ok.
17:25 zmalone https://github.com/saltstack/salt/blob/develop/doc/topics/troubleshooting/yaml_idiosyncrasies.rst#integers-are-parsed-as-integers
17:25 Grokzen /etc/sudoers file
17:25 zmalone okay, that's different
17:25 OliverUK Hiya, not to be impatient but can anyone answer my question from earlier on today? :-)
17:26 Akhter joined #salt
17:26 ubikite joined #salt
17:26 ubikite joined #salt
17:27 Grokzen zmalone, that would only apply to file.managed where you can specify the mode? in file.uncomment it do not have a mode variable or something where you specify what permission to have the file in
17:27 ubikite joined #salt
17:27 ubikite joined #salt
17:27 jfindlay OliverUK: if by version you mean any of those attributes you mentioned, then I think that should be possible, it is only a matter of setting up a state to look at the things you need
17:28 OliverUK jfindlay: Thanks, I am going to be testing Salt soon I think, it may just solve a few headaches :-)
17:28 jfindlay OliverUK: no problem, ping me if you have further questions
17:29 OliverUK jfindlay: So to confirm a later version from one minion can set some variable somewhere that sets a condition for a state (or something like that, I am not too confident with salt terminology yet :-P)
17:30 OliverUK *that is used in a condition for a state
17:30 iggy generally, you keep your latest version of the config file in your state tree, and salt just puts that in place
17:31 ViciousLove joined #salt
17:31 sgargan joined #salt
17:31 jfindlay it depends on how you want to architect your system, really.  You could create a custom grain that tells you information about the state of the hosts file on that minion
17:32 jfindlay or you could revision the files and keep them in a git repository
17:32 OliverUK Thanks :-)
17:32 OliverUK GTG now but thank you :-)
17:32 jfindlay sure
17:34 ubikite hi, i'm using salt 2014.1.13 (Hydrogen) and salt-ssh gives me this error: KeyError: 'extension_modules'.
17:35 iggy holy old
17:35 ubikite it's old version?
17:35 sdm24 hey jfindlay: I saw you just updated https://github.com/saltstack/salt/issues/28268 (updating docs to include nodegroup targetin in Jina). I'm currently working on it, but I'm not sure how applicable it is to update the docs. I'll explain more in a comment on the issue
17:36 zmalone ubikite: hard to say, docs are no longer online for 2014.1.
17:36 iggy ubikite: yeah, 2014.1 is almost 2 years old (in salt terms, that's ancient)
17:36 zmalone Currently salt is 2015.5 and 2015.8
17:37 ubikite ok, thanks.
17:37 Fiber^ joined #salt
17:37 jfindlay sdm24: sounds good, thanks
17:40 dendazen and if I use salt minion state.apply my_state pillar="secret: 'too many'
17:40 dendazen how can use that pillar 'secret'?
17:40 dendazen just in any sls file reference to it as 'secret' and it will be available at run time?
17:42 jfindlay dendazen: you can reference pillar data in an sls file with jinja, `{% set data = pillar.get('secret') %}` and then `password: {{ data }}`
17:44 dendazen ok would i be able to do something like this
17:45 dendazen if {{data}} == 'prod' then cmd.run blah 'whatever relevant to "prod" args' elif {{data}} == 'dev' then cmd.run blah 'whatever relevant to "dev" args'
17:45 dendazen ?
17:46 seweryn joined #salt
17:46 dyasny joined #salt
17:47 flou joined #salt
17:50 troyready joined #salt
17:53 mway joined #salt
17:53 tanta_ge joined #salt
17:53 mway for salt:// paths in reactor, does it use file_roots or does it default to /srv/salt?
17:55 iggy mway: it should use file_roots
17:56 mway thought so. alright, problem must be elsewhere, -ldebug on master shows it gathering reactor events but not firing based off of sls defined in master.d/reactor.conf
17:56 iggy did you restart the master?
17:57 mway yup. running both in foreground atm, specifically trying to do key accept magic and it just complains about the cached key - master sees the event being fired but doesn't respond to it
17:57 pravka joined #salt
17:57 mpanetta joined #salt
17:59 SheetiS1 joined #salt
17:59 iggy best I can suggest is paste boiled down configs to gist and maybe someone spots something
17:59 mway np, I will if I don't find something with a little more digging
18:00 mway unrelated, dockerio stopped being available randomly, docker-py==1.2.3 is installed (running Lithium), just 'module dockerio is not available' - nuked the cache, restarted, foreground, virtualenv/system, etc, no dice
18:01 mpanetta joined #salt
18:03 ubikite joined #salt
18:03 kinetic joined #salt
18:08 Akhter joined #salt
18:10 stevednd anyone have any resources on how to generate a file for use with iptables-restore? the builtin salt states are absurdly slow when there are a bunch of rules. my firewall states take about 5 minutes to run.
18:11 stevednd the top matter that iptables-save generates is the part I stumped how to generate automatically
18:11 RandyT_ jfindlay: winsalt fwiw, fresh build of winexe makes it now possible to deploy Winserver 2012 R2
18:11 jfindlay RandyT_: nice
18:12 Brew joined #salt
18:14 RandyT_ jfindlay: also just updated that issue you referenced to add that to the thread in case that helps anyone else.
18:15 Akhter joined #salt
18:17 pcn Has anyone used salt-cloud to tag ec2 instances at launch before the bootstrap launches?
18:18 jfindlay thanks, RandyT_
18:19 pcn Ah, looks like "tag" not "tags".
18:21 Ahlee stevednd: couldn't you just iptables-save > my_rules.txt, file.managed that, and then iptables-restore that file?
18:22 kinetic joined #salt
18:24 zmalone Ahlee: I work for a place that does that, although it's a lot kludgier than doing something like "If I'm a web host, use iptables.foo to make sure port 80/443 is open!"
18:25 ajw0100 joined #salt
18:26 dthom91 joined #salt
18:27 stevednd Ahlee: yes, but that doesn't help for adding/generating new rules when other machines are added. I'm just really not exactly sure what to make of all the bracketed numbers, and *nat, *mangle, etc...
18:28 quantum-x joined #salt
18:29 quantum-x Hey all. Quick question - is it possible / how would I call a standard command (ie, salt set_job) from a module ?
18:29 Brew joined #salt
18:31 jemejones has anyone used salt on a windows host to work with vagrant VMs?
18:34 StolenToast joined #salt
18:35 StolenToast how can I check for the version of a package in a state?
18:35 StolenToast different configs for different versions
18:41 buMPnet joined #salt
18:41 breaking_ joined #salt
18:45 ekkelett joined #salt
18:45 ekkelett joined #salt
18:46 solidsnack joined #salt
18:48 buMPnet joined #salt
18:49 impi joined #salt
18:50 quix joined #salt
18:51 ajw0100 joined #salt
18:52 jeffpatton1971 joined #salt
18:56 kinetic joined #salt
18:59 orionx_ joined #salt
19:01 rvankleeck joined #salt
19:01 rvankleeck I'm getting kind of a weird error using git_pillar where it says "37 conflicts prevent checkout" even though it is the initial pull
19:03 zmalone initially you clone, so it's possible something has changed since that clone.
19:03 zmalone git status should tell you what's up.
19:03 zmalone or maybe local files in the directory you are trying to clone to?
19:04 rvankleeck zmalone: this happens when I initially install salt-master, and seems to only happen on CentOS 7
19:04 rvankleeck works fine with CentOS 6.7
19:05 ubikite joined #salt
19:05 ubikite joined #salt
19:06 k00l joined #salt
19:06 k00l hey everyone, some salt cloud questions.  how can i use teh API to get teh cloud to kick off a request to spin up a server ?
19:07 k00l i cant seem to find any API commands that speak to salt-cloud. am i just looking in the wrong area ?
19:07 cyborg-one joined #salt
19:08 penguin_dan joined #salt
19:09 nikogonzo k00l: http://salt-cloud.readthedocs.org/en/latest/topics/aws.html#cloud-profiles seems like it's what you want
19:09 penguin_dan joined #salt
19:11 k00l nikogonzo: unless i missed something (which is very possible) that artical speaks about cloud profiles, and im looking for a connection to the salt-cloud and teh salt-api.
19:11 opensource_ninja joined #salt
19:12 ajw0100_ joined #salt
19:12 baweaver joined #salt
19:12 pravka joined #salt
19:13 rvankleeck Looks like going into /var/cache/salt/master/git_pillar and doing 'git pull origin <branch>' and then 'git checkout <branch>' worked
19:13 racooper joined #salt
19:15 jeffpatton1971 joined #salt
19:16 vaganych joined #salt
19:17 kinetic joined #salt
19:18 traph joined #salt
19:18 ubikite joined #salt
19:19 ubikite joined #salt
19:19 nikogonzo k00l: so you mean use salt-api to drive salt-cloud? hrm i don't know if it's abstracted in salt-api; i'll defer to someone else - sorry :( alternatively you might want to look up the client api and make your own caller. i think salt/salt/cloud/cli.py has a good example
19:20 k00l nikogonzo: ok, thanks mate ill look into it.
19:20 vandemar joined #salt
19:21 jaguar_ joined #salt
19:22 trph joined #salt
19:24 flou joined #salt
19:25 baweaver joined #salt
19:29 trph joined #salt
19:29 kinetic joined #salt
19:31 KyleG joined #salt
19:31 KyleG joined #salt
19:31 Akhter joined #salt
19:32 vandemar joined #salt
19:32 perfectsine joined #salt
19:32 tanta_ge joined #salt
19:34 vaganych left #salt
19:40 kinetic joined #salt
19:42 mrtrosen joined #salt
19:48 keimlink joined #salt
19:52 dan_johnsin joined #salt
19:53 ajw0100 joined #salt
19:56 DammitJim joined #salt
19:57 breakingmatter joined #salt
19:59 jimklo joined #salt
19:59 meye1677 joined #salt
19:59 quix_ joined #salt
20:00 tanta_g joined #salt
20:03 subsigna_ joined #salt
20:03 iggy k00l: it's probably easier to call the cloud modules/states than to talk to salt-cloud itself (they all use the same code in the background, it's just a different way of addressing
20:04 k00l iggy: yes, i wa sthinking that i may have to have states that spool my rigs iup and then use mine to fetch and finalize the boxes/roles
20:06 pravka joined #salt
20:06 dendazen how would one use state.apply in conjunction with state.sls?
20:06 subsignal joined #salt
20:07 iggy state.apply replaces state.sls
20:07 larsfronius joined #salt
20:08 cornfeedhobo hello. i am having the oddest issue, and it must be something simple. i have a state file that uses 'rsync.rsync' and i can see that i have /usr/lib/python2.7/site-packages/salt/modules/rsync.py on my system, and yet i still receive KeyError: 'rsync.rsync'. any ideas what i could be messing up on?
20:08 dendazen well i want to run one state sls file
20:08 iggy cornfeedhobo: rsync is a module, not a state
20:08 iggy dendazen: state.apply one.state
20:09 dendazen oh ok, thanks iggy.
20:09 iggy dendazen: if you don't specify anything it's state.highstate, if you do, it's state.sls
20:10 cornfeedhobo iggy: yes, i believe that is how i under stand it. in a state file, i am trying to use that module, and i receive said error.
20:10 dendazen oh that's good to know as well
20:10 iggy cornfeedhobo: you can't call modules directly in state files, you have to use salt.states.module.*
20:11 cornfeedhobo iggy: oh
20:12 edulix joined #salt
20:12 cornfeedhobo iggy: how do i differentiate? there are numerous file.* examples, and it would seem like rsync was no different.
20:12 Guest25336 joined #salt
20:12 dthom91 joined #salt
20:13 cornfeedhobo hmm, nvm https://docs.saltstack.com/en/2015.5/ref/states/all/index.html
20:13 cornfeedhobo iggy: thanks
20:13 iggy https://docs.saltstack.com/en/latest/salt-modindex.html
20:13 iggy is helpful too
20:14 cornfeedhobo good to know.
20:14 iggy basically everything in salt.states.*.* is what you put in sls files
20:14 cornfeedhobo gotchya. thanks for clarifying that
20:14 iggy everything in salt.modules.*.* is what you run on the command line
20:14 cornfeedhobo oohhh
20:14 cornfeedhobo that makes sense. okay thank you again!
20:15 iggy but as I said before, you can use salt.states.module.* to run modules in states
20:15 iggy so... exceptions/rules/etc...
20:16 cornfeedhobo oh, i misunderstood your meaning. i will check that out
20:18 cornfeedhobo i see. okay
20:20 baweaver joined #salt
20:25 edulix joined #salt
20:26 dendazen salt uat-dada.sec1.example.com state.apply packages.spacewalk_client  pillar="env: 'prod'" pillar="user: 'jenkins'" pillar="password: 'password'"-bash: !'": event not found
20:26 dendazen this doesn't work
20:27 iggy pillar doesn't work like that
20:28 jfindlay dendazen: you need to make sure the pillar data is formatted either as valid yaml/json or a python dictionary
20:28 iggy you specify pillar once, but you make it a dict if you need multiple values set
20:28 dendazen oh i see.
20:28 jfindlay also what iggy says
20:28 dendazen and when it says
20:29 dendazen uat-dada.sec1.example.com:
20:29 dendazen "state.apply" is not available.
20:29 dendazen what does this mean?
20:29 iggy the minion is old
20:29 jfindlay state.apply was added in 2015.5 or 2015.8, I don't remember which
20:29 Eugene It means I need a beer
20:30 jfindlay https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.state.html#salt.modules.state.apply
20:30 jfindlay 2015.5.0
20:31 dendazen oh, that is not good.
20:32 iggy use state.sls instead
20:32 iggy or upgrade the minion
20:33 iggy state.apply _literally_ does "if args state.sls, else state.highstate"
20:34 dendazen oh ok
20:34 dendazen so i can provide state.sls with pillar= argument
20:34 iggy yes
20:37 pravka joined #salt
20:38 dyasny joined #salt
20:38 edulix joined #salt
20:39 dendazen and can i do something like this?
20:39 dendazen {% if {{ our_env }} == 'prod' %}
20:39 dendazen where {% set our_env = pillar.get('env') %}
20:39 baweaver joined #salt
20:41 falenn joined #salt
20:42 StolenToast how can I assign a different config file in a state based on the version of an installed package?
20:42 sgargan joined #salt
20:42 doriftoshoes joined #salt
20:42 Mate dendazen:
20:42 Mate 1156 <Mate> rotbeard: yes, but without the {{}}
20:42 Mate 1156 <Mate> like in a python code
20:43 dendazen just {% if our_env  == 'prod' %}?
20:44 lpmulligan joined #salt
20:44 Mate yes
20:45 toddnni_ joined #salt
20:47 jeffpatton1971 joined #salt
20:47 dan_johnsin joined #salt
20:47 iggy dendazen: I'd avoid using 'env' (it could get easily confused with Salt's built-in enviroments)
20:47 teebes joined #salt
20:48 dendazen Thank you.
20:48 iggy dendazen: {% if salt['pillar.get']('companyenv') == 'prod' %}
20:48 ViciousLove StolenToast, if you want to get down and dirty, you can use the "onlyif" requisite to test the pkg version. https://docs.saltstack.com/en/latest/ref/states/requisites.html#onlyif
20:49 dendazen then in this case i do not need {% set blah ... %}
20:49 ViciousLove StolenToast: If you are specifying the version in your state, then thats even easier to handle with some if statements
20:49 StolenToast I know the version numbers
20:49 dendazen if i am using pillar.get
20:49 ViciousLove Are you specifying which pkg version to install?
20:50 StolenToast in the future I will but right now I just need to match it to one of two versions and use a different conf
20:50 Akhter joined #salt
20:50 StolenToast two different versions for various support reasons
20:50 ViciousLove Then "onlyif" is your best bet. This debian based?
20:51 StolenToast centos
20:51 ViciousLove ah, then I can't help you the actual command :) good luck
20:51 StolenToast it should be the same, shouldn't it?
20:51 StolenToast salt should be a unified interface for both
20:51 StolenToast apt and yum
20:52 ViciousLove it is, but the "onlyif" uses an actual command line execution and checks the return status
20:52 StolenToast ahh, well that's no problem
20:52 StolenToast I'm a yum ninja
20:53 winsalt StolenToast, why dont you have the name for the file in the sls be a pillar value
20:53 StolenToast would it be a grain value?
20:53 StolenToast that's an idea
20:54 winsalt yeah grain or pillar would work i think
20:54 racooper joined #salt
20:54 StolenToast ok I'll try that
20:54 aidalgol joined #salt
20:54 flou joined #salt
20:55 winsalt you would just need a way to feed the package version into which value is chosen
20:57 kinetic joined #salt
20:58 MadHatter42 joined #salt
21:00 ilbot3 joined #salt
21:00 Topic for #salt is now Welcome to #salt | 2015.8.1 is the latest | Please use https://gist.github.com for code, don't paste directly into the channel | Please be patient when asking questions as we are volunteers and may not have immediate answers | Channel logs are available at http://irclog.perlgeek.de/salt/
21:02 dendazen So i created the state
21:02 dendazen https://gist.github.com/anonymous/045bde55aea96ae74024
21:03 dendazen but when i run it i get nothing on the last state in the state
21:03 dendazen it does all previous states
21:03 s_kunk joined #salt
21:05 sgargan joined #salt
21:06 sdm24 dendazen: what does "salt '*' pillar.get companyenv" give?
21:07 opensource_ninja joined #salt
21:10 dyasny joined #salt
21:12 dendazen after running that state?
21:13 sgargan joined #salt
21:13 jhauser joined #salt
21:14 dendazen weird it gives me hostname
21:14 dendazen maybe some collegues are using it somewhere.
21:16 sdm24 dendazen: I'm just thinking that maybe companyenv isn't set to prod, dev, or uat, so the state is ignoring the if statements and just finishing
21:16 dendazen yeah that what i said
21:16 dendazen when i ran your command
21:16 dendazen that shows me
21:17 dendazen that companyenv points to hostnames
21:17 rootchord joined #salt
21:18 rootchord what is the difference between community and enterprise?
21:18 rootchord feature-wise
21:20 zmalone How many hosts do you have?
21:20 zmalone Oh, sorry, thinking of chef "community", I don't usually hear of salt that way.
21:21 timoguin_ joined #salt
21:21 linjan joined #salt
21:22 sdm24 dendazen: can you post your pillar .sls file(s) that define companyenv?
21:22 edulix joined #salt
21:23 dendazen well actually i am defining those pillars in the shell with args
21:23 sdm24 oh ok
21:23 dendazen like this
21:24 dendazen salt -v  uat-dada.sec1.example.com state.sls packages.spacewalk_client  pillar=["companyenv: 'prod',user: 'jenkins',password: 'dada!'"]
21:24 dendazen but i think bash
21:24 dendazen fucking up my quoting to be honest
21:26 zmalone inline passwords in bash can make for problems
21:26 sgargan joined #salt
21:26 zmalone & etc.
21:29 dendazen i just do not want to save it in the sls file
21:29 dendazen as i store all salt in git
21:33 jdesilet joined #salt
21:34 winsalt debdazen, if it is worth the effort to you, you can encrypt passwords with gpg and save them in pillar files
21:34 zmalone I've gone down that road, there are some bugs that make it tough
21:35 zmalone https://github.com/saltstack/salt/issues/24556
21:35 zmalone if you pre-clean your passwords to avoid special characters, it can work
21:35 zmalone and if you don't mind gpg encrypting every single entry seperately
21:36 zmalone your pillars get *ugly* too
21:36 eliasp that's why I split my pillars into 2 repos… salt-pillars and salt-secret-pillars
21:36 eliasp salt-secret-pillars contains only GPG data
21:36 eliasp keeps the remaining pillars readable
21:37 eliasp so I just include foo.bar.secrets wherever I need it in the plain pillars
21:37 sdm24 I found a strange bug, has anyone else noticed this? When I do salt '*' pillar.ls, only about 60-75% of the minions return that they have anything, even  though I have a base: '*
21:38 sdm24 in my pillar/top. However, when I run "salt '*' cmd.run 'salt-call pillar.ls'", they all return with their proper pillars
21:38 sdm24 I just upgraded my master and some minions to 2015.8.1
21:40 sdm24 And for each minion that shows an empty pillar, in the master log file I get "Failed to checkout master from git_pillar remote 'master git@git.example:user/salt.git': remote ref does not exist", even though it works for the other minions. The minions that don't return anything are random
21:42 eliasp sdm24: I feel like I've seen this before…
21:42 edulix joined #salt
21:43 iggy rootchord: the web gui
21:44 subsignal joined #salt
21:45 ldelossa joined #salt
21:45 ldelossa Hey guys, quick question - what's the best way to control order within your state top.sls file
21:46 ldelossa Is it possible to make a state.sls file depend on the completion of a different state.sls file
21:46 eliasp ldelossa: sure, just "require: \n - sls: foo.bar"
21:47 ldelossa Okay perfect it's that simple
21:47 Corey What's the best way to test for a pillar value being set?
21:47 eliasp ldelossa: you'll have to include this SLS to be able to require it…
21:47 ldelossa salt '*' pillar.items ?
21:47 Corey {% if pillar['foo'] %} doesn't seem tow ork.
21:47 Corey ldelossa: Sorry, I meant in jinja for flow control in a state. :-)
21:48 ldelossa ohh in template
21:48 eliasp Corey: what about {% if 'foo' in pillar %}?
21:48 Corey It blows up at rendertime.
21:48 Corey Testing.
21:48 ldelossa try
21:48 ldelossa yeah corey has it
21:48 ldelossa {% if 'my_ssh_key' in pillar %} this is what I use
21:49 rootchord Iggy: really? all the features are the same otherwise?
21:50 eliasp ldelossa: well, I suppose you'll also get professional support
21:50 Eugene Oh, the web gui finally launched?
21:50 Eugene Man, it's been too long since I've paid attention
21:50 aparsons joined #salt
21:51 zmalone eliasp: saltstack will now sell support on the open source version.
21:51 murrdoc its $$ per minion
21:51 * murrdoc is poor
21:51 ldelossa elias, so if I have a state file say, configure_snmpd - which has a bunch of states into there to get snmpv3 configured. I then have a whole different install_packages.sls that needs to be ran first, Inside the configure_snmpd state I would be require: -n sls: install_packages.sls
21:52 eliasp ldelossa: leave off the .sls at the end, but that's it…
21:52 ldelossa okay perfect
21:52 ldelossa thanks a ton!
21:52 surge__ joined #salt
21:52 eliasp ldelossa: also: the name needs to be absolute, so this would assume install_packages.sls is located at the root of your repo/file_roots…
21:52 Gareth o/
21:52 eliasp ldelossa: otherwise use a full canonical name like net.snmp.install_packages or wherever your SLS is located
21:58 aparsons joined #salt
21:58 zmalone left #salt
21:59 shpoont joined #salt
22:00 dan_johnsin joined #salt
22:00 iggy rootchord: correct (afaik anyway, I welcome corrections)
22:02 baweaver joined #salt
22:04 jeddi joined #salt
22:04 breakingmatter joined #salt
22:06 surge__ Can I delay enabling a service until the end of a salt run? Similar to listening to config changes?
22:07 surge__ Collectd throws an error before I get a chance to add in my custom config.
22:07 sdm24 surge__: you want " - order: last" probably
22:07 surge__ It runs fine after the listen forces a service restart.
22:07 sdm24 https://docs.saltstack.com/en/latest/ref/states/ordering.html
22:07 surge__ Hm, I guess that’s the easiest way. Thought there might be another Salty way of doing that.
22:08 ekristen joined #salt
22:08 sdm24 you can use requires and watch_ins and things like that, but theres no reason to complicate it if its simple
22:08 sgargan joined #salt
22:08 eliasp surge__: the problem might be your package manager… many package managers/packages have the bad habit of running non-deterministic crap like postinst scripts etc, some of them (esp. on Debian/Ubuntu) attempt to start the service as part of the package installation/upgrade
22:09 larsfronius joined #salt
22:10 thalleralexander joined #salt
22:12 surge__ sdm24: Yep, that did it. No errors.
22:14 keimlink joined #salt
22:15 sdm24 glad to hear
22:16 perfectsine joined #salt
22:19 keimlink joined #salt
22:21 bhosmer joined #salt
22:24 sgargan joined #salt
22:27 sgargan joined #salt
22:28 dthom91 joined #salt
22:30 aparsons joined #salt
22:30 armguy Is there a way to run a specific state from a minion? I seem to be failing
22:34 ajw0100 joined #salt
22:34 kinetic joined #salt
22:35 enarciso joined #salt
22:35 jdesilet joined #salt
22:36 murrdoc salt-call state.sls lol.path.to.state
22:36 Tritlo left #salt
22:37 armguy hrm OK thanks murrdoc guess I have other issues :)
22:45 baweaver joined #salt
22:45 dthom91 left #salt
22:46 murrdoc :)
22:46 murrdoc we out here ot help, but we have bad jokes
22:47 Daemonik joined #salt
22:47 Daemonik Am attempting to use Salt-Cloud with Joyent, I get [ERROR   ] Failed to get the output of 'joyent.avail_sizes()': 'headers'
23:02 kinetic joined #salt
23:03 ekristen_ joined #salt
23:04 mosen joined #salt
23:05 deus_ex joined #salt
23:05 blue0ctober joined #salt
23:11 Nazca__ joined #salt
23:16 deus_ex joined #salt
23:16 thefish joined #salt
23:17 edulix joined #salt
23:22 breakingmatter joined #salt
23:28 cberndt joined #salt
23:40 sgargan joined #salt
23:44 dendazen joined #salt
23:46 solidsnack joined #salt
23:48 pravka joined #salt
23:49 dthom91 joined #salt
23:52 DammitJim joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary