Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-04-27

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

All times shown according to UTC.

Time Nick Message
00:01 tercenya joined #salt
00:06 woodtablet left #salt
00:10 fracklen joined #salt
00:14 sh123124213 joined #salt
00:20 keldwud joined #salt
00:20 keldwud joined #salt
00:30 nidr0x joined #salt
00:42 MTecknology I have a web app I want to deploy, but the settings file is in the top of the directory structure (and one other variable file is built outside of the dir and a symlink that can't be in the repo is created. I'm having an issue trying to mash the git.latest and two file.managed states. (issue: I can't figure it out)
00:44 aneeshusa joined #salt
00:48 whytewolf to bad it is git.latest and not file.recurse file.recurse you could just do require the 2 file.managed and it would ignore them with out deleting them
00:49 MTecknology git.recurse w/ clean:True?! :P
00:49 whytewolf yes
00:50 whytewolf lol
00:50 whytewolf missed you said git
00:53 MTecknology oh...
00:53 MTecknology .gitignore
00:53 * MTecknology checks
00:54 PatrolDoom joined #salt
00:55 NeoXiD joined #salt
00:55 mpanetta joined #salt
01:04 gmoro joined #salt
01:06 MTecknology whytewolf: lovely... I've already solved this problem. All I had to do was delete the stuff git didn't like and run a highstate.
01:07 whytewolf nice
01:07 MTecknology I probably fell asleep (passed out late at night) the last time I figured it out and just never finished cleaning it up
01:13 Shirkdog joined #salt
01:13 mpanetta joined #salt
01:18 swa_work joined #salt
01:22 aneeshusa joined #salt
01:31 antpa joined #salt
01:33 MTecknology I'm clearly not running "salt '*' state.highstate" often enough. Worse, I'm not getting errors.
01:34 ping0ra joined #salt
01:41 Kelsar joined #salt
01:41 prg3 joined #salt
01:47 nikdatrix joined #salt
01:49 ilbot3 joined #salt
01:49 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.4 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ (please don't multiline paste into channel) <+> See also: #salt-devel, #salt-offtopic <+> Ask with patience as we are volunteers and may not have immediate answers
02:04 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.6, 2016.11.4 <+> Support: https://www.saltstack.com/support/ <+> SaltStack Webinar on Carbon, Nitrogen, and Enterprise 5.1 on May 18, 2017 https://goo.gl/PvsOvQ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic <+> We are volunteers and may not have immediate answers
02:05 gtmanfred boom, first try
02:08 edrocks joined #salt
02:19 aneeshusa joined #salt
02:20 hemebond So.... import_yaml is broken in 2016.3.6?
02:20 hemebond Or have I some how written a bad path?
02:21 hemebond I see it was broken for pillars in develop.
02:22 gmoro joined #salt
02:24 jdipierro joined #salt
02:40 sp0097 joined #salt
02:47 aneeshusa joined #salt
02:49 antpa joined #salt
03:01 onlyanegg joined #salt
03:04 evle joined #salt
03:12 zerocoolback joined #salt
03:30 sp0097 joined #salt
03:43 nikdatrix joined #salt
03:48 cyborg-one joined #salt
03:54 Praematura joined #salt
03:59 onlyanegg joined #salt
04:00 rem5 joined #salt
04:01 sp0097 joined #salt
04:11 Bock joined #salt
04:11 LeProvokateur joined #salt
04:13 mosen joined #salt
04:13 Bock joined #salt
04:14 debian112 joined #salt
04:18 antpa joined #salt
04:34 vodik joined #salt
04:45 icebal joined #salt
05:13 LeProvokateur joined #salt
05:14 zerocool_ joined #salt
05:33 jas02 joined #salt
05:34 rdas joined #salt
05:35 eseyman joined #salt
05:44 nikdatrix joined #salt
05:54 do3meli joined #salt
05:55 do3meli left #salt
05:56 sh123124213 joined #salt
05:58 citaret joined #salt
06:09 antpa joined #salt
06:16 guerby joined #salt
06:26 jas02 joined #salt
06:29 onlyanegg joined #salt
06:40 felskrone joined #salt
06:43 fracklen joined #salt
06:43 willprice94 joined #salt
06:44 golodhrim|work joined #salt
06:53 zerocoolback joined #salt
06:54 Ricardo1000 joined #salt
06:54 sh123124213 joined #salt
06:57 sh123124213 joined #salt
06:59 _JZ_ joined #salt
07:03 Miouge joined #salt
07:06 Rumbles joined #salt
07:07 jas02 joined #salt
07:09 candyman88 joined #salt
07:11 aldevar joined #salt
07:12 JohnnyRun joined #salt
07:13 edrocks joined #salt
07:21 muxdaemon joined #salt
07:21 fracklen joined #salt
07:22 fracklen joined #salt
07:24 eseyman joined #salt
07:34 pbandark joined #salt
07:35 fracklen joined #salt
07:38 alex-zel joined #salt
07:38 alex-zel Hello, there seems to be an issue with updating salt via yum https://gist.github.com/anonymous/2782ccf5a4f10d3e2fb1e9e7bb7e66fb
07:39 alex-zel i'm getting this error on multiple servers running centos 7/Scientific Linux release 6
07:39 hemebond Centos again
07:39 alex-zel I've tried disabling the EPEL repo but that didn't help
07:45 nikdatrix joined #salt
07:46 o1e9 joined #salt
07:55 gmocanu joined #salt
07:56 willprice94 joined #salt
08:02 geomacy joined #salt
08:09 mikecmpbll joined #salt
08:14 ronnix joined #salt
08:15 sh123124213 joined #salt
08:17 bdrung_work joined #salt
08:17 XenophonF joined #salt
08:19 ronnix joined #salt
08:20 mikecmpbll joined #salt
08:28 darioleidi joined #salt
08:29 cyborg-one joined #salt
08:30 darioleidi joined #salt
08:31 willprice joined #salt
08:31 Mattch joined #salt
08:38 ronnix joined #salt
08:40 BernhardG joined #salt
08:41 zerocool_ joined #salt
08:42 s_kunk joined #salt
08:42 s_kunk joined #salt
08:43 nikdatrix joined #salt
08:44 BernhardG Good day everybody. Yesterday I reported problems with the new version 2016.11.4 and CentOS in combination with Cryptodome. Now I found out the reason why my keys were not accepted anymore - they are using insecure exponents (as the key was generated with a salt version before mid 2013 - https://github.com/saltstack/salt/issues/40889). Now I need help to exchange my (insecure) master keys. Could someone please help me?
08:44 saltstackbot [#40889][OPEN] salt-master 2016.11.4 crashes on CentOS 7 with error "RSA key format is not supported" | Description of Issue/Question...
08:45 benner does anyone saw this error: https://gist.github.com/anonymous/ac34b3f71a0e229afa780876938ba447 and have solution?
08:52 Rumbles joined #salt
09:00 FuzzyVeg joined #salt
09:00 ronnix joined #salt
09:06 Dmitry joined #salt
09:09 jas02 joined #salt
09:21 jas02 joined #salt
09:22 zerocoolback joined #salt
09:24 Kelsar joined #salt
09:28 antpa joined #salt
09:41 Sarphram joined #salt
09:48 jhauser joined #salt
10:00 XenophonF benner: any context for what you're doing when you get that exception?
10:03 willprice joined #salt
10:04 noob_ joined #salt
10:17 sh123124213 joined #salt
10:20 zerocoolback joined #salt
10:25 FuzzyVeg joined #salt
10:26 ronnix joined #salt
10:26 legreffier joined #salt
10:32 Praematura joined #salt
10:35 zerocool_ joined #salt
10:35 ronnix joined #salt
10:41 zerocoolback joined #salt
10:53 seaman joined #salt
10:55 seaman left #salt
11:03 ronnix joined #salt
11:07 antpa joined #salt
11:16 edrocks joined #salt
11:17 sh123124213 joined #salt
11:25 evle1 joined #salt
11:31 Miouge left #salt
11:33 BernhardG The usage of `salt-run manage.key_regen` messed up my previously working salt network quite badly.
11:34 BernhardG I have to manually call `salt-call test.ping` on every minion to reconnect it to the master.
11:34 Xenophon1 joined #salt
11:46 willprice joined #salt
11:53 hemebond left #salt
12:01 nikdatrix joined #salt
12:03 pbandark joined #salt
12:12 rem5 joined #salt
12:16 Tanta joined #salt
12:17 squishypebble joined #salt
12:18 demize IIRC you should just have to restart the master and then wait a bit for them to reconnect.
12:19 sh123124213 joined #salt
12:21 BernhardG demize, that's the theory. I wait since about 2 hours now. Many (Linux) minions are back but not one of the Windows minions. If I call a `salt-call test.ping` the minion connects to the master.
12:22 BernhardG That is a lot of work. But it is still better than insecure keys or unable to upgrade to 2016.11.4
12:22 demize BernhardG: And did you restart the master within 60 seconds?
12:23 amcorreia joined #salt
12:23 edrocks joined #salt
12:25 Dev0n joined #salt
12:26 BernhardG demize, yes - `salt-run manage.key_regen` + `service salt-master restart` - all within 45 seconds.
12:27 BernhardG Are there any config settings that could prevent a reconnect?
12:34 Praematura joined #salt
12:35 numkem joined #salt
12:39 Brew joined #salt
12:53 numkem joined #salt
12:54 antpa joined #salt
12:55 jdipierro joined #salt
12:58 pbandark I have configured external pillar but, I can see that all external pillar data is visible to all minions. How to control the targets for external pillar ?
12:59 jas02 joined #salt
13:06 racooper joined #salt
13:09 Miouge joined #salt
13:15 Pyro_ joined #salt
13:15 tapoxi joined #salt
13:18 rdas joined #salt
13:23 tapoxi joined #salt
13:30 brousch__ joined #salt
13:33 ronnix joined #salt
13:35 asyncsec joined #salt
13:38 squishypebble joined #salt
13:42 cmarzullo pbandark: early on in your external pillar module you want to do a check to see if you to hit the external pillar for the minion.
13:43 pbandark cmarzullo: any document which I can refer for an example ?
13:44 cmarzullo not really. I just ran into the same problem. Within the ext pillar configuration on the master I include a value that is a regex for the minions I want to run against. Then early on I compare the minion id against the regex.
13:45 it_dude joined #salt
13:48 pbandark cmarzullo: >> Within the ext pillar configuration on the master I include a value that is a regex for the minions I want to run against. << == can you tell me exactly which config file you edited with what syntax ?
13:50 nutcase_ joined #salt
13:50 nutcase_ Good efternoon.
13:51 nutcase_ Been trying to get a formula to work for hours now. Anyone that can give me a hand?
13:51 nutcase_ The formula in question: https://github.com/saltstack-formulas/vmware-tools-formula
13:54 VR-Jack-H joined #salt
14:06 jas02 joined #salt
14:07 sarcasticadmin joined #salt
14:11 mpanetta joined #salt
14:11 benner XenophonF: I only use for cmd.run
14:11 benner and some returners sync
14:12 mpanetta joined #salt
14:14 rdas joined #salt
14:15 benner Xenophon1: and looking around in logs, it happend with receiving msg (look at times): https://gist.github.com/anonymous/bc37ab8610467cdb2db045eb98069033
14:16 benner probably it was receicing new cmd.run message
14:17 darioleidi joined #salt
14:20 sh123124213 joined #salt
14:21 Aleks3Y joined #salt
14:27 mat_ I was looking for a vim syntax file for jinja and there are several, is there one recommended ?
14:27 jdipierro joined #salt
14:27 fracklen joined #salt
14:28 mat_ (or for salt as a whole)
14:28 GrokZen joined #salt
14:29 GrokZen Hi. I got a ERROR in the logs in the latest 2016.11.4 release but i see no exception stack trace. how do i get the stacktrace to be printed? error is in the master
14:30 heaje joined #salt
14:30 dev_tea joined #salt
14:33 BernhardG GrokZen, you could run the salt-master in foreground with `salt-master -l debug`.
14:34 BernhardG GrokZen, do you by chance use Salt since beginning of 2013 or even earlier?
14:34 jas02 joined #salt
14:35 mat_ in a sls/jinja file, what is the difference between running salt['pillar.get']('bob') and pillar.get('bob') ?
14:35 GrokZen i run it with `salt.master -l all` and i get only the following 3 lines
14:35 GrokZen https://gist.github.com/Grokzen/4723f7917ec991d2668d12e34fe88ec6
14:36 Praematura joined #salt
14:36 GrokZen i have the following line in the file log
14:36 GrokZen 2017-04-27 17:26:09,341 [salt.transport.ipc][ERROR   ][29536] Exception occurred while handling stream: 'int' object has no attribute '__getitem__'
14:36 GrokZen that is it
14:36 deuscapturus joined #salt
14:37 GrokZen 3 minions connected to the master, i can run commands on all 3 minions, minions is 2015.5.6
14:37 GrokZen error happens every 30 seconds
14:41 deuscapturus joined #salt
14:43 BernhardG GrokZen, unfortunately I don't know the reason for this error message. Sorry.
14:43 scoates joined #salt
14:44 tercenya joined #salt
14:44 GrokZen kinda hard to track down without stack trace :P
14:45 fracklen joined #salt
14:55 dyasny joined #salt
14:57 promorphus joined #salt
14:58 megamaced joined #salt
14:59 DammitJim joined #salt
15:02 zerocoolback joined #salt
15:02 tkharju joined #salt
15:03 zerocoolback joined #salt
15:07 jdipierro joined #salt
15:09 promorphus Anyone know of a good way to check if a webservice is running in salt before proceeding to the next state / step? I'm currently doing an http.query, but if the server isn't up, i get the  following error -- https://gist.github.com/promorphus/acdcf32d64c0b11beab3eab6afac916d.   Here's the actual state that's running -- https://gist.github.com/promorphus/3e0b577fc27f3ea094533951cacddfa4
15:10 promorphus Apparently, salt handles non-200's or non-status codes just fine, but an exception soils the bed
15:11 fracklen joined #salt
15:11 TCShain joined #salt
15:12 TCShain Thanks to whytewolf and cmarzullo for your help yesterday!
15:12 TCShain I was able to figure out the problem and am engineering a fix! Most appreciated!
15:12 TCShain Excellent introduction to the salt IRC community.
15:13 cmarzullo TCShain: Great!
15:14 cmarzullo pbandark: sorry I stepped away. In /etc/salt/master under ext_pillar
15:14 pbandark cmarzullo: np
15:14 pbandark would you mind pastebin the config you used if possible ?
15:15 cmarzullo so extpillar: [{'my_extpillar': {'matcher': 'my_minon'}}]
15:16 cmarzullo so ext_pillar: [{'my_extpillar': {'matcher': 'my_minon'}}]
15:16 cmarzullo I can't really paste bin it since it's all custom stuff.
15:16 dev_tea joined #salt
15:16 Praematura joined #salt
15:17 asyncsec joined #salt
15:17 cmarzullo But the long and short of it is that the configuration under ext_pillar gets passed into the ext_pillar module so you can use the values in there to do things.
15:18 pbandark ok
15:18 pbandark cmarzullo:
15:18 pbandark thanks. let me give a try
15:21 omegamike joined #salt
15:26 antpa joined #salt
15:27 dev_tea joined #salt
15:31 ecdhe I'm trying to manage some ubiquiti edgerouters through salt.  The ERLite-3 I'm working on has python already, and with the debian repos, "apt-get install python-pip" worked, but "pip install salt" fails.
15:31 XenophonF joined #salt
15:32 ecdhe Then I look and see that debian.saltstack.com used to have a mips repo, but repo.saltstack.com doesn't...
15:33 zerocoolback joined #salt
15:35 fracklen joined #salt
15:36 EvaSDK any saltstack-formulas people around ? I still have merge request to get approved :/
15:36 ecdhe Besides tapping out and going with salt-ssh, is there a recommended route for getting salt to work on my MIPS devices?
15:37 amcorreia joined #salt
15:40 Sketch {% if grains['osrelease_info'][1] >= 2 %}
15:40 Sketch Rendering SLS failed: Jinja variable tuple object has no element 1
15:41 onlyanegg joined #salt
15:41 Sketch on some OS versions, osrelease_info is a single value, and on others it has multiple values.  how can i test for this?
15:41 jeffspeff joined #salt
15:43 ronnix joined #salt
15:43 Sketch oh wait, the reason it's missing is because i have an old minion version.
15:44 Sketch though i didn't have anything left on 2015.8, but i guess this system got left behind.
15:44 PatrolDoom joined #salt
15:49 whytewolf ecdhe: try the bootstrap install with the git method.
15:50 ecdhe whytewolf, will report back!
15:53 ronnix joined #salt
15:54 aldevar left #salt
15:55 PatrolDoom joined #salt
15:58 Splix76 joined #salt
16:00 nicksloan joined #salt
16:03 nixjdm joined #salt
16:06 frew So I asked a couple days ago about how to prepend some content to a template with a file, I think I have that wired up, but it's running after the other one runs with a `watch` command, but I have a bootstrapping problem where I need it to run even if the other one doesn't change for the very run change; should I maybe replace the `watch` with an `onlyif` and look for a string in the file or something?
16:09 censorshipwreck joined #salt
16:09 whytewolf frew: why not require?
16:09 frew I don't really know honestly; my coworkers said that watch was more predictable IIRC
16:10 frew I can never keep the various requisites straight in my mind
16:10 frew but do you see what I mean about using onlyif so that it bootstraps correctly?
16:11 whytewolf okay, watch = run mod_watch function of state if x = change. require means run state if x = true or change
16:12 whytewolf you can do an onlyif. if you want. seems like more work. and less "predictable"
16:13 frew nah I don't really prefer to
16:13 frew it's more predictable to me, but that's because I am not a salt lord ;)
16:13 monjwf joined #salt
16:14 whytewolf also not sure what state you are using. watch can have very different things happen based on what state it is in.
16:14 it_dude joined #salt
16:14 tapoxi joined #salt
16:15 frew yeah I get that.
16:16 frew I think I'm just gonna play with it and see if it works well.  What I worry about is that a template then prepend will imply a change every time, which is annoying
16:16 frew but I'm not sure if there's a way around that you know
16:17 whytewolf depends on the state being used. if your using cmd.run then yes it will run everytime. if your using one of the file.* states then there are things in there to keep them from running all the time
16:17 frew yeah it's just file.*
16:17 nicksloan joined #salt
16:18 frew let me just paste what it is, sec
16:18 elliot1 Hi, I'm trying to setup an elasticsearch returner. I added this in my master config (tried minion as well) : https://pastebin.com/raw/A1iCesap. I restarted master and minion. When I run `test.ping --return elasticsearch` the result still comes back in the cli and nothing in elasticsearch.
16:18 elliot1 Am I missing something?
16:19 whytewolf elliot1: iirc the elasticsearch does not currently work for the master_job_cache.
16:19 frew whytewolf: http://paste.scsys.co.uk/559060
16:19 PatrolDoom joined #salt
16:20 whytewolf okay, does it really matter that the managed is first and the prepend second?
16:20 elliot1 whytewolf: So does that mean that you can't set up logs for elasticsearch right now?
16:20 frew no not at all
16:20 whytewolf [most of the time no]
16:21 whytewolf let me test something
16:22 sh123124213 joined #salt
16:23 woodtablet joined #salt
16:26 ronnix joined #salt
16:28 whytewolf humm. lovely. okay. this wouldn't work... file.managed is going to delete the file.prepend everytime which is going to cause the file.prepend to run everytime
16:28 frew right.
16:28 whytewolf even with onlyif
16:28 frew yeah
16:29 frew the only solution I can think of is to write my own module
16:29 frew or just try not to care :)
16:29 whytewolf or some how get the contents of your prepend into the file.managed template.
16:29 whytewolf so you don't need the prepend
16:29 frew hm.
16:29 frew maybe make a wrapper template
16:30 frew is that a thing in salt / jinja?  Where the inner templates are wrapped with an outer one that they don't need to know about?
16:31 PatrolDoom joined #salt
16:31 whytewolf iirc they are called blocks
16:31 whytewolf been a while since i used them in jinja [in my pre salt days]
16:32 whytewolf http://jinja.pocoo.org/docs/2.9/templates/#template-inheritance
16:32 frew perfect
16:32 frew I don't love having to extend the base one
16:32 frew but if I have to do it... oh well
16:33 whytewolf well in all honestity might make the hole thing run faster as you don't have multiple file states that can take more time
16:33 frew sure
16:33 frew btw is the Duration that salt reports for a single statement accurate?
16:34 whytewolf it doesn't count overhead
16:34 frew interesting
16:34 frew the prepend state here is saying 2.3ms
16:34 frew which seems *really* high
16:35 whytewolf that does seem high.
16:35 pipps joined #salt
16:35 Deliant joined #salt
16:37 frew so just fyi, I am willing to do the block inheritance thing, but for something that you care about (and I really care about this) it seems like a frustrating compromise, because inevitably someone will forget to do the extend call and end up missing the prelude
16:38 frew but so it goes.
16:38 mpanetta joined #salt
16:41 Shirkdog joined #salt
16:41 promorphus joined #salt
16:51 AvengerMoJo joined #salt
16:56 darvon joined #salt
16:57 pipps joined #salt
17:05 pipps joined #salt
17:13 Trauma joined #salt
17:18 elliot1 Has anyone else had experience with getting an eleasticsearch returner up?
17:20 riftman joined #salt
17:23 kwork joined #salt
17:24 Tanta joined #salt
17:25 Edgan joined #salt
17:25 whytewolf elliot1: https://github.com/saltstack/salt/issues/23125
17:25 saltstackbot [#23125][OPEN] Elasticsearch as master_job_cache throws critical | Hi all,...
17:27 ChubYann joined #salt
17:28 cscf MTecknology, were you working on the 'network' state earlier?  I'm working on fixing the behavior with Debian "source" lines
17:28 __number5__ joined #salt
17:28 Rumbles joined #salt
17:29 MTecknology cscf: I was, but dear god please don't have any hard questions...
17:30 MTecknology (i.e. the entire bloody thing!) :P
17:31 cscf MTecknology, lol.  I wish Python had proper (IMHO) types
17:31 cscf Or rather, made you specify the type of your arguments
17:32 MTecknology I'm iffy..
17:32 whytewolf Meh, there are times i want that. and times i'm glad i don't
17:32 MTecknology I'd like static typing with an undefined type option
17:33 cscf MTecknology, right now I'm looking at modules/debian_ip.py , _parse_settings_source()
17:33 whytewolf i could live with that
17:33 cscf IMHO dictionaries already give you all the flexibility you need with types
17:33 MTecknology I don't think I had to touch that one so I might not be any help, but I can take a look
17:33 cscf Making you say "this function takes a dict, which holds anything" is still better than "takes a thing called x"
17:35 MTecknology I often go over-kill on my checks in python and in public functions frequently have things like if not type(foo) == dict: _whatever_break()
17:35 s_kunk joined #salt
17:35 s_kunk joined #salt
17:36 cscf Yeah, which IMHO should be implicit by specifying the type.  Or at least optionally enforced.
17:36 cscf Apparently dynamic languages where types are optional is a hot area of research.
17:37 whytewolf i like the way php went with static typing. it CAN be there but doesn't have to be
17:37 whytewolf [one of the few things i like about php]
17:37 MTecknology php does it?
17:37 MTecknology see, now I hate the idea
17:37 cscf lol
17:37 whytewolf lol
17:38 elliot1 whytewolf: Thanks for that! I actually just went to send the return to elasticsearch and not the job_cache. I might be going about this the wrong way. I'm not getting any errors in logs, I feel like it's just not loading my configuration
17:38 whytewolf elliot1: have you restarted the minion after you made the config change?
17:39 elliot1 yes
17:39 whytewolf elliot1: then turn up the debugging
17:39 elliot1 `-l debug`?
17:40 whytewolf logsince you are wondering about something that happens in the loading you either need to start the salt-minion deamon with -l debug from the cli or turn up the logging level
17:40 whytewolf https://docs.saltstack.com/en/latest/ref/configuration/logging/#log-level-logfile
17:42 MTecknology cscf: When I was playing with the networking stuff, to figure out what the flying crap was going on, I traced through it a lot of times line by line with pudb
17:42 sh123124213 joined #salt
17:42 cscf MTecknology, oh that looks handy
17:43 sp0097 joined #salt
17:43 MTecknology It's a little tricky to get used to, and you need to keep salt from forking, but otherwise *very* helpful
17:44 whytewolf if you have pycharm you should be able to use it's trace
17:46 thinkt4nk joined #salt
17:47 thinkt4nk is there a way to list the pillars that would be applied to a minion, _from_ the minion?
17:47 whytewolf thinkt4nk: piller.items
17:47 whytewolf it isn't what would be applied but that is applied
17:48 MTecknology .items, eh? I've always used .data
17:48 thinkt4nk thanks whytewolf
17:48 cscf _parse_settings_source(parsed, "source", True, "source")['source']['data']['sources'][0]['data']['sources']    wtf?
17:49 whytewolf MTecknology: .data is to .get as .items is to .item
17:49 MTecknology I gotta play now... (later)
17:49 MTecknology salt... every day a new lesson
17:50 whytewolf least iirc that is how .data works.
17:50 whytewolf .data doesn't really show up in the docs :P
17:51 MTecknology I was just noticing that too
17:52 whytewolf anyway. in short. iirc .data uses the pillar cache like .get does. and .items pulls directly from the master
17:52 MTecknology nice, thanks for the explanation :)
17:53 whytewolf but i could be wrong about .data ... been a while since i actually looked i up
17:54 MTecknology I think it may have been removed.... I don't see it in the source of develop
17:55 whytewolf data = salt.utils.alias_function(items, 'data')
17:55 whytewolf i was wrong
17:55 whytewolf .data = .items
17:55 MTecknology oh, and that's why I couldn't find it
17:56 whytewolf yeap, it is just an alias
17:56 whytewolf there are times i wish there was a .get version of .items
17:56 elliot1 whytewolf: I'm seeing this in the logs: http://paste.awesom.eu/raw/gxwl that is a return correct ?
17:57 whytewolf that is an event. [part of the event bus]
17:57 whytewolf although it is a job return event so the return should be around there
17:58 Sketch joined #salt
17:58 whytewolf ohhh pillar.ls
17:59 elliot1 whytewolf: This is the whole log: http://paste.awesom.eu/raw/lEKF . Yeah I figured it was a return, but the retunr is still comming out in the cli, so maybe it's the cli's return ?
18:00 whytewolf elliot1: you might need to bump up to trace
18:00 whytewolf elliot1: this line is just after where the return should be Got return from stage01.bo.internal for job 20170427175402712506
18:01 whytewolf elliot1: that line isn't a return but a job return event. basicly it is to let the event bus know that a return happened.
18:01 elliot1 ah ok
18:02 whytewolf also, even with a returner you should still get cli returns iirc. because the job_cache requires them
18:03 whytewolf now, i need to go do some reading on elasticsearch curator to see how badly they changed it since 3
18:06 elliot1 whytewolf: okay thank you, I followed this: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.elasticsearch.html
18:07 elliot1 I pip installed the matching version of elasticsearch
18:07 elliot1 and added the conf in my minion conf file like I mentionned earlier
18:08 whytewolf that ... is not a returner
18:08 whytewolf https://docs.saltstack.com/en/latest/ref/returners/all/salt.returners.elasticsearch_return.html#module-salt.returners.elasticsearch_return
18:08 elliot1 wrong link, my bad
18:08 elliot1 yes that one
18:09 Brew joined #salt
18:14 mikecmpbll joined #salt
18:17 aldevar joined #salt
18:23 hemphill joined #salt
18:25 SalanderLives joined #salt
18:33 ahrs joined #salt
18:35 andi- joined #salt
18:36 Rumbles joined #salt
18:37 hexa- joined #salt
18:37 tharkun_ joined #salt
18:38 bfritz_ joined #salt
18:38 shallot joined #salt
18:38 filippos_ joined #salt
18:38 froztbyt1 joined #salt
18:38 davroman1ak joined #salt
18:38 Arendtse1 joined #salt
18:38 Xenophon1 joined #salt
18:38 Edur joined #salt
18:39 lstor joined #salt
18:39 rofl____ joined #salt
18:39 CeBe joined #salt
18:40 rem5 joined #salt
18:42 rem5 joined #salt
18:42 cliluw joined #salt
18:46 hexa- joined #salt
18:50 nicksloan joined #salt
18:55 geomacy joined #salt
19:03 hexa- joined #salt
19:05 rem5 joined #salt
19:07 Aleks3Y joined #salt
19:09 jrklein joined #salt
19:15 aneeshusa joined #salt
19:15 zinzinzin joined #salt
19:29 nikdatrix joined #salt
19:30 candyman88 joined #salt
19:31 hoonetorg is augeas broken in 2016.11.4?
19:32 hoonetorg downgrading to 2016.3.4 makes it work again
19:33 hoonetorg anybody here knows about problems
19:39 cscf hoonetorg, you should try intermediate versions to locate the bug
19:39 prg3 joined #salt
19:42 hoonetorg cscf: ok "yum dowgrade" -> :heart:
19:42 cscf hoonetorg, not on a production system, ofc...
19:43 cscf hoonetorg, also look through https://github.com/saltstack/salt/issues?utf8=%E2%9C%93&amp;q=is%3Aissue%20is%3Aopen%20augeas
19:47 hoonetorg cscf: thx
19:54 sh123124213 joined #salt
19:58 rubenb joined #salt
20:01 sh123124213 joined #salt
20:04 rem5 joined #salt
20:04 MTecknology cscf: you ever play on the develop branch much?
20:04 cscf MTecknology, not really, I intend to set up a VM or two with it
20:06 hoonetorg regarding augeas on 2016.11.4: it seems that https://github.com/saltstack/salt/pull/38115 is the cause
20:06 saltstackbot [#38115][MERGED] Revert "fix augeas module so shlex doesn't strip quotes" | Reverts saltstack/salt#34643--this causes quotes to remain where they should have been eliminated.  Recommend if quotes need to be left alone, to escape them.
20:07 aneeshus1 joined #salt
20:08 sh123124213 joined #salt
20:09 hoonetorg the revert should be merged into 2016.11.1. according to https://github.com/saltstack/salt/issues/38078
20:09 saltstackbot [#38078][MERGED] Broken configuration files due to Augeas change | In PR #34643, a change was made to support quotes in arguments. However this change results in every augeas value being inserted with quotes....
20:09 hoonetorg but is still/again there in 2016.11.4
20:11 sh123124_ joined #salt
20:11 aldevar joined #salt
20:13 swills joined #salt
20:15 aldevar1 joined #salt
20:18 sh123124213 joined #salt
20:25 fleaz joined #salt
20:27 promorphus joined #salt
20:27 aneeshusa joined #salt
20:30 sh123124213 joined #salt
20:37 hoonetorg updated pr and issue report
20:39 btorch left #salt
20:50 promorphus joined #salt
20:51 aldevar1 left #salt
20:53 aneeshusa joined #salt
20:57 ConnorCG joined #salt
21:01 NicoV joined #salt
21:02 mpanetta joined #salt
21:03 mpanetta joined #salt
21:09 woodtablet left #salt
21:10 sqwishy joined #salt
21:15 mpanetta joined #salt
21:20 onlyanegg joined #salt
21:21 SalanderLives joined #salt
21:22 asyncsec joined #salt
21:30 geomacy joined #salt
21:30 nikdatrix joined #salt
21:32 hemebond joined #salt
21:54 jauz joined #salt
21:54 jauz Is there any real difference between using GitPython/pygit/Dulwitch for GitFS backend functionality? Seems up to preference from what I can tell.
21:55 jauz I'm on a CentOS 7 Salt Master, so some of the potential issues mentioned in the docs are all I can see so far.
21:59 aneeshusa joined #salt
21:59 _JZ_ joined #salt
22:08 whytewolf there is major differences between them. pygit2 is a git client in it's self useing libgit2. as such gives access to security features for logging into git repos. GitPython uses the git client installed on the operating system. as such it requires the git client to be able to login with out interaction. Dulwitch i have never used but from what i understand it goes through the same thing as gitpython
22:10 whytewolf if you are not going to be logging into a git repo at all in any kind of backend. then gitpython is fine. if any of them needs user/password then use pygit2
22:11 c4rc4s joined #salt
22:11 whytewolf if you use ssh based... gitpython has workarounds. [XenophonF can walk you through those]
22:13 Laogeodritt joined #salt
22:14 sknebel_ joined #salt
22:14 godber joined #salt
22:14 jor_ joined #salt
22:14 lubyou_ joined #salt
22:15 c4rc4s joined #salt
22:16 mschiff joined #salt
22:16 mschiff joined #salt
22:17 spaceman_spiff joined #salt
22:17 StolenToast joined #salt
22:17 Rkp joined #salt
22:18 Tanta joined #salt
22:19 eightyeight joined #salt
22:19 wonko21 joined #salt
22:19 jauz Ah, it would be a privite Bitbucket repo, so I suppose I will need to use pygit2.
22:19 jauz Thank you.
22:19 stotch joined #salt
22:20 Xevian joined #salt
22:20 scarcry joined #salt
22:20 inire joined #salt
22:21 supermike_ joined #salt
22:22 tercenya joined #salt
22:22 justanotheruser joined #salt
22:22 adongy joined #salt
22:25 theanalyst joined #salt
22:26 jas02 joined #salt
22:28 antpa joined #salt
22:28 prg3 joined #salt
22:31 Savemech joined #salt
22:48 cyborg-one joined #salt
22:51 sarlalian joined #salt
23:13 asyncsec joined #salt
23:17 hexa- joined #salt
23:22 bunjamins joined #salt
23:23 antpa joined #salt
23:30 jdipierro joined #salt
23:31 nikdatrix joined #salt
23:35 onlyanegg joined #salt
23:35 nicksloan joined #salt
23:37 upb joined #salt
23:39 nicksloan joined #salt
23:42 antpa joined #salt
23:47 thinkt4nk joined #salt
23:50 nicksloan joined #salt
23:51 justanotheruser joined #salt
23:52 sh123124213 joined #salt
23:57 mrueg joined #salt

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