Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-04-09

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

All times shown according to UTC.

Time Nick Message
00:00 hemebond Not sure how you can create a specific grain to get just that though.
00:00 brotatochip The grain already exists
00:00 hemebond But if you were just trying to get it in a template then you've found it.
00:00 brotatochip Right, that’s what I’m trying to do
00:00 hemebond I know but I thought you wanted a grain that had only that, a custom grain.
00:01 brotatochip Ah, no, I just wanted to reliably grab the eth0 address
00:01 brotatochip For a template
00:01 hemebond I see.
00:10 baweaver joined #salt
00:10 subsignal joined #salt
00:14 brotatochip quick uqestion - what’s the best way to trigger a new firewall rule on the installation or setup of a package, such as elasticsearch for example?
00:14 brotatochip i’m thinking it should go in start.sls, I’m just not sure what it would look like
00:15 hemebond start.sls?
00:15 hemebond Is that a specific thing or just a module you created?
00:16 brotatochip It’s a submodule that one would call in theory on initilization of something
00:16 hemebond Well, there are modules for managing firewalls. You could create a state that updates the rules and watches the Elasticsearch package. It will then get run every time the package changes
00:17 brotatochip So I could invoke module.run onchanges with the pkg.managed section?
00:18 hemebond Well you would either "watch" from the firewall state (the state that updates the firewall rules) or "watch_in" from the pkg.managed (managed or installed?)
00:20 hemebond There's an iptables state module, btw.
00:20 brotatochip Ah, I suppose I could use that instead of firewalld
00:20 brotatochip But that’s more work
00:20 amcorreia joined #salt
00:20 hemebond There's a firewalld state module too.
00:20 space-lord-fett joined #salt
00:20 brotatochip Right, I think that would be better
00:22 hemebond Would your firewall config actually change when the package is upgraded?
00:23 quique joined #salt
00:23 antpa joined #salt
00:23 hemebond Oh, there's an onchanges requisite.
00:24 space-lord-fett Does anyone have any examples of how you would deploy your software via Salt through dev/stage/prod?  Specifically how do I control the version of the software package being deployed to each environment as new code is committed, built, and promoted from environment to environment.
00:24 hemebond space-lord-fett: What is "the software packge"? A pkg.installed thing?
00:25 space-lord-fett Possibly, it is internal software built by an internal team.  It could be a choco package, composer package, or node package.
00:26 hemebond Well, if you're managing it with Salt, and you want a specific version, you'd put that version into your Pillar data for each environment, no?
00:26 ahammond space-lord-fett there are a _lot_ of ways to do this.
00:26 ahammond here at AF, we use at least 3
00:26 space-lord-fett I thought about that, but how would I dynamically change that version as code makes its way through the CI/CD pipeline?
00:27 hemebond space-lord-fett: I have a different repo for the Pillar data for each environment.
00:27 ahammond 1) deploying directly via git. This makes sense for less sensitive stuff that doesn't require compilation / build / etc
00:27 hemebond So if an environment should get a new package version, I update that Pillar/repo.
00:27 aw110f joined #salt
00:28 space-lord-fett Do you manually update it, or is it part of the CI/CD pipeline?
00:28 ahammond 2) branch-based CD, where git commits drive builds (in buildbot) which generates salt events which drive a reactor to install them on different subsets of machines based on which branch was built
00:28 ahammond 3) somewhat more traditional deployment via yum repo management
00:29 space-lord-fett I have been targeting something like 3.  I am just having a hard time figuring out what should or should not update the pillar data as new artifacts are made available.
00:29 hemebond I manually update the Pillar data. We just use deb packages so by updating the Pillar the environment gets that version.
00:30 ahammond what hemebond is describing makes a lot of sense too, if you want to have multiple versions available in the same repo and then manually select which ones go where. Generally we install latest of everything in the repo and then manage the contents of the repos.
00:30 hemebond Test/dev environment just gets the latest version.
00:30 hemebond But prod gets the version we specify.
00:30 space-lord-fett got it
00:30 space-lord-fett Thanks!
00:31 space-lord-fett During automated tests in the Test/dev environment, do you queue up version updates and serially test versions?  Or do you allow parallel environments / test runs?
00:32 MTecknology joined #salt
00:32 aw110f joined #salt
00:32 hemebond Well my team doesn't dev or test them really.
00:32 hemebond That's done by another team.
00:33 hemebond But I believe they just deploy a new version as soon as it's built.
00:34 space-lord-fett One thought was to allow for dev/Test to just pull the latest and promote the version to a new artifact repo (RC).  Then Stage pulls the latest from RC and manual / auto tests.  Once finished in Stage the Prod pillar could be manually updated.
00:35 hemebond One of the environments, staging, gets changed via a web interface by QA.
00:35 hemebond They can select the version of each application to deploy to test it.
00:36 space-lord-fett That sounds like a good idea.
00:36 hemebond Prod is manually updated in the config to deploy the new versions.
00:37 space-lord-fett Thanks for the input and advice!  On another note, has anyone had issues getting gitfs to work through Vagrant?
00:39 quix joined #salt
00:40 ahammond space-lord-fett no issues, works fine for me.
00:41 hemebond I've heard of people having issues when they have a lot of repos.
00:41 paydro joined #salt
00:41 space-lord-fett Is there a way to get it to log in more detail?  I have the master's config copied from the Salt Doc, but no srv/salt or srv/pillar directories get created.
00:42 space-lord-fett I am starting small with one repo.  It is a private bit-bucket server repo.
00:43 space-lord-fett To clarify private, it is on a private network where the repo is set to public and read-only default access.
00:44 teatime nothing auto-creates /srv/salt or /srv/pillar, unless you have a state that does that
00:45 teatime to the extent they're used in the docs, they're expected to be manually created
00:46 teatime http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM
00:46 teatime ^^ may provide some enlightenment?
00:50 space-lord-fett That may be my issue, I will give that a shot.
00:51 teatime and yeah, you can change the log level, or just stop the master/minion and start them manually with -l DEBUG
00:51 teatime there's some description of that in the docs
00:53 devops left #salt
00:54 paydro joined #salt
01:13 quasiben joined #salt
01:20 catpiggest joined #salt
01:31 michelangelo joined #salt
01:31 TheoSLC joined #salt
01:38 ageorgop joined #salt
01:43 iggy `salt-call cp.list_master` or `salt-run fileserver.file_list` are good commands for seeing if your files are showing up on the master
01:51 akhter joined #salt
01:53 renaissancedev joined #salt
02:01 hasues joined #salt
02:01 hasues left #salt
02:05 iceyao joined #salt
02:06 writtenoff joined #salt
02:17 paydro joined #salt
02:17 paydro joined #salt
02:18 quasiben joined #salt
02:25 antpa joined #salt
02:35 jalbretsen joined #salt
02:48 vivek_ joined #salt
02:50 vivek_ hi all . i m getting this error while running commands fromm master "Minion did not return. [No response]" ..can someone pls suggest  how i can fix it.i have same version of zmq installed on master & minion  plus timeout on master is set to 300 . is ther anything else i can do..pls advise
02:51 teatime do you get it all the time from certain minions, or just like once after minion startup and then not again, or what?
02:51 vivek_ i get this from certain minions all the time..
02:52 teatime probably those minions are offline, then?
02:52 teatime or otherwise can't contact / connect to the master.
02:53 vivek_ no i checked salt-minion is running on those machines which r returing this message >>> "Minion did not return. [No response]"
02:54 teatime you might try checking the debug log on the minion during startup.
02:57 vivek_ ahh i got that thanks...salt-minion is having different public key ...can u please share the reason why the public of master got changed at the minion end
02:58 vivek_ i dont understand this behaviour of different public key of master,,,when does this happen
02:58 vivek_ & how i can avoid it
02:58 teatime doesn't happen on its own
02:58 teatime can you post the message?
02:58 teatime sounds like maybe those minions are actually connecting to a different master
02:59 teatime maybe because you're taking advantage of the auto-lookup of the DNS name 'master' when no master is specified in the config?
03:04 vivek_ this is the mesg
03:04 vivek_ ++++++++++++
03:04 akhter joined #salt
03:04 kshlm joined #salt
03:05 vivek_ [ERROR   ] The master key has changed, the salt master could have been subverted, verify salt master's public key [CRITICAL] The Salt Master server's public key did not authenticate! The master may need to be updated if it is a version of Salt lower than 2015.8.8.2, or If you are confident that you are connecting to a valid Salt Master, then remove the master public key and restart the Salt Minion. The master public key can be found at:
03:05 vivek_ [INFO    ] The Salt Minion is shut down [ERROR   ] Minion failed to start [WARNING ] ** Restarting minion ** [INFO    ] Sleeping random_reauth_delay of 9 seconds [DEBUG   ] Reading configuration from /etc/salt/minion [DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf' [DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf [DEBUG   ] Using cached minion ID from /etc/salt/minion_id: solr-shard-9-sl
03:06 vivek_ [CRITICAL] The Salt Master server's public key did not authenticate! The master may need to be updated if it is a version of Salt lower than 2015.8.8.2, or If you are confident that you are connecting to a valid Salt Master, then remove the master public key and restart the Salt Minion.
03:06 teatime don't paste here
03:06 teatime it's in the topic, even.
03:06 barajasfab joined #salt
03:09 vivek_ sorry
03:11 mavhq joined #salt
03:11 vivek_ another doubt.. sallt-master has rejected my minion key..now how to know why the master rejected it.. is there any log i can check
03:13 teatime that sounds like it's the minion rejecting the master's the key.
03:13 teatime which you really, really need to figure out why.
03:13 teatime that minion almost certainly registered with a different master originally.
03:15 hightekvagabond1 joined #salt
03:15 teatime vivek_: do you configure the master hostname explicitly in your minion configuration?
03:16 vivek_ yes i do mention the ip in the minion configuration
03:17 teatime how do you figure you managed to register your minion to a different master earlier?
03:17 teatime also, what version of salt on the master?
03:17 vivek_ version is salt-master 2015.8.8.2 (Beryllium)
03:18 vivek_ i m also surprised yesterday i registered this minion with master & today it showing the mesg "minion didnt return" , even though nothing has changed on master
03:18 vivek_ running the minnion in debug mode shows that the minion is not able to connect to master
03:19 vivek_ teatime_ do you an idea on this behaviour,, so that i can take in the furture as wel
03:19 teatime no, only that I suspect you're doing something very weird/unusual.
03:19 teatime are you the same person that was having the issue of there being extra/extraneous minions running on some hosts?
03:22 paydro joined #salt
03:27 vivek_ noo i m not the one
03:35 borgstrom joined #salt
03:43 beardedeagle joined #salt
03:46 ninecheddar joined #salt
03:54 quix joined #salt
04:11 cheus joined #salt
04:15 CeBe joined #salt
04:23 quique joined #salt
04:34 akhter joined #salt
04:39 ageorgop joined #salt
04:40 jalbretsen joined #salt
04:47 sjmh joined #salt
04:47 cberndt joined #salt
04:57 ninecheddar left #salt
05:12 brianfeister joined #salt
05:13 sauvin joined #salt
05:20 brotatochip joined #salt
05:23 ajw0100 joined #salt
05:24 sauvin joined #salt
05:31 iceyao joined #salt
05:59 punkoivan joined #salt
06:01 punkoivan left #salt
06:05 babilen vivek_: In most of these cases it turned out to be a network issue for us (e.g. wrong MTU settings) - Check if you can telnet into $MASTER_IP:4505. I'd also recommend to run both the master and the minion in debug mode (salt-{master,minion} -ldebug)
06:21 sauvin joined #salt
06:37 vivek_ thanks _babilen for ssharing the info
06:44 mavhq joined #salt
07:14 kshlm joined #salt
07:20 evle joined #salt
07:21 cliluw joined #salt
07:24 brotatochip joined #salt
07:27 cpowell joined #salt
07:45 asyncsrc1 joined #salt
07:45 felskrone joined #salt
07:48 jankmcjanker left #salt
07:54 mavhq joined #salt
08:02 brianfeister joined #salt
08:17 slav0nic joined #salt
08:26 colegatron joined #salt
08:29 cpowell joined #salt
08:29 armyriad joined #salt
08:46 keimlink joined #salt
09:05 jamesp9 joined #salt
09:10 colegatron joined #salt
09:23 drunk_signal joined #salt
09:29 thehaven joined #salt
09:34 vicky_ joined #salt
09:35 Guest26566 hi
09:35 punkoivan joined #salt
09:35 Guest26566 for a cluster of 2300 machines.. how much threads should i configure in the salt master config file.. please suggest
09:35 punkoivan left #salt
09:36 Guest26566 what is the metrics for defining threads in master
09:36 jeddi joined #salt
09:39 paydro_ joined #salt
09:47 babilen Guest26566: At that scale I'd run jobs asynchronously by passing --async and would look up results later by JID. You are probably also interested in reading https://docs.saltstack.com/en/latest/topics/tutorials/intro_scale.html
09:47 cyborg-one joined #salt
09:48 babilen Not sure what you need hardware-wise and how to tinker with worker threads. We are running a 1000+ minion on a master with 16 cores and 6G RAM (but we don't pay for it, so I figured "why not?").
09:49 mavhq joined #salt
09:50 Guest26566 actually i was referring to worker_threads in master config file.. does this also need not to be altered for a cluster ssize of 2000 nodes ?
09:51 brianfeister joined #salt
09:53 evle1 joined #salt
09:58 sthns joined #salt
10:01 cberndt joined #salt
10:09 ivanjaros joined #salt
10:12 renaissancedev joined #salt
10:14 brianfeister joined #salt
10:22 TheoSLC joined #salt
10:23 TheoSLC left #salt
10:31 cpowell joined #salt
10:34 mavhq joined #salt
10:42 LeProvokateur joined #salt
10:55 dmaiocchi joined #salt
11:04 dmaiocchi joined #salt
11:05 ingslovak joined #salt
11:07 mohan__ joined #salt
11:07 mohan__ hi
11:10 mohan__ if i remove/add any key on master, or restart the master ,, does this process brings any change in the public keys of master,,>? actually i m confused i read in the salt documentation that on restart master changes its AES key but i dont see any change in the master public key file..what is AES key ?? isnt the same master public key master.pub ?? please help in understand
11:14 jf__ joined #salt
11:16 quasiben joined #salt
11:17 renaissancedev joined #salt
11:18 jf__ for ubuntu, is there any reason why anybody would want to use the "community-maintained" repo over the official one? (see https://docs.saltstack.com/en/latest/topics/installation/ubuntu.html)
11:32 jf__ another question: I'm seeing this line in my minion's log: [salt.cli.daemons ][WARNING ][<pid>] IMPORTANT: Do not use md5 hashing algorithm! Please set "hash_type" to SHA256 in Salt Minion config!
11:33 jf__ But when I go to check out /etc/salt/minion, I see a comment in there that says that "The default is sha256, sha224, sha384 and sha512 are also supported."? This is on a new install, with no specific 'hash_type:' setting
11:33 amcorreia joined #salt
11:35 AndreasLutro mohan__: I don't think the key changes on every restart. afaik, it gets changed every 24 hours
11:35 AndreasLutro jf__: if the comment says that then it's probably misleading... the default has been md5, and if you can you should set it explicitly to something else
11:36 mavhq joined #salt
11:39 teatime jf__: I don't know of any reason to use the ppa over repo.saltstack.com
11:39 teatime and I can think of a couple why I wouldn't want to
11:44 jf__ teatime: sure. I would think so too. I'm just surprised. Cos I did like a quick install and then missed that pointer to the official repo!
11:45 jf__ AndreasLutro: gotcha. Thanks
11:45 teatime I don't know, but suspect it may be related to migration from the 'old' salt repos to the new repo.saltstack.com
11:45 jf__ AndreasLutro: do I need to set it on both sides, master and minion? or is one side sufficient?
11:45 teatime so one of my reasons for preferring repo.saltstack.com is that I know it will receive new versions, for sure :)
11:45 teatime the other reason is, I use it for all other distros.
11:46 AndreasLutro jf__: I think it's just a minion setting. you can look it up in the docs
11:46 jf__ I see this warning in the master log as well: [salt.cli.daemons ][WARNING ][<pid>] IMPORTANT: Do not use md5 hashing algorithm! Please set "hash_type" to SHA256 in Salt Master config!
11:47 jf__ will search in the doc.
11:48 paydro joined #salt
11:48 AndreasLutro well you don't need to ask then
11:49 jf__ yeah... I guess! I saw it in the minion log first
11:50 jf__ I assume that between discrepancies (like this 'hash_type' thing) between what I see reported in the log, and what I see as a comment in the config, that the log is probably the one that wins?
11:50 teatime yeah
11:50 teatime where did the config comment come from?
11:50 teatime official saltstack.com packages?
11:50 jf__ yup
11:51 teatime probably worth seeing if there's a bug about it and submitting one if not
11:51 jf__ gotcha
11:51 teatime again, if it's the repo.saltstack.com packages of the newest version
11:51 mohan__ what is AES key of master,,> any thoughts
11:51 jf__ thanks
11:51 slav0nic joined #salt
11:52 jf__ mohan__: that should be negotiated on a per-connection basis. It should not be static
11:53 mohan__ if_ - is there any doc on AES keys which i can refer & how it get used in salt ..pls guide
11:54 jf__ I really doubt so. You can read any doc on ssh or ssl
11:54 jf__ what are you trying to do?
11:55 LeProvokateur joined #salt
11:56 mohan__ i want to understand how keys r being used in salt master & minion.. is this something different than public private key authetication
11:57 mavhq joined #salt
11:57 teatime jf__: sounds like he wants more salt-specific details than that
11:57 sthns joined #salt
11:59 mohan__ would be great if anyone can poinnt me online Salt doc..
11:59 teatime aha!  I just found a possible cause of Vivek's problem from yesterday
11:59 mohan__ what was tthat ..
11:59 mohan__ I followed that too Vivek issue..
12:00 mohan__ _teatime can u pls share
12:01 teatime "The minion id is used to generate the minion's public/private keys and if it ever changes the master must then accept the new key…"
12:04 teatime hrm, I thought there was a PKI overview doc; can't find it.
12:04 mohan__ ahhh ..
12:05 teatime these have some hints, though:  https://salt.readthedocs.org/en/stable/topics/tutorials/multimaster_pki.html  https://salt.readthedocs.org/en/stable/topics/tutorials/preseed_key.html
12:05 renaissancedev joined #salt
12:06 mohan__ thanks _teatime..appreciate ur time & effort
12:08 mohan__ any idea on this error on master >>  Bad load from minion: AuthenticationError: message authentication failed
12:10 mavhq joined #salt
12:20 linziyan hi
12:20 linziyan i come back..
12:20 linziyan if i want to use cp.get_file in state file
12:20 linziyan how to write it..
12:26 drunk_signal joined #salt
12:26 TyrfingMjolnir joined #salt
12:30 hightekvagabond joined #salt
12:31 Trauma joined #salt
12:33 cpowell joined #salt
12:40 XenophonF use file.managed instead of cp.get_file?
12:40 XenophonF there isn't a cp.get_file state
12:40 XenophonF there is a file.managed state
12:41 XenophonF you can give it a source of salt://something/something/something/dark/side
12:41 XenophonF and it will pull the file from /usr/local/etc/salt/states/something/something/something/dark/side
12:42 XenophonF adjust as appropriate for a file_roots config different than mine on FreeBSD
12:44 mavhq joined #salt
12:47 mavhq joined #salt
12:50 Azid joined #salt
13:02 mavhq joined #salt
13:35 Guest94643 joined #salt
13:49 akhter joined #salt
13:52 ingslovak joined #salt
13:53 paydro joined #salt
13:54 mavhq joined #salt
13:56 mavhq joined #salt
14:00 KingJ joined #salt
14:06 mavhq joined #salt
14:18 tharkun joined #salt
14:22 felskrone joined #salt
14:26 LostSoul Hi anyboddy around :)?
14:26 LostSoul I'm getting error: Too many functions declared in state 'network'  - what I did wrong? (Paste below)
14:26 LostSoul http://paste.debian.net/hidden/6ae2d956/
14:30 drunk_signal joined #salt
14:34 cpowell joined #salt
14:35 amcorreia joined #salt
14:37 teatime can you post your pillar file also?
14:39 KingJ joined #salt
14:42 teatime but fwiw I think it's probably that some of your values contain yaml special characters so they're not getting parsed as strings.
14:44 teatime if you know the values will never contain single quotes, you can just do it like this:  - ipaddr: '{{ interface.ip }}'
14:45 morissette joined #salt
14:46 LostSoul teatime: Sure
14:46 LostSoul Give me 5 min
14:46 AndreasLutro LostSoul: it's not that state causing the error
14:46 AndreasLutro show us the entire sls
14:53 Muchoz joined #salt
14:55 teatime (    and more generally, just to be comprehensive, you can do it like this:   - ipaddr: {{ interface.ip|yaml_encode }}    )
14:56 teatime ( or yaml_dquote/yaml_squote depending on the semantics you want )
15:06 catpig joined #salt
15:08 quix joined #salt
15:12 mavhq joined #salt
15:15 mavhq joined #salt
15:17 dmaiocchi joined #salt
15:20 LostSoul Sorry guys, on my way
15:21 teatime btw fairly sure AndreasLutro is right so please show full state sls first
15:23 mavhq joined #salt
15:23 LostSoul This is full sls file
15:24 mavhq joined #salt
15:25 Azid joined #salt
15:30 mavhq joined #salt
15:35 LostSoul http://paste.debian.net/hidden/20b86db2/
15:37 LostSoul Any ideas, as I though it's ok
15:40 teatime lines under '- name:' lines need another indent
15:40 teatime ... that is a lot different than what you initially posted, btw
15:43 av_ joined #salt
15:47 LostSoul Hmm
15:47 LostSoul Can you elaborate?
15:47 LostSoul As I didn't get it
15:48 AndreasLutro I assume that's your pillar sls
15:48 AndreasLutro it's the state sls I'm interested in
15:48 LostSoul AndreasLutro: But there is nothing more in state sls
15:49 LostSoul I'm rewriting it and currently all that there is in that sls is this: http://paste.debian.net/hidden/6ae2d956/
15:49 teatime alright, let me start over here.
15:50 LostSoul I guess I'm still newbie if it comes to Jinja/YAML
15:50 LostSoul And I'm often lost if it comes to using all those []. -, {}, {{ }}, '', ""
15:50 AndreasLutro your yaml is fine
15:51 AndreasLutro if that's your entire state sls then the error is probably from another sls file
15:51 AndreasLutro it's complaining about a state with the id "network"
15:52 teatime looking at the rendered state file would probably be helpful
15:53 tharkun joined #salt
15:53 teatime LostSoul: where does the pillar .sls live and how does it get targeted to the minion?
15:53 amcorreia joined #salt
15:54 LostSoul teatime: How to check rendered state file?
15:54 LostSoul teatime: In top.sls I'm including - nagios
15:55 LostSoul And in this nagios init.sls I'm including all pillars
15:56 LostSoul AndreasLutro: This network sls is this one I pasted
15:57 teatime LostSoul: you don't mean to say you're including pillars .sls files from states .sls files right?
16:02 teatime AndreasLutro: actually..
16:02 teatime AndreasLutro: wouldn't he get this error if his "pillar" file was actually being used as a state file?
16:02 LostSoul I don't teatime
16:02 LostSoul I keep them in 2 different location
16:03 LostSoul With 2 indepentent top files
16:03 teatime and yet... that would give you this error...
16:03 LostSoul It was working till I started to change my network sls to use loop for interfaces
16:03 teatime what are your pillar_roots and files_roots in master config?
16:04 LostSoul insted of creating X variables, I wanted to use list
16:04 LostSoul I'm not sure if I did it in good way and if this dns stuff is not done in wrong way
16:04 LostSoul files roots are untouched
16:04 teatime it looks like it would work.
16:05 LostSoul pillar and states are set from 2 different git repos
16:07 teatime ok, well; you can use `salt 'minionspec' state.show_sls path.to.some.state` to see how your state file gets rendered.
16:17 teatime you can also use pillar.item / pillar.items to confirm your pillar data looks like you expect
16:18 teatime but, it's pretty much only possible to guess randomly, since you don't want to share more of your config.
16:23 sjmh joined #salt
16:25 LostSoul thanks teatime
16:25 LostSoul I will check it
16:25 LostSoul I will share it soon
16:25 LostSoul But I give you all info really
16:30 amcorreia joined #salt
16:31 akhter joined #salt
16:32 drunk_signal joined #salt
16:34 LostSoul teatime: this state.show_sls: - Too many functions declared in state 'network'
16:34 LostSoul As it appeared twice (I forgot to mention it)
16:34 LostSoul I guess there is something wrong in pillar
16:34 LostSoul Like some variable makes mess
16:34 LostSoul I will try workouround
16:34 teatime it's just the same error as before 'cause trying to render the same way
16:35 teatime I thought there was a convenient function to so the same thing but only do the jinja render step w/o the next yaml render step
16:35 teatime but now I'm not finding the convenient one I was thinking of
16:35 LostSoul I will try to remove this dns
16:35 teatime pillar.items will tell you if your pillar makes sense, though.
16:36 LostSoul Ou, right
16:36 LostSoul Thanks man ;)
16:37 jfelchner joined #salt
16:38 LostSoul This is awesome
16:38 teatime and I could be way off base, but I am still betting on somehow you are having your pillar file (that defines 'network: interfaces:') as a state file.
16:38 LostSoul But on the other hand I have no idea
16:38 drunk_signal joined #salt
16:38 teatime LostSoul: you can also do  pillar.get "network:interfaces"  on the command line
16:39 LostSoul btw teatime
16:39 LostSoul 17:40 < teatime> lines under '- name:' lines need another indent
16:39 LostSoul 17:40 < teatime> ... that is a lot different than what you initially posted, btw
16:39 LostSoul What do you wanted to say by that
16:39 teatime yes, I was reading it as a state, not a pillar; disregard
16:39 kshlm joined #salt
16:41 mavhq joined #salt
16:41 LostSoul Ah, ok
16:46 LostSoul I have no idea what's wrong there
16:48 Muchoz_ joined #salt
16:50 LostSoul Strange teatime but pillar.get returned me old pillar values
16:53 teatime saltutil.refresh_pillar ?
16:53 teatime ... I almost said that earlier, but either forgot or decided you couldn't have overlooked it ...
16:55 LostSoul Should I use it on master on minion?
16:56 LostSoul Ah, worked but same error stil
16:56 LostSoul Ah, worked but same error still*
16:57 teatime on the master, targeting the minion.
16:57 teatime do you have new pillar values in pillar.get now?
16:59 sjorge joined #salt
17:03 LostSoul Yes
17:03 paydro joined #salt
17:04 nahamu joined #salt
17:05 grumm_servire joined #salt
17:06 tharkun So I installed saltstack and began playing with it. So far so good. But as someone told me: "Python is a boring language yet it is worth knowing." Where can I get a 101 crash course on python that you guys know about. Sorry for the OT question but I am sure your answer is better than the google crap I've been reading.
17:08 Muchoz joined #salt
17:09 honestly The official docs are the best reference
17:09 honestly Dunno about a crash course though
17:13 mavhq joined #salt
17:29 LostSoul teatime:
17:29 LostSoul I've changed enabled, type and proto to values and it worked
17:29 LostSoul Something is wrong with those default values
17:30 teatime perhaps you should use ['type'] instead of .type
17:30 dmaiocchi joined #salt
17:30 teatime they do different things, but in jinja each falls back to the other
17:32 LostSoul Strange as this "dotting" always worked so far for me
17:35 LostSoul teatime: It didn't help
17:35 punkoivan joined #salt
17:36 slav0nic joined #salt
17:39 slav0nic joined #salt
17:40 teatime LostSoul: fwiw, I don't see type, enabled, or proto in your pillar file?
17:40 punkoivan left #salt
17:40 teatime so those would sub in as empty string ...
17:40 teatime and not literal "" either, just no value
17:41 LostSoul teatime: They were set to:
17:42 LostSoul - enabled: {{ interface.enabled|default(true) }}
17:42 LostSoul So it should pass
17:42 mavhq joined #salt
17:42 teatime ( for future reference, difference between . and [] in jinja is: described here http://jinja.pocoo.org/docs/dev/templates/#variables but dicts do not seem to have attributes named thsoe things so indeed not relevant here.  but good to be aware of. )
17:45 LostSoul teatime: Strange thing happaned
17:45 teatime hrm, out of curiosity (you can check easier than I can), does |default("default value", true) work ?
17:45 LostSoul So I added 3 variables this way:     - enabled: {{ interface.enabled }}
17:45 LostSoul And I set them all 3 and now I still get the same error
17:45 teatime refresh_pillar
17:45 LostSoul So problem must be with those 3
17:46 LostSoul Still same
17:46 LostSoul Problem is cause either by enabled, proto or type
17:46 LostSoul I will change enabled just for fun
17:46 LostSoul And we will see
17:47 teatime I'm not sure what {{ true }} becomes but either true or "true" should work fine
17:48 felskrone joined #salt
17:49 source47 joined #salt
17:50 LostSoul Damn
17:50 LostSoul Hahahaha
17:50 aganders3 joined #salt
17:50 LostSoul I think I have it :)
17:52 teatime you better tell whatever it was when you figure itout
17:54 LostSoul Work like a charm
17:54 LostSoul You know what I did wrong?
17:55 LostSoul Check this:  - proto:{{ interface.proto|default('static') }}
17:56 LostSoul You see? proto:{{ should be proto: {{  - I did same mistake in past with same error message, shame on me
18:10 brotatochip joined #salt
18:13 brotatochip joined #salt
18:16 mavhq joined #salt
18:17 ageorgop joined #salt
18:19 mavhq joined #salt
18:19 paydro joined #salt
18:36 cpowell joined #salt
18:39 source47 joined #salt
18:43 mavhq joined #salt
18:48 colegatron joined #salt
19:01 mavhq joined #salt
19:04 cberndt joined #salt
19:09 josuebrunel joined #salt
19:10 mavhq joined #salt
19:11 LeProvokateur joined #salt
19:12 sjorge joined #salt
19:13 kevinquinnyo1 joined #salt
19:35 sjorge joined #salt
19:37 aganders3 joined #salt
19:38 cpowell joined #salt
19:38 cpowell joined #salt
19:39 cpowell joined #salt
19:40 elsmo joined #salt
19:41 paydro_ joined #salt
19:41 aganders3 joined #salt
19:44 aganders3 joined #salt
19:49 cyborg-one joined #salt
19:56 cyborg-one joined #salt
19:57 sjorge joined #salt
19:59 mavhq joined #salt
20:00 Azid joined #salt
20:01 mavhq joined #salt
20:02 sjorge joined #salt
20:05 mavhq joined #salt
20:06 hax404 joined #salt
20:18 mavhq joined #salt
20:25 armyriad joined #salt
20:26 scoates joined #salt
20:30 arif-ali joined #salt
20:30 mavhq joined #salt
20:37 dezet joined #salt
20:38 ingslovak joined #salt
20:39 mavhq joined #salt
20:42 LeProvokateur joined #salt
20:48 quique joined #salt
20:49 dmaiocchi joined #salt
20:49 mavhq joined #salt
20:50 Rumbles joined #salt
20:56 viq joined #salt
20:56 keimlink joined #salt
21:03 mavhq joined #salt
21:06 hax404 joined #salt
21:09 toastedpenguin joined #salt
21:10 toastedpenguin is it possible to tag ebs volumes when launching new instance using salt-cloud?
21:12 aganders3 joined #salt
21:16 hax404 joined #salt
21:19 ageorgop joined #salt
21:24 hax404 joined #salt
21:25 hax404 joined #salt
21:31 mavhq joined #salt
21:35 hasues joined #salt
21:35 hasues left #salt
21:47 kevinquinnyo1 joined #salt
21:51 mavhq joined #salt
21:52 aganders3 joined #salt
22:13 ageorgop joined #salt
22:15 hightekvagabond joined #salt
22:16 aganders3 joined #salt
22:17 aganders3_ joined #salt
22:21 hightekvagabond joined #salt
22:23 dayid joined #salt
22:24 paydro joined #salt
22:25 Twiglet joined #salt
22:27 barajasfab joined #salt
22:27 brianfeister joined #salt
22:27 hasues joined #salt
22:28 godlike joined #salt
22:28 godlike joined #salt
22:29 source47 joined #salt
22:29 hasues left #salt
22:31 ageorgop joined #salt
22:32 ageorgop joined #salt
22:32 source47 joined #salt
22:33 source47 joined #salt
22:40 liqw joined #salt
22:41 zenlot6 joined #salt
22:54 kevinquinnyo1 joined #salt
23:01 mavhq joined #salt
23:03 mavhq joined #salt
23:07 mavhq joined #salt
23:14 keimlink_ joined #salt
23:15 onlyanegg joined #salt
23:18 mavhq joined #salt
23:26 source47 joined #salt
23:27 beardedeagle joined #salt
23:28 mavhq joined #salt
23:32 mavhq joined #salt
23:38 west575 joined #salt
23:40 seblu joined #salt
23:41 source47 joined #salt
23:47 brianfeister joined #salt
23:47 paydro joined #salt
23:48 TyrfingMjolnir joined #salt
23:53 mavhq joined #salt

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