Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2018-04-11

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

All times shown according to UTC.

Time Nick Message
00:00 onslack joined #salt
00:17 cewood joined #salt
00:26 aphor extend in state.sls is giving me an exception in the state compiler :( :( :(
00:26 aphor anyone seeing anything like this in 2017.7.5?
00:26 aphor https://gist.github.com/aphor/6cf8d4807d02a48e058c24b4daaf13ae
00:28 zer0def is your cmd cut off on purpose?
00:29 zer0def cmd in the extend statement
00:29 aphor I redacted it because it succeeds parsing everything to highstate but fails to get lowstate because the exception in salt.state.reconcile_extend()
00:34 aphor NM. I walked it back.
00:34 aphor It's not actually doing show_highstate for me now, so I need to figure that out.
00:37 aphor I was doing some sketchy stuff in yaml+jinja that I need to rewrite as a python sls.
01:20 fernie joined #salt
01:30 sreddy joined #salt
01:56 ilbot3 joined #salt
01:56 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2017.7.5, 2018.3.0 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ <+> See also: #salt-devel, #salt-offtopic, and https://saltstackcommunity.herokuapp.com (for slack) <+> We are volunteers and may not have immediate answers
01:58 JPaul joined #salt
02:06 shiranaihito joined #salt
02:32 tiwula joined #salt
02:33 zerocoolback joined #salt
02:34 zerocoolback joined #salt
02:40 jab416171 joined #salt
03:07 justan0theruser joined #salt
03:11 noobiedubie joined #salt
03:14 sreddy joined #salt
03:26 swa_work joined #salt
03:28 chesty joined #salt
03:37 noobiedubie joined #salt
03:57 aldevar joined #salt
04:13 zerocoolback joined #salt
04:24 evle joined #salt
04:25 dezertol joined #salt
05:03 joshin joined #salt
05:03 joshin joined #salt
05:10 stewgoin joined #salt
05:10 Bryson joined #salt
05:17 sauvin joined #salt
05:23 xet7 joined #salt
05:53 swa_work joined #salt
06:13 darioleidi joined #salt
06:44 BHauser joined #salt
06:45 onmeac joined #salt
06:49 BHauser Hi all, after upgrading salt-master / salt-minions to 2018.3.0 i'm unable to run highstates anymore. The message is "No Top file or master_tops data matches found.". I'm using "/usr/bin/foreman-node" as master_tops and there is no top.sls in my "file_roots".
06:49 BHauser when i run manually "/usr/bin/foreman-node <minion-id>" i am receiving the expected yaml output.
06:50 BHauser I've read https://docs.saltstack.com/en/latest/topics/releases/2018.3.0.html#master-tops-changes but setting "master_tops_first: True" on the minion makes no difference.
06:53 briner joined #salt
07:03 aldevar joined #salt
07:04 aldevar1 joined #salt
07:05 aldevar2 joined #salt
07:06 aldevar3 joined #salt
07:07 aldevar4 joined #salt
07:08 aldevar5 joined #salt
07:08 zer0def incoming spam?
07:20 fernie BHauser: same here, not really looked into it yet, changed repositories to point to 2017.7 in the mean time..
07:21 tyx joined #salt
07:22 BHauser fernie: ack, i'm investigating it right now but don't have much time today. If i find something i'll let you know.
07:24 fernie also on debian stretch salt master updated to 2018.3.0 getting these when trying to send salt event /usr/lib/python2.7/dist-packages/salt/transport/zeromq.py:342: RuntimeWarning: IOLoop.current expected instance of <class 'zmq.eventloop.ioloop.ZMQIOLoop'>, got <tornado.platform.epoll.EPollIOLoop object at 0x7f9d5b462390>
07:25 fernie after that salt master stops responding, so thats bad. needed to downgrade
07:25 BHauser ack, fyi i'm on centos 7.
07:25 fernie i have everything on debian 9
07:29 Pjusur joined #salt
07:34 BHauser Also i see the following error on the salt-master when running a highstate on the salt-minion:
07:34 BHauser [ERROR   ] Top function ext_nodes failed with error 'int' object has no attribute 'communicate' for minion <redacted minion-id>
07:48 mikecmpbll joined #salt
07:56 xet7 joined #salt
08:07 Pjusur joined #salt
08:09 briner joined #salt
08:25 xet7 joined #salt
08:26 Ricardo1000 joined #salt
08:29 Elsmorian joined #salt
08:29 Mattch joined #salt
08:33 onslack_ joined #salt
08:38 briner joined #salt
08:40 zerocool_ joined #salt
08:40 briner_ joined #salt
08:44 darioleidi joined #salt
08:51 zer0def oh, actually, boto_asg works fine… from outside AWS
09:00 DanyC joined #salt
09:01 DanyC joined #salt
09:17 Mogget joined #salt
09:24 ProT-0-TypE joined #salt
09:27 zulutango joined #salt
09:34 BHauser fernie: Found it! in the file "/usr/lib/python2.7/site-packages/salt/tops/ext_nodes.py" on line 83, change "stdout=subprocess.PIPE.communicate()[0])" into "stdout=subprocess.PIPE).communicate()[0]".
09:34 BHauser w00t!
09:35 eightyeight joined #salt
09:36 copec joined #salt
09:43 BHauser Ah, in de develop branch on github it is already fixed. https://github.com/saltstack/salt/commit/3655569322389b2d7932a13d056110fd94c911d5
09:43 fernie BHauser: ok thanks!
09:44 ProT-0-TypE is fire_event in a state supposed to work with masterless minions?
09:44 ProT-0-TypE it doesn't really work for me
09:44 BHauser fernie: My pleasure.
09:52 SteamWells_ left #salt
10:33 BHauser left #salt
10:48 Elsmorian joined #salt
10:56 mikecmpbll joined #salt
11:02 fernie joined #salt
11:19 mikecmpbll joined #salt
11:29 Pjusur joined #salt
11:32 Elsmorian joined #salt
11:52 nickadam joined #salt
12:10 briner joined #salt
12:11 noobiedubie joined #salt
12:13 cbosdonnat joined #salt
12:27 Hybrid joined #salt
12:38 cdunklau how do you run a command if a state fails, like, automaticcally?
12:38 cdunklau preferably also that if the command succeeds, the state doesn't actually fail
12:38 cdunklau real case: if a particular directory does not exist, i want to run a script that will populate it
12:39 cdunklau and only if the script exits nonzero should the state fail
12:41 XenophonF cdunklau: would the onfail requisite do what you want?
12:43 alex-zel joined #salt
12:44 cbosdonnat I'm working on rationalizing the virt module configuration properties... is there a way to deprecate a configuration property?
12:44 cdunklau XenophonF: looks like it, thanks!
12:48 XenophonF cbosdonnat: look at how Salt issues deprecation warnings, e.g., salt.utils.is_windows() in 2018.3.0
12:49 edrocks joined #salt
12:52 cbosdonnat XenophonF, thanks... I wasn't sure if warn_until could be used with config properties
12:52 XenophonF beats me - I forget offhand where config processing takes place, but I'm sure if you grep for those warnings, you'll find it
12:52 AvengerMoJo joined #salt
12:52 XenophonF or search the repo on GitHub
13:06 gh34 joined #salt
13:07 dlloyd_ joined #salt
13:15 cgiroua joined #salt
13:17 racooper joined #salt
13:20 onslack <tmacey> Every time I see someone ask about how to run Salt on python 3 the answer is to "install the python 3 packages" without any reference to instructions for actually doing so. When I run 'apt-cache search salt' there is only one set of packages shown. Has anyone done this successfully and care to share the details?
13:20 onslack <tmacey> Every time I see someone ask about how to run Salt on python 3 the answer is to "install the python 3 packages" without any reference to instructions for actually doing so. When I run 'apt-cache search salt' there is only one set of packages shown. Has anyone done this successfully and care to share the details?
13:32 Elsmoria_ joined #salt
13:36 zer0def tmacey: as far as i can tell, only ubuntu 18.04 currently has the py3 treatment, but your universal solution would be to set up a python3 virtualenv and install salt to it
13:38 pf_moore joined #salt
13:56 cgiroua joined #salt
13:56 hiroshi joined #salt
13:59 Nahual joined #salt
14:02 jrenner joined #salt
14:03 cbosdonnat is there anyone here familiar with the virt module connection code?
14:18 Elsmorian joined #salt
14:32 noobiedubie joined #salt
14:49 briner joined #salt
14:58 Elsmoria_ joined #salt
15:02 tiwula joined #salt
15:19 MTecknology ubuntu 18.04 also runs the master as a separate user, which is pretty neat
15:20 peters-tx This is likely silly, but does anyone know of a way to execute a State from a different State file (without using Include)
15:20 peters-tx Yeah, that seems ridiculous
15:21 peters-tx Hmm
15:23 sreddy joined #salt
15:25 englishm_work joined #salt
15:28 Elsmorian joined #salt
15:30 aldevar joined #salt
15:31 aldevar1 joined #salt
15:32 ecdhe joined #salt
15:48 DanyC joined #salt
15:52 iggy fire an event and have the reactor run the other state?
15:52 iggy or does it have to happen in that context?
15:55 cewood joined #salt
15:58 zerocoolback joined #salt
16:02 dezertol joined #salt
16:07 dendazen joined #salt
16:18 mavhq joined #salt
16:19 tys101010 joined #salt
16:24 Edgan peters-tx: Why would you not want an include?
16:24 Edgan peters-tx: WIthout the include you are going to break the dependecy management
16:28 Edgan Anyone created a state(the wrapper around module kind) that can write files to S3? I see the s3 module, but I want it to be stateful.
16:33 briner joined #salt
16:40 briner joined #salt
17:00 armyriad joined #salt
17:00 sjorge joined #salt
17:08 zerocoolback joined #salt
17:26 edrocks joined #salt
17:40 rollniak joined #salt
17:42 DanyC joined #salt
17:43 DanyC_ joined #salt
17:49 rollniak1 joined #salt
17:49 rollniak joined #salt
17:56 ymasson joined #salt
17:58 VR-Jack-H joined #salt
18:18 esteban joined #salt
18:20 esteban joined #salt
18:21 ecdhe joined #salt
18:25 Bryson joined #salt
18:30 nickadam joined #salt
18:34 copec What event thinger do you guys use so that the salt master pulls in new commits to the salt state tree?
18:37 q1x joined #salt
18:40 MTecknology I use git hooks + salt events + reactor
18:41 MTecknology .. also + sdb + cron, but those aren't needed
18:42 hrumph2 joined #salt
18:42 hrumph2 hi
18:42 hrumph2 is pillar data fetched when you do a highstate?
18:42 copec It seems like git hooks + salt events + reactor is the proper way
18:43 cwright joined #salt
18:43 MTecknology you can also use salt-api to generate the events
18:43 copec hrumph2 I believe it does, although not on a state.apply
18:48 copec When you commit do you call a highstate MTecknology, or do you schedule those?
18:48 whytewolf state.apply calls state.highstate or state.sls
18:49 brokensyntax joined #salt
18:49 copec Then it is state.sls that hasn't refreshed the pillar data, in my experience. Although with 2017.7 state.highstate does
18:53 briner joined #salt
18:54 aldevar joined #salt
19:06 MTecknology I use reactor + sdb + cron + script for scheduling
19:33 mikecmpbll joined #salt
19:40 Hybrid joined #salt
19:44 tom29739 joined #salt
19:53 aldevar left #salt
19:56 noobiedubie anyone have a syntax example of smtp settings in pillar?
20:05 Trauma joined #salt
20:15 Hybrid joined #salt
20:20 IPvSean_ joined #salt
20:20 tom29739 joined #salt
20:21 ipmb_ joined #salt
20:21 mihait_ joined #salt
20:24 stankmac1 joined #salt
20:24 froztbyt1 joined #salt
20:24 Miuku_ joined #salt
20:25 dendazen joined #salt
20:26 daks_ joined #salt
20:27 StarHeart joined #salt
20:27 ThomasJ|d joined #salt
20:28 Dr_Jazz joined #salt
20:30 brokensyntax joined #salt
20:30 systemdave joined #salt
20:31 gomerus[m] joined #salt
20:33 alj[m] joined #salt
20:33 LeProvokateur joined #salt
20:34 vali joined #salt
20:41 mianosm I use a managed file for /etc/ssmtp/ssmtp.conf
20:45 JacobsLadd3r joined #salt
20:47 JacobsLadd3r joined #salt
20:49 nsidhu joined #salt
20:50 ProT-0-TypE joined #salt
20:50 Sammichmaker joined #salt
20:50 Sammichmaker joined #salt
21:32 q1x joined #salt
21:33 DanyC joined #salt
21:35 JawnAuz joined #salt
21:38 JawnAuz If I'm using a hosted ELK service that I'm currently using a Filebeat for, is there a way to have it also watch my Salt-Mast Event Bus? Right now it's just watching my normal Salt-Master log, so any errors/gitfs stuff comes through, but not sure how to get it to watch the event-bus. Do I need a separate returner configured?
21:38 q1x joined #salt
21:39 JawnAuz Was going to try this: https://docs.saltstack.com/en/latest/ref/returners/all/salt.returners.elasticsearch_return.html#module-salt.returners.elasticsearch_return -- But not sure if the right path.
21:39 hemebond JawnAuz: Do you want returner or every event?
21:39 hemebond What info do you want?
21:40 JawnAuz I would like to watch all the traffic coming in, but may eventually want to only send certain event tags. Right now I'll settle for a good feed.
21:46 breshead joined #salt
21:47 whytewolf JawnAuz: I havn't used it personally but take a look at https://github.com/martinhoefling/saltbeat
21:49 JawnAuz Will do. Thank you. Interesting he seems to point directly at the .ipc -- didn't think you could read it like that.
21:55 Hybrid joined #salt
22:07 dendazen joined #salt
22:21 gforgx joined #salt
22:23 gforgx Hi! I'm using salt and napalm type proxy. Is there an option already to authenticate to devices (when calling salt <proxy> net.load_config) to use custom login/password than those configured in proxy? Or is it planned as a feature?
22:24 dwoz joined #salt
22:25 gforgx * username/passwd, I mean.
22:30 rem5 joined #salt
22:32 Hybrid joined #salt
22:38 aphor gforgx: look at the proxy minion. If you can't get auth details from a pillar I'd be very surprised. Its the heaviest use case for pillar...
22:41 gforgx What I'm concerned about is providing a fully privileged account for Salt proxy. For most functions read-only access is OK, but when, e. g., I'm about to use net.load_config I obviously need a fully privileged account.
22:41 gforgx Is there any workaround? Is it possible or is it maybe planned as a feature (or maybe theoretically possible - then I can jump on and try to hack this) to bypass custom login credentials from Salt master to proxy on demand?
22:44 gforgx The idea is to use limited rights account credentials for all the functions and provide fully privileged account credentials when necessary only - manually.
23:02 ipsecguy joined #salt
23:02 Puckel_ joined #salt
23:04 johnkeates joined #salt
23:06 noobiedubie joined #salt
23:13 tom29739 joined #salt
23:55 justanotherus3r joined #salt

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