Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2014-10-12

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

All times shown according to UTC.

Time Nick Message
00:00 pfallenop joined #salt
00:05 ajolo__ joined #salt
00:12 crane bbradley: babilen: no clue how but i fixed it. maybe there was a small typo or something else. i just rewritet the complete map.jinja file
00:14 bbradley what did you do differently?
00:15 crane i dont know. i just rewritet it step by step
00:23 crane bbradley: got another question. lets assume i would like to install with salt on two hosts openssh using that formula. how would i configure different config options in the pillar file for the hosts?
00:31 bhosmer joined #salt
00:32 invsblduck joined #salt
00:39 dude051 joined #salt
00:42 sunkist ,,
00:45 pfallenop joined #salt
00:56 kingel joined #salt
01:12 mechanicalduck joined #salt
01:14 n8n joined #salt
01:17 otter768 joined #salt
01:37 elfixit joined #salt
01:37 jalaziz joined #salt
01:45 sroegner_ joined #salt
01:47 klotho joined #salt
01:50 kedo39 joined #salt
02:04 cads joined #salt
02:08 CeBe1 joined #salt
02:15 klotho joined #salt
02:20 bhosmer joined #salt
02:40 Outlander joined #salt
02:45 kingel joined #salt
02:50 zartoosh joined #salt
02:55 rostam joined #salt
02:57 zartoosh joined #salt
03:05 schristensen joined #salt
03:08 StDiluted joined #salt
03:23 active8 joined #salt
03:24 ajprog_laptop joined #salt
03:31 nitti joined #salt
03:37 DaveQB joined #salt
03:46 sroegner_ joined #salt
03:47 thedodd joined #salt
03:49 n8n joined #salt
03:56 sunkist I put some stuff in pillar, then wrote a state to dump that stuff into a file, but the file stays empty.
03:58 sunkist When I run salt-call --local -l debug saltutil.refresh_pillar, I can see salt scanning/compiling top.sls and my pillar data.
03:58 sunkist But I don't see the data at all when I check pillar.items.
03:58 TheThing joined #salt
03:59 sunkist How should I debug this further?
04:09 bhosmer joined #salt
04:22 dccc__ joined #salt
04:34 kingel joined #salt
04:41 invsblduck joined #salt
04:57 UForgotten joined #salt
05:13 zartoosh joined #salt
05:16 rostam joined #salt
05:18 zartoosh joined #salt
05:20 zartoosh__ joined #salt
05:32 TheThing joined #salt
05:34 bhosmer joined #salt
05:34 kingel joined #salt
05:38 linjan joined #salt
05:47 sroegner_ joined #salt
05:52 n8n joined #salt
05:54 hardwire joined #salt
05:58 bhosmer joined #salt
05:58 scoates joined #salt
06:11 rostam joined #salt
06:14 zartoosh joined #salt
06:19 hardwire joined #salt
06:25 jchen joined #salt
06:26 ndrei joined #salt
06:26 Pixionus joined #salt
06:31 ajolo__ joined #salt
06:36 kingel joined #salt
06:46 rostam joined #salt
06:48 zartoosh joined #salt
06:51 zartoosh__ joined #salt
06:57 otter768 joined #salt
07:14 astol joined #salt
07:14 cberndt joined #salt
07:24 zartoosh__ joined #salt
07:26 hardwire joined #salt
07:38 rostam joined #salt
07:40 zartoosh joined #salt
07:43 mbaechtold joined #salt
07:43 invsblduck joined #salt
07:47 bhosmer joined #salt
07:48 sroegner_ joined #salt
07:58 cruatta joined #salt
08:12 ndrei joined #salt
08:24 kingel joined #salt
08:40 Katafalkas joined #salt
09:13 intellix joined #salt
09:22 mbaechtold left #salt
09:23 CeBe joined #salt
09:33 ndrei joined #salt
09:35 bhosmer joined #salt
09:36 bhosmer_ joined #salt
09:37 oyvjel joined #salt
09:40 thehaven joined #salt
09:42 agend joined #salt
09:48 invsblduck joined #salt
09:49 sroegner_ joined #salt
09:58 glyf joined #salt
10:01 agend joined #salt
10:04 viq joined #salt
10:04 viq joined #salt
10:05 oyvjel1 joined #salt
10:10 kingel joined #salt
10:11 viq joined #salt
10:12 thehaven joined #salt
10:16 kingel joined #salt
10:18 CeBe joined #salt
10:21 linjan joined #salt
10:49 invsblduck joined #salt
10:50 bhosmer joined #salt
10:52 __gotcha joined #salt
10:53 __gotcha Is there someone that has started to work on bootstrap for mac osx ?
11:01 intellix joined #salt
11:07 marv__ joined #salt
11:11 kingel joined #salt
11:21 bmcorser joined #salt
11:24 bhosmer_ joined #salt
11:36 duncanmv joined #salt
11:45 ingwaem joined #salt
11:49 nickjj are there any prebuilt modules or discovered patterns to solve this problem? generate random pw (if pw exists, skip this) -> store it on the master securely -> read it on minions when accessed
11:49 puddingMe joined #salt
11:49 sroegner_ joined #salt
11:49 madpickle left #salt
11:52 eliasp nickjj: "secure storage" are pillars provided by the master, so you'd have to generate them in the pillars where needed
11:53 eliasp nickjj: if you have large amounts of passwords to be generated, you could automate the generation of pillars somehow, use external pillars etc.
11:53 eliasp nickjj: if it's just a handful of passwords, generate them manually (using pwgen or something similar) and copy'n'paste them into your pillars
11:53 nickjj eliasp: i have about 6-7 passwords, self signed ssl certs, ssh keypairs etc
11:53 eliasp yeah, ok… if it's just 6-7 … just manually copy'n'paste them into your pillars
11:54 eliasp automating it is probably worth it >50
11:54 nickjj hmm, but then they are sitting there in plain text
11:54 eliasp nickjj: starting with 2014.7, Pillars can be GPG encrypted
11:54 eliasp nickjj: http://docs.saltstack.com/en/latest/topics/releases/2014.7.0.html#gpg-renderer
11:54 nickjj eliasp: i am using the latest development build -- where did you see that?
11:55 nickjj that's interesting
11:55 eliasp nickjj: see also: https://github.com/saltstack/salt/blob/develop/salt/renderers/gpg.py
11:56 nickjj this might also be a non-issue in salt too, i'm coming at this from an ansible POV where in a lot of cases you'd just run your commands from a workstation
11:57 nickjj i guess with salt you would trust anyone with access to the master?
11:57 eliasp nickjj: you necessarily have to trust everyone with access to the master… the master is in full control of every minion connected to it
11:58 nickjj yeah
11:58 eliasp nickjj: so securing your master should be your highest priority
11:58 eliasp also when using GPG encrypted pillars, the master will still hold (at least in memory) the private key required to decrypt the pillars
11:59 eliasp so the access to the master has to be very very limited…
11:59 nickjj ah, so it doesn't get cleared after the run? it would be saved in an agent?
12:00 eliasp well, even if the agent holds it, the agent's allocated memory still contains the private key
12:00 eliasp so if I have access to /dev/mem on the master, I'll be able to read your private key
12:00 nickjj i mainly just want to be able to commit my pillar data to git without worries but
12:00 nickjj i still need to investigate forms of external pillar sources
12:04 nickjj thanks a lot for that gpg source link tho -- this should be good for now
12:14 darrend joined #salt
12:14 SheetiS joined #salt
12:33 eliasp any Jinja ninjas around who could tell what's wrong here?: http://pastie.org/9641767
12:46 Katafalkas joined #salt
12:48 eliasp ok, solved… .update({key: "value"}) instead of .update(key="value")
12:53 invsblduck joined #salt
12:59 kingel joined #salt
13:08 kusams joined #salt
13:12 PsionTheory joined #salt
13:13 bhosmer_ joined #salt
13:15 pdayton joined #salt
13:22 bhosmer joined #salt
13:23 darrend joined #salt
13:28 tmh1999 joined #salt
13:29 darrend joined #salt
13:30 tmh1999 joined #salt
13:35 darrend joined #salt
13:45 kusams joined #salt
13:50 sroegner_ joined #salt
13:52 zooz joined #salt
13:53 Katafalkas joined #salt
14:00 kingel joined #salt
14:13 astol joined #salt
14:16 linjan joined #salt
14:21 zooz joined #salt
14:27 puddingMe joined #salt
14:31 ndrei joined #salt
14:40 ingwaem joined #salt
14:50 bbradley nickjj: i experienced a bug with the GPG renderer. something about outputting an extra newline. currently using a state outside source control (i call it auth.sls) that has passwords in it. please mention if you get the GPG renderer working.
14:50 bbradley filed here: https://github.com/saltstack/salt/issues/16270
14:57 TheThing joined #salt
14:59 Katafalkas joined #salt
15:00 TheThing joined #salt
15:02 bhosmer_ joined #salt
15:04 cads joined #salt
15:10 astol joined #salt
15:13 Katafalkas joined #salt
15:20 httpdss joined #salt
15:28 deepz88 joined #salt
15:28 nickjj bbradley: ok, will do -- i'm not quite ready to tackle that yet, probably in the next few days
15:29 nickjj i'll post feedback in your issue if i experience the same thing
15:29 bbradley no worries, just wanted to give a heads up. was very sad that bug exists.
15:29 bbradley time, you know.
15:30 nickjj hopefully it gets patched soon, i'm reading your issue now
15:30 bbradley yes i will be using the renderer when its fixed.
15:31 bhosmer joined #salt
15:31 nickjj i wonder if it's some yaml error
15:31 nickjj have you tried also just stripping out the last character of the password variable as a quick fix?
15:33 bbradley the '-n' is appended. the '\n' from the debug output is not part of the password when applied by salt.
15:34 Katafalkas joined #salt
15:34 nickjj i didn't even notice the -n hah, i was only looking at the trailing new line
15:35 bbradley it is slightly confusing now that i look at that.
15:35 nickjj have you verified the password itself has no -n prefixed in it by decrypting it outside of salt?
15:35 bbradley hmmm
15:35 bbradley maybe i didn't. it has been two weeks.
15:36 bbradley but i did follow the instructions exactly.
15:36 nickjj ok
15:36 nickjj $ echo -n"supersecret" | gpg --homedir --armor --encrypt -r <KEY-name>
15:37 nickjj the instructions seem messed up, they forgot to space the -n
15:37 bbradley aha
15:37 bbradley i even recalled using 'man echo'.
15:38 dude051 joined #salt
15:38 bbradley i think the renderer instructions biased me :)
15:38 jpl1079 joined #salt
15:38 pfallenop joined #salt
15:38 bbradley i might look at it again today and file a PR for the docs unless you want to.
15:39 nickjj what shell are you running on the master?
15:39 darrend joined #salt
15:39 bbradley i'm have a masterless setup with vagrant.
15:39 nickjj or whatever machine you used when following those steps
15:39 bbradley s/i'm/i/
15:39 bbradley it's ubuntu 14.04 so bash
15:39 ckao joined #salt
15:40 nickjj are you in a position to test it now?
15:41 bbradley no honestly like i said, i just keep my passwords outside of source control for now.
15:41 nickjj ah ok, i thought maybe you had a test setup to quickly rerun it
15:41 bbradley not ready to work yet today, but maybe in a few hours.
15:42 bbradley the edits are trivial, just enjoying Sunday morning a bit first :)
15:43 nickjj trivial edits... sounds like famous last words
15:43 bbradley heh
15:43 bbradley i have a bouncer running so i'm around most of the time.
15:44 bbradley i'll ping you if i get to that today.
15:44 nickjj i don't mind sending a PR but i don't want to send one with a fix commit that doesn't fix it in the end
15:44 bbradley heh
15:44 darrend joined #salt
15:44 mrh-2727-2 joined #salt
15:44 nickjj but just fooling around in my terminal, adding the space does fix it
15:44 aquinas joined #salt
15:44 mrh-2727-2 Hi there, I need to define a list of fqdn of already deployed 3 mongo-config servers for sls of mongos. Let say if should be defined as {{ config_svrs }} in init.sls of mongos. How can I get those fqdn in jinja.map in cycle? Anyone?
15:44 bbradley whoevers first i guess :)
15:49 kingel joined #salt
15:50 aquinas_ joined #salt
15:51 jpl1079 does anyone know of a way to redirect the output of a cmd.script run on multiple minions to individual files on the master?
15:51 sroegner_ joined #salt
15:51 darrend joined #salt
15:53 jpl1079 can't seem to find this in the documentation anywhere
15:55 invsblduck joined #salt
15:56 httpdss hi! im trying to get pillar data but it seams somehting is wrong. looking at the log, the variables are read correctly, but states dont see them when setting variables (ex: root_password on mysql-formula ). btw im using salty-vagrant (vagrant+saltstack). any idea on whats happening or what should i do to debug it?
15:57 astol1 joined #salt
15:58 httpdss oh, and running masterless
15:59 astol joined #salt
15:59 httpdss i tried all whats said here: https://github.com/JustinCarmony/salt-troubleshoot but nothing
16:01 rigor789|away joined #salt
16:14 darrend joined #salt
16:15 crane hi, what is the way to target minions with different pillar files? i tried this way but ending up with empty pillar contents https://www.refheap.com/91617
16:16 viq crane: you could just do 'host1':   as id matching is the default
16:17 crane viq: but i still have to refer that i want to match grain?
16:17 viq no
16:18 viq https://www.refheap.com/a086d4139e872b9bb643f6922
16:20 crane hmm... my pillar content is still not written into my file
16:20 Katafalk_ joined #salt
16:21 rigor789 joined #salt
16:22 StDiluted joined #salt
16:22 mrh-2727-2 Guys, please, what did I do wrong when trying to get list of fqdn's? https://www.refheap.com/91619
16:25 darrend joined #salt
16:25 dccc__ joined #salt
16:34 StDiluted joined #salt
16:36 darrend joined #salt
16:42 darrend joined #salt
16:48 StDiluted joined #salt
16:50 kingel joined #salt
16:51 bhosmer joined #salt
16:54 acabrera joined #salt
16:55 deepz88 joined #salt
16:59 mrh-2727-2 Or even here: https://www.refheap.com/91620 ?
17:02 Mso150 joined #salt
17:02 crane viq: i still end up with no data from my pillars. if i run it without trying to use multiple configs it works as expected
17:07 XenophonF joined #salt
17:07 eliasp prepare your salt shells, more SSL fun incoming: https://twitter.com/briankrebs/status/521301468192968704 (thx Whissi :) )
17:16 Katafalkas joined #salt
17:16 kingel joined #salt
17:18 cads joined #salt
17:26 mechanicalduck joined #salt
17:29 micah_chatt joined #salt
17:29 viq crane: how are you trying to use multiple configs?
17:30 crane viq: multiple pillar files with different vars targetet by minion id
17:31 viq crane: does "salt minion pillar.get tor" work?
17:33 crane viq: salt-call --local pillar.get tor -- looks empty
17:35 viq crane: if you're using .11 switch to different version or use real master, there's a bug with local mode and pillars
17:35 crane viq: so the problem will maybe go away if i run a real setup with master and minions?
17:52 sroegner_ joined #salt
17:52 mlilenium_ joined #salt
17:53 mlilenium_ left #salt
17:56 faust joined #salt
18:03 kingel joined #salt
18:05 schimmy joined #salt
18:09 cberndt joined #salt
18:12 schimmy joined #salt
18:34 diegows joined #salt
18:37 mrh-2727-2 How to use "salt 'instance-name*' grains.get fqdn" in jinja template? Something like salt['grains.get']('instance-name*', 'fqdn')? Or how to do it right?
18:39 ingwaem joined #salt
18:40 bhosmer joined #salt
18:51 eliasp mrh-2727-2: in Jinja this would be:
18:51 eliasp {% grains['fqdn'] %}
18:52 eliasp mrh-2727-2: no need for 'instance-name*' … this will be provided through the renderer context
18:52 babilen mrh-2727-2: Well, salt['grains.get']('fqdn', 'some-default') would work too
18:54 babilen But you typically see grains['foo']
18:55 mrh-2727-2 Thank you, guys! I was messed up with how to get fqdn of some instance already deployed.
18:55 ingwaem joined #salt
18:56 dude051 joined #salt
18:57 crane babilen: maybe you can help me out. ;) this is how far i got right now: https://github.com/craneworks/tor-salt now i would like to target different minions so that they use different pillar files for configuration. in this example i'm using the two private_keys. but i just end up with empty prviate keys?
19:02 astol joined #salt
19:02 Mso150 joined #salt
19:03 babilen crane: Looks fine (but I will be doing that a lot tomorrow so forgive me if I don't spend a lot of time on it right now)
19:04 kingel joined #salt
19:04 astol joined #salt
19:04 crane babilen: you helped me allready a lot. so dont apologize for not having time for giving free support. ^^
19:05 astol1 joined #salt
19:08 Kelsar_ joined #salt
19:09 babilen crane: I'd check if the pillar is available for the minions in question and then run the minion/master/job in debug mode (salt{,-master,-minion} -ldebug)
19:12 crane babilen: maybe, but i'm not sure, the problem is that i'm testing this setup masterless with vagrant...
19:13 babilen Oh, .11 ?
19:13 crane .11?
19:14 babilen Version 2014.1.11
19:14 babilen masterless pillars are broken in .11 and will be fixed in .12
19:14 crane *doh*
19:15 crane yes
19:15 crane true
19:15 crane now i got what viq mentioned before... sorry
19:15 babilen (cf. #16416, #16210, #16212)
19:16 crane it's time for a real setup... ^^
19:17 cmthornt1n crane: just add this before you call the salt provisioner: config.vm.provision :shell, :inline 'salt-call --version || wget -O - http://bootstrap.saltstack.org | sh -s -- -D git v2014.7'
19:18 cmthornt1n untested, but something like that should work to install a salt version where pillar data isn't broken for masterless
19:20 babilen I'd probably still track 2014.1 rather than 2014.7 right now
19:21 crane cmthornt1n: thx for the hint
19:21 babilen crane: I use a master/minion setup based on docker for fast checking: https://gist.github.com/babilen/e9479fdfbcca431db208
19:21 crane babilen: never used docker before. using atm only vagrant for fast setups
19:21 babilen Well, I am primarily using libvirt based vagrant boxes right now, but that docker setup is pretty fast (everything is better than poopy virtualbox)
19:21 crane but there i can also go with a master/minion setup
19:22 crane babilen: +1 ^^
19:23 babilen crane: You essentially just run "docker build -t debian-7-vagrant-salt-master /path/to/the/dir/with/that/dockerfile" and then "vagrant up --provider=docker"
19:23 babilen (Ah, "--no-parallel" is sometimes needed too)
19:25 crane babilen: will take a look later on it... but first... making some mexican tacos ^^
19:26 pdayton joined #salt
19:27 babilen sounds like a plan :)
19:27 babilen fwiw, .12 packages will hit the mirrors quite soon
19:28 ndrei joined #salt
19:31 desposo joined #salt
19:33 Mso150 joined #salt
19:36 bbradley nickjj: your hypothesis about the problem was correct.
19:36 bbradley just a documentation error
19:37 nickjj bbradley: cool
19:38 bbradley that's funny.
19:38 cmthornt1n is there any way to match strictly on the state id (I believe it must be unique?), something like `require: [ id: install-thepkg ]` instead of `require: [ pkg: thepkg ]`. I have a package that I was installing with `pkg.installed` but now I'm compiling it from source, so I now use `cmd.run`, but I'd like to not have to fix up all the `require` lines. I have a solution, but it's a bit of a hack, which is installing a dummy package a
19:38 bbradley another bug i was encountering came back after using gpg encrypted items.
19:40 Mso150 joined #salt
19:45 eliasp cmthornt1n: what you want is: use whatever name you want for your state and address the package name via "- name: mypackage"
19:46 eliasp cmthornt1n: then you can refer to this state as a requisite via it's name
19:47 cmthornt1n ahh, thanks a ton :D  I've been searching for something called state, state-id, id but didn't try or see `name`
19:49 bluenemo joined #salt
19:50 bluenemo when file.managed, can I disable the source_hash requirement somehow when setting source to a https://foo.com/file.txt
19:52 bbradley nevermind, one of my commits had me using 2014.7rc2.
19:53 sroegner_ joined #salt
19:58 superseb joined #salt
20:00 IOMonste1 joined #salt
20:00 wedgie joined #salt
20:00 ahale joined #salt
20:00 keekz_ joined #salt
20:00 JoeyJoeJo joined #salt
20:00 esogas_ joined #salt
20:00 Sacro joined #salt
20:00 devx_ joined #salt
20:00 aqua^lsn joined #salt
20:00 luminous joined #salt
20:01 repl1cant joined #salt
20:01 micah_chatt joined #salt
20:01 nkuttler joined #salt
20:01 MatthewsFace joined #salt
20:01 z3uS joined #salt
20:01 scooby2 joined #salt
20:01 huleboer joined #salt
20:01 Ssquidly joined #salt
20:01 aarontc joined #salt
20:01 programmerq joined #salt
20:01 lahwran joined #salt
20:01 manfred joined #salt
20:02 flebel joined #salt
20:02 IOMonster joined #salt
20:04 jalaziz joined #salt
20:04 toddnni joined #salt
20:04 perfectsine joined #salt
20:05 cofeineSunshine joined #salt
20:05 cofeineSunshine joined #salt
20:06 tmh1999 joined #salt
20:06 nkuttler joined #salt
20:06 J[] joined #salt
20:07 tmh1999 joined #salt
20:07 blast_hardcheese joined #salt
20:09 dstufft joined #salt
20:11 dstufft Using a grain matcher in a pillar means that a node can control if they match that grain by editing the minion config right?
20:12 dstufft e.g. in the case of a compromised node, someone could add themselves so they get _all_ the pillar data
20:12 httpdss_ joined #salt
20:13 eliasp dstufft: that's why you should never hand out any valuable data simply based on grain matches
20:13 Eugene Yes. Don't trust grains
20:14 dstufft Yea, We're (python.org :|) doing that right now, that's what I thought so time to figure out how to fix that :D
20:15 dstufft Does doing this in a pillar : https://bpaste.net/show/2cf8863dd7f5 (taken from the salt docs..) work to create "roles" and match based on pillar data?
20:20 kingel joined #salt
20:29 bhosmer joined #salt
20:29 pdayton1 joined #salt
20:34 schimmy joined #salt
20:37 schimmy1 joined #salt
20:40 tafa2 joined #salt
20:41 anotherZero joined #salt
20:45 synical joined #salt
21:04 kiorky joined #salt
21:05 vlcn is it possible to make use of wildcards in the pillar top file?
21:08 ajolo__ joined #salt
21:09 babilen vlcn: http://docs.saltstack.com/en/latest/topics/targeting/
21:10 cads joined #salt
21:11 vlcn babilen, sorry I should have been mre specific.  I meant something like this: https://gist.github.com/kelchm/42fd647e4805563e9be8
21:11 kiorky joined #salt
21:12 iggy no
21:12 jdmf joined #salt
21:14 babilen You might be able to write such a "include all subpillars" pillar in Python or, if necessary, as external pillar though
21:14 vlcn https://github.com/saltstack/salt/issues/4610#issuecomment-40198089
21:14 vlcn this is essentially what I am trying to implement
21:15 vlcn I want to be able to easily manage minion-specific configurations, ideally without having to edit the top file every time
21:15 vlcn and my minion-specific configurations I meants to say minion-specific pillar data
21:26 eliasp hu? salt-master on Ubuntu 14.04 is playing jokes on me… with "-l debug" it tells me on startup it would read the config files from master.d/, but then doesn't act according to the values provided in those files…
21:28 n8n joined #salt
21:30 eliasp wiping the master's cache doesn't change anything
21:30 eliasp it just acts like the files in master.d/*.conf were empty
21:31 eliasp I just copied them over from another master where they worked just fine for the past 9 months or so
21:35 eliasp even with '-l trace' everything looks OK
21:35 peters-tx joined #salt
21:37 iggy sure they aren't just being overwritten by another file?
21:38 eliasp iggy: no… there are no conflicting config values in my master.d/*.conf files…
21:38 eliasp iggy: and in /etc/salt/master itself is nothing but the defaults…
21:38 eliasp iggy: adding now some debug to salt/config.py to find more out
21:39 eliasp iggy: I have the feeling the results from reading the config files aren't properly propagated into __opts__
21:42 eliasp salt/config.py → load_config() looks good… it returns proper values
21:43 eliasp hmm… there were no changes to salt/config.py since June 3rd…
21:44 eliasp same goes for salt/loader.py - which is the only module calling load_config()
21:45 anotherZero joined #salt
21:48 eliasp although it repeats reading the config multiple times (https://github.com/saltstack/salt/issues/10317), the last files being read are still those from master.d/*.conf
21:51 eliasp ok… now it's getting really funny… I just appended all the content of the files from master.d/*.conf to /etc/salt/master and it's still ignoring the given values
21:51 eliasp is this a weird 2014.1.11 issue?
21:53 sroegner_ joined #salt
21:56 kingel joined #salt
21:56 eliasp oh, this seems to be connected to the "no pillars on masterless minions issue" in 2014.1.11
21:56 acabrera_ joined #salt
22:02 eliasp hmm, no… applying PR#16212 locally doesn't change anything ;(
22:02 eliasp this is really frustrating…
22:03 mosen joined #salt
22:03 eliasp hmm… wait
22:04 eliasp it seems to have at least accepted my fileserver/GitFS setup… still not reading my PKI, but that might be something else
22:11 bbradley nickjj: if you ping me your github username, i'll cc you in a comment about finding the problem earlier.
22:11 Mso150 joined #salt
22:13 nickjj bbradley: it's nickjj
22:13 bbradley k
22:15 callbacker joined #salt
22:16 SheetiS joined #salt
22:17 bhosmer joined #salt
22:23 Katafalkas joined #salt
22:31 marsdominion joined #salt
22:35 bbradley nickjj: i guess the only other thing i should tell you is to make sure you use v2014.7 from git.
22:35 nickjj bbradley: i only started using salt the other day, but yes i'm working off the latest dev version
22:37 nickjj it's tough being a developer first and sys admin second -- i'm a sucker for new versions
22:45 bbradley heh
22:45 bbradley i like to stay slightly stable :)
22:51 viii joined #salt
22:53 httpdss joined #salt
22:57 kingel joined #salt
22:59 Outlander joined #salt
23:07 kusams joined #salt
23:12 badon_ joined #salt
23:27 mordonez joined #salt
23:33 ilbot3 joined #salt
23:33 Topic for #salt is now Welcome to #salt | 2014.1.10 is the latest | Help us test the 2014.7 RC! http://bit.ly/salt-rc | 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/
23:35 bhosmer joined #salt
23:45 ilbot3 joined #salt
23:45 Topic for #salt is now Welcome to #salt | 2014.1.10 is the latest | Help us test the 2014.7 RC! http://bit.ly/salt-rc | 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/
23:45 callbacker joined #salt
23:54 sroegner_ joined #salt

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