Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-11-06

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

All times shown according to UTC.

Time Nick Message
00:09 laertus can grains be created on a machine that salt manages via salt-ssh?
00:10 laertus i tried putting some grains in /etc/salt/grains on such a machine, but "salt-ssh '*' grains.items" did not see them
00:28 tiwula joined #salt
00:34 claudekenni joined #salt
00:37 bstevenson joined #salt
00:38 bstevens_ joined #salt
00:40 bsteven__ joined #salt
00:44 bstevenson joined #salt
00:59 bstevens_ joined #salt
01:00 bsteven__ joined #salt
01:00 johnj_ joined #salt
01:03 J0hnSteel joined #salt
01:18 laertus when i do a "salt-ssh '*' test.modules_report" i only see test.* cmd.* config.* and vsphere.* modules
01:18 laertus shouldn't i be seeing a whole bunch of other modules, like network.* and disk.*?
01:18 laertus oh, wait, those are functions that i saw a list of, not modules
01:18 laertus interesting
01:18 laertus there actually were no modules at all
01:20 laertus am i supposed to do something to enable the use of commands like "salt-ssh '*' network.interfaces" or "salt-ssh '*' disk.usage" ?
01:23 laertus i do see that i have the network module installed under:  /usr/lib64/python2.7/site-packages/salt/modules/network.py
01:23 laertus so i should be able to just use it, shouldn't i?
01:25 lastc joined #salt
01:37 shortdudey123 joined #salt
01:43 Shirkdog joined #salt
01:47 iggy never used salt-ssh, but I'd think so
01:50 MTecknology laertus: salt-ssh should push a whole self-contained tarball for it to unpack and run from, which would include modules.
01:52 laertus hmm
01:52 iggy that said, it only pushes what gets used, so it's possible you won't see everything available if you don't have much in your states
01:52 laertus and those modules should be listed when i do a "salt-ssh '*' test.modules_report" shouldn't they?
01:52 laertus ah
01:52 laertus i don't have any states :]
01:52 laertus maybe that's why...
01:53 laertus so i can't do a "salt-ssh '*' network.interfaces" until i have a state that uses the network module?
01:54 iggy no, if you call that module explicitly, it should copy that across
01:55 laertus hmm
01:56 laertus well, i can do "salt-ssh '*' test.ping" and that works... and so does "salt-ssh '*' cmd.run foo" and that works (with any command)
01:58 laertus but when i try "salt-ssh '*' network.interfaces" i get:  https://paste.pound-python.org/show/gdl4WZgLrtLg1SqnQWyC/
01:58 laertus i get the same thing when i try "salt-ssh '*' disk.usage"
01:58 laertus and "salt-ssh '*' test.modules_report" didn't list any modules, just the functions i named earlier
01:59 laertus so i was thinking that maybe this was happening because it didn't have access to those modules for some reason
01:59 iggy that looks like a bad ssh config or something
02:00 laertus it's the default sshd config on a fresh openbsd install (that i'm running in a virtualbox VM on my laptop)
02:00 laertus and salt-ssh doesn't normally give those errors when things like test.ping succeed
02:00 MTecknology iggy: I thought it copied over the entire package
02:01 laertus i can actually take a look in /tmp on the openbsd guest... i did see it copied a bunch of stuff in there
02:01 MTecknology is copying only what's needed a new-er feature?
02:01 johnj_ joined #salt
02:05 user-and-abuser joined #salt
02:08 laertus ok, here's what it copied over:  https://paste.pound-python.org/show/FA0Lg9nV7aF5gyeK5yct/
02:08 noobiedubie joined #salt
02:08 dxiri joined #salt
02:08 laertus in /tmp/.myuser_239339_salt
02:09 laertus it doesn't seem to have many modules
02:13 zerocool_ joined #salt
02:17 laertus by the way, one thing i wanted to mention about that error i was getting:  Unsupported option "gssapiauthentication"
02:18 laertus i managed to track down the part in the salt source where it passes a "GSSAPIAuthentication=no" option to ssh
02:19 laertus and i took it out, and i no longer got that error in those salt-ssh commands, but i still didn't get any output from them
02:19 laertus that option's in /usr/lib64/python2.7/site-packages/salt/client/ssh/shell.py in case anyone's curious, btw
02:22 laertus without that option in shell.py, the result of "salt-ssh '*' disk.usage" looks like this:   https://paste.pound-python.org/show/lXTXjZvdBjNLyCO3Uo7a/
02:27 * MTecknology has never once used salt-ssh and likely never will.
02:30 nixjdm joined #salt
02:32 laertus i just found this github issue:  https://github.com/saltstack/salt/issues/9851
02:32 laertus "salt-ssh - are salt modules (e.g. cp.get_file) supported ? #9851"
02:33 laertus "Eventually, we would like salt-ssh to support all the functionality of normal salt. However, fileserver operations must be wrapped to ensure that the relevant files are delivered with the salt-ssh commands..."
02:34 laertus "For example, we have a state wrapper which compiles the state run on the master, and in the process finds all the references to salt: // paths and copies those files down in the same tarball as the state run. (It does not copy the whole fileserver across) However, we have not done similar wrapping with the cp module and similar at this point."
02:35 laertus also, i recall reading in https://docs.saltstack.com/en/latest/topics/ssh/
02:35 laertus "At the moment fileserver operations must be wrapped to ensure that the relevant files are delivered with the salt-ssh commands. The state module is an exception, which compiles the state run on the master, and in the process finds all the references to salt:// paths and copies those files down in the same tarball as the state run. However, needed fileserver wrappers are still under development."
02:36 laertus i didn't fully understand what that meant when i read it.. not sure if i do even now
02:36 laertus but that might explain why i'm running in to problem with modules in salt-ssh
02:36 laertus maybe it's because "fileserver wrappers are still under development"
02:39 iggy that would only impact modules that did things that interact with the master (i.e. cp.* archive.* etc)
02:40 iggy laertus: what kind of "minion" is this? it almost sounds like salt doesn't understand the system very well
02:41 laertus it's just an openbsd VM
02:41 laertus oh... i think i just realized what the problem is!
02:41 laertus this was a bare, new install of openbsd
02:41 laertus and guess what?
02:41 laertus i never installed bash on it
02:41 laertus so it's just using openbsd's sh
02:42 laertus i bet if i install bash this problem will be fixed
02:53 iggy openbsd is not on the list of supported OSes
02:53 laertus oh, bummer
02:53 laertus well, maybe it'll still work.. gotta try :]
02:53 iggy that seems like something you'd be used to mentioning if you were an OpenBSD user
02:53 XenophonF there's support for OpenBSD in the codebase
02:53 XenophonF https://docs.saltstack.com/en/latest/topics/installation/openbsd.html
02:53 laertus sorry, it is unix.. and salt-ssh did seem to kind of work :]    i think i did mention it was openbsd earlier
02:55 ilbot3 joined #salt
02:55 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.8, 2017.7.2 <+> Support: https://www.saltstack.com/support/ <+> 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
03:02 johnj_ joined #salt
03:22 theham joined #salt
03:32 zerocoolback joined #salt
03:46 zerocoolback joined #salt
03:49 JPT joined #salt
03:54 Vaelatern iggy: openbsd is quite supported by the code, if not by people with money
03:55 theham left #salt
03:56 theham joined #salt
04:03 XenophonF laertus: why not just use a normal salt-master/salt-minion setup?
04:03 XenophonF masterless and salt-ssh are not good places to start IMO
04:03 johnj_ joined #salt
04:04 laertus XenophonF: well, for a couple of reasons
04:05 laertus first, i do want to do some testing while i'm just learning salt, and salt-ssh didn't need almost any setup beyond installing salt on my laptop
04:06 laertus second and more importantly, i want to use salt to set up this server i have running on a VPS to which i don't normally connect to, and which has no way of connecting back to my laptop (which would run the salt master, if i was to use a master/minion setup) unless i first connect to it and set up ssh port forwarding to allow it to connect back
04:07 XenophonF you want to end up in a totally reasonable place, but to get there you're making the learning curve waaaaaay steeper than it needs to be
04:07 laertus eventually i'll definitely be running a master/minion setup in AWS... once i learn more about salt.. and i'll have multiple VMs to play with then
04:07 laertus but first i want the simple task of setting up this server i have on th VPS
04:07 XenophonF that's the thing: salt-ssh ain't simple
04:08 theham laertus: i am just joining in here...so forgive if i lack context...but why not just install the master + minion on your vps and then use it to configure
04:08 laertus well, it seemed simple.. obviously it's lacking something or i'm using it wrong or something
04:08 theham plain old salt is waaay easier to get going that salt-ssh
04:08 XenophonF there's a lot of corner cases in salt-ssh, stuff like making sure it bundles everything you need on the other end
04:08 XenophonF if you're just learning salt, I'd start with the getting started tutorials
04:08 laertus theham: i guess i could install both the master and minion on my single vps server.. i just thought that salt-ssh would be simpler.. .and now i've had masterless recommended to me, and that seems simpler too
04:09 XenophonF https://docs.saltstack.com/en/getstarted/
04:09 XenophonF you can do simple master/minion setups in virtualbox for now
04:09 XenophonF learn how to write formulas and use pillar and so forth
04:09 theham well masterless is a gimped minion so you don't get the full effect. you could certainly run exec modules with salt call, states, etc
04:09 XenophonF and then once you have a working config, try to make it work with salt-ssh
04:10 XenophonF even the tutorial has you start out with a master and minion for the fundamentals
04:10 XenophonF it only introduces agentless stuff later
04:10 laertus what's your opinion on masterless, XenophonF?
04:11 XenophonF I don't have a use case for it.
04:11 mikecmpbll joined #salt
04:11 XenophonF I don't think there's anything wrong with it, BTW, just that I don't have a use for it.
04:12 laertus will a master/minion setup take up more memory than masterless?
04:12 theham not really at all
04:12 theham you are not exactly going to be pushing high volume through that master
04:12 laertus :) true
04:12 laertus but it's an extra process.. and that take memory
04:13 XenophonF how much memory are you talking about?
04:13 laertus i'm not sure.. that's why i was asking
04:13 XenophonF like, are you trying to run servers in less than 64 MB RAM?
04:13 laertus oh, no
04:14 laertus but they do have other things running on them too.. though not a huge amountyet
04:14 XenophonF my smallest minion is 512 MB RAM running FreeBSD 11 and a web server
04:14 laertus is it a master too?
04:14 XenophonF no
04:14 laertus b/c the question earlier was why i didn't run both a master and minion on the VPS box
04:15 XenophonF how big is your VPS box?
04:15 XenophonF and what's its workload?
04:15 laertus have to check... brb
04:17 laertus Memory: Real: 23M/293M act/tot Free: 692M Cache: 197M Swap: 0K/0K
04:17 XenophonF so tiny
04:17 XenophonF nah I wouldn't run a master and a minion on that unless you have swap configured
04:17 laertus according to the plan i'm on, that's a 1 gig machine
04:17 XenophonF yup
04:18 XenophonF salt-minion by itself would be fine
04:18 XenophonF salt-master would be ok too but not if you scale out
04:18 laertus also, on the AWS free tier i have to use only 1 gig VMs
04:18 XenophonF right
04:19 XenophonF well, my recommendation stands: learn Salt using master/minion setups in private VMs at home, then when you have a handle on that, try out salt-ssh
04:20 theham i agree with that recommendation. no need to run that on a small vps when you can do a vm and learn at home
04:20 theham that can allow you to test with multiple vms and simulate more real world scenarios (1 master, 2 minions)
04:20 laertus salt-ssh doesn't seem to be working, though.. at least not for modules i've tried like network.interfaces and disk.usage
04:21 laertus so why don't i go with masterless?
04:22 laertus also, with masterless there at least wouldn't be a permanent resource drain as there would be even with just a minion
04:23 laertus and i don't have to worry about figuring out a way for the minion to connect back to the master
04:23 laertus or, rather, not the figuring out part, but the security considerations that keep me from allowing that in my case
04:24 XenophonF go for it
04:24 XenophonF but i'd still go through the traditional salt-master/salt-minion tutorials on docs.saltstack.com
04:25 XenophonF work up to a masterless setup
04:25 laertus alright, i'll do that
04:25 laertus thank you
04:27 07EAAAIRN joined #salt
04:33 MTecknology the yaml output of jinja is a bit interesting...
04:49 zer0def joined #salt
04:58 XenophonF yay openldap directory is provisioned
04:58 XenophonF will figure out ldaps am morgen
05:00 MTecknology am morgen?
05:01 XenophonF tomorrow
05:01 XenophonF er, today
05:01 XenophonF later today
05:02 XenophonF https://github.com/irtnog/salt-states/blob/development/irtnog-co/openldap-provider.sls
05:02 * MTecknology grumbles @ http://dpaste.com/354GKQ5
05:04 XenophonF woah that's a weird error
05:04 johnj_ joined #salt
05:08 icebal joined #salt
05:12 MTecknology ah.. I see
05:12 MTecknology (maybe)
05:22 MTecknology yup.. dumb typo
05:29 MTecknology there we go...  "salt-run state.orchestrate _orchestrate.cloud_run"  /should/ be provisioning a VM for me. If it were actually doing that, I'd be starting to get a little excited.
05:34 jnials joined #salt
05:35 MTecknology Woohoo!!!!!
05:40 MTecknology well, it created the instance anyway, it didn't actually run the provisioning stuff. It's something anyway, a good stopping point for tonight.
05:46 XenophonF congrats!
05:47 fxhp joined #salt
05:48 zerocoolback joined #salt
05:52 MTecknology When I manually run "salt-call cloud.map_run path=/etc/salt/cloud.map", the VM gets correctly created but the orchestration bit only creates a VM... :S
05:52 MTecknology http://dpaste.com/19B3WPM
05:52 MTecknology OH OH!! I SEE WHY! :D
06:05 MTecknology Of course... when we get to the simple "apt-get install openvpn resolvconf" is totally where it should logically break.  I'm gonna finally try to give up for the night!!
06:05 johnj_ joined #salt
06:10 pjs_ joined #salt
06:19 Diaoul joined #salt
06:21 dnull joined #salt
06:21 felskrone joined #salt
06:29 zerocoolback joined #salt
06:31 inetpro_ joined #salt
06:34 justanotheruser joined #salt
06:37 nledez joined #salt
06:37 shortdudey123 joined #salt
06:39 ahrs joined #salt
06:59 wongster80 joined #salt
07:06 johnj_ joined #salt
07:08 colttt joined #salt
07:08 om2 joined #salt
07:12 Eugene joined #salt
07:12 bildz joined #salt
07:12 dvdmuckle joined #salt
07:12 jacksontj joined #salt
07:12 teratoma joined #salt
07:12 ponyofdeath joined #salt
07:12 Whissi joined #salt
07:12 mechleg joined #salt
07:12 rathier joined #salt
07:12 wryfi joined #salt
07:12 shadoxx joined #salt
07:12 cliluw joined #salt
07:12 irated joined #salt
07:12 darkalia joined #salt
07:12 basepi joined #salt
07:12 Reverend joined #salt
07:12 mishanti1 joined #salt
07:12 Vaelatern joined #salt
07:12 StolenToast joined #salt
07:12 nielsk joined #salt
07:12 ccha joined #salt
07:12 scooby2 joined #salt
07:12 Valfor joined #salt
07:12 Edgan joined #salt
07:12 dober joined #salt
07:12 ws2k3 joined #salt
07:12 drags joined #salt
07:12 elektrix joined #salt
07:13 ws2k3 joined #salt
07:13 cliluw joined #salt
07:14 dagb_ left #salt
07:15 HTTP_____GK1wmSU joined #salt
07:15 chowmeined joined #salt
07:17 HTTP_____GK1wmSU left #salt
07:17 nledez joined #salt
07:18 Miouge joined #salt
07:18 tongpu joined #salt
07:19 BlackSponge joined #salt
07:19 rylnd joined #salt
07:19 Ryan_Lane joined #salt
07:19 hax404 joined #salt
07:23 nledez joined #salt
07:23 nledez joined #salt
07:23 sjorge joined #salt
07:34 zerocoolback joined #salt
07:36 yuhl_ joined #salt
07:37 do3meli joined #salt
07:37 do3meli left #salt
07:47 zerocoolback joined #salt
07:49 Ricardo1000 joined #salt
07:52 zerocoolback joined #salt
07:52 pualj joined #salt
07:57 bigjazzsound joined #salt
08:04 darioleidi joined #salt
08:06 hammer065 joined #salt
08:07 johnj joined #salt
08:11 Hybrid joined #salt
08:11 aldevar joined #salt
08:17 evle1 joined #salt
08:18 zerocoolback joined #salt
08:23 jrenner joined #salt
08:25 robman joined #salt
08:31 mikecmpbll joined #salt
08:43 zerocoolback joined #salt
08:44 zerocoolback joined #salt
08:45 zerocoolback joined #salt
08:46 zerocoolback joined #salt
08:46 usernkey joined #salt
09:02 mikecmpbll joined #salt
09:05 zerocoolback joined #salt
09:07 zerocoolback joined #salt
09:08 zerocoolback joined #salt
09:08 obitech joined #salt
09:08 johnj joined #salt
09:10 pbandark joined #salt
09:15 Processus42 joined #salt
09:17 toanju joined #salt
09:20 SkyRocknRoll joined #salt
09:23 CeBe hi, is there a way to generate a password and use it in two different states in the same sls file? e.g. set the password for mysql user and also configure an application to use it for mysql connection?
09:23 usernkey1 joined #salt
09:23 CeBe so that all instance of the applied formula will use different passwords
09:24 CeBe using google with the keywords salt and password generation is obviously a bit difficult :)
09:26 usernkey joined #salt
09:28 Mattch joined #salt
09:29 kkkkkk joined #salt
09:29 kkkkkk left #salt
09:33 coredumb CeBe: it should be doable
09:34 coredumb you declare a variable that gets the result of your pass generation, then you reuse the variable in the states
09:34 CeBe yeah, I just found this: {% set mysql_pw = salt['random.get_str'](20) %}
09:34 CeBe trying it out now
09:35 coredumb that or you execute your own command
09:37 zerocoolback joined #salt
09:46 ilbot3 joined #salt
09:46 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.8, 2017.7.2 <+> Support: https://www.saltstack.com/support/ <+> 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
09:56 zerocoolback joined #salt
10:07 kbaikov[m] joined #salt
10:07 hackel joined #salt
10:07 freelock joined #salt
10:07 benjiale[m] joined #salt
10:07 psychi[m] joined #salt
10:07 viq[m] joined #salt
10:07 toofoo[m] joined #salt
10:07 jerrykan[m] joined #salt
10:07 gomerus[m] joined #salt
10:07 ThomasJ|m joined #salt
10:07 aboe[m] joined #salt
10:07 theblazehen joined #salt
10:07 rtr63gdh[m] joined #salt
10:07 renaissancedev[m joined #salt
10:07 fujexo[m] joined #salt
10:09 johnj joined #salt
10:12 jhauser joined #salt
10:26 ProT-0-TypE joined #salt
10:32 _KaszpiR_ joined #salt
10:38 dhwt joined #salt
10:40 pewpew joined #salt
10:45 stooj joined #salt
10:55 HTTP_____GK1wmSU joined #salt
10:56 HTTP_____GK1wmSU left #salt
11:01 HTTP_____GK1wmSU joined #salt
11:03 HTTP_____GK1wmSU left #salt
11:10 johnj joined #salt
11:17 HTTP_____GK1wmSU joined #salt
11:19 HTTP_____GK1wmSU left #salt
11:25 colegatron joined #salt
11:42 Deliant joined #salt
11:43 HTTP_____GK1wmSU joined #salt
11:45 HTTP_____GK1wmSU left #salt
11:48 hoonetorg joined #salt
12:08 zerocoolback joined #salt
12:11 johnj joined #salt
12:22 darioleidi joined #salt
12:25 viq Also there's `grains.get_or_set_hash`
12:25 zerocoolback joined #salt
12:31 Cottser joined #salt
12:48 Naresh joined #salt
12:48 toanju joined #salt
12:49 mkn joined #salt
12:49 mkn left #salt
13:10 GMAzrael joined #salt
13:12 GMAzrael_ joined #salt
13:12 johnj joined #salt
13:15 N-Mi joined #salt
13:15 N-Mi joined #salt
13:18 permalac joined #salt
13:20 toanju joined #salt
13:23 m0nky joined #salt
13:24 dragon788 joined #salt
13:24 nahkiss joined #salt
13:24 mrbobbytables joined #salt
13:24 djural joined #salt
13:24 futuredale joined #salt
13:24 simonmcc joined #salt
13:24 SteamWells joined #salt
13:24 johtso joined #salt
13:25 aerbax joined #salt
13:30 magz0r joined #salt
13:37 Tucky joined #salt
13:40 AdamSewell joined #salt
13:41 toanju joined #salt
13:41 GMAzrael joined #salt
13:42 numkem joined #salt
13:46 gh34 joined #salt
13:53 t3rm joined #salt
13:55 usernkey joined #salt
13:56 DanyC joined #salt
14:00 darioleidi joined #salt
14:00 asdf___ joined #salt
14:02 permalac joined #salt
14:06 t3rm joined #salt
14:06 ooboyle joined #salt
14:07 t3rm joined #salt
14:08 t3rm id like to copy only newer files (recursively) from master -> minion, this possible with salt? file.recurse seems to always copy if content differs
14:08 edrocks joined #salt
14:09 toanju joined #salt
14:12 mchlumsky joined #salt
14:17 SkyRocknRoll joined #salt
14:17 noobiedubie joined #salt
14:19 mchlumsky joined #salt
14:36 numkem joined #salt
14:36 user-and-abuser joined #salt
14:38 CampusD joined #salt
14:42 permalac joined #salt
14:45 CampusD joined #salt
14:45 beardedeagle joined #salt
14:45 permalac joined #salt
14:45 racooper joined #salt
14:47 dxiri joined #salt
14:50 CampusD question, on the minion side, is there something similar to salt.runners.jobs.list_jobs to get a list of all of the locally cached jobs?
14:58 enigma82 joined #salt
14:58 enigma82 msg NickServ identify enter123
15:04 GMAzrael joined #salt
15:06 mage_ stupid question, merging of pillar data is only done in the top file?
15:07 mage_ if I'm include: - somesls in foo.sls, shouldn't overriding works in foo.sls ?
15:12 mage_ I have the following: https://gist.github.com/silenius/f2d96cca1e3891a12b5ab75190c459b7 and I'm including webapps.bbpf.dev
15:13 mage_ however, value for "pyramid.debug_all" and "pyramid.reload_all" are still True, even if they are overriden at like 26-27
15:13 mage_ any idea?
15:14 stooj joined #salt
15:14 cgiroua joined #salt
15:15 mage_ err, "are still False" instead of "are still True"
15:16 mage_ (in other words, it's not overriden in webapps.bbpf.dev)
15:16 sxar joined #salt
15:17 t3rm_ joined #salt
15:19 sp0097 joined #salt
15:20 toanju joined #salt
15:21 stankmack joined #salt
15:21 SkyRocknRoll joined #salt
15:24 scbunn joined #salt
15:27 skeeved joined #salt
15:27 AdamSewell joined #salt
15:30 AdamSewell Does anyone know if there is a way to see minions that have not communicated in a period of time/
15:32 lordcirth_work AdamSewell, like, get the exact numbers?
15:33 lordcirth_work You could make a cron job, I guess.
15:33 matwey joined #salt
15:33 AdamSewell lordcirth_work, like i want to clean up old minions that haven't connected in a while
15:33 lordcirth_work AdamSewell, do you regularly have minions that are gone and then reconnect?
15:33 AdamSewell lordcirth_work, yes sir
15:34 Brew joined #salt
15:34 ecdhe joined #salt
15:34 lordcirth_work I'd probably hack together a bash script and run it with cron, myself
15:35 SlicerDicer joined #salt
15:35 SlicerDicer joined #salt
15:42 bstevenson joined #salt
15:43 t3rm joined #salt
15:44 CampusD joined #salt
15:49 bildz saltconf was a lot of fun
15:50 bildz whytewolf: did you give a presentation or just attend?
15:57 CampusD hi guys, question, on the minion side, is there something similar to salt.runners.jobs.list_jobs to get a list of all of the locally cached jobs?
15:58 CampusD I know I can use salt-call saltutil.find_cached_job to find details of a specific job, just wondering how to get the cached jids on the minion
16:07 tom[] how may i write a status string from an sls to the runner log?
16:07 tom[] at present i use cmd.run echo but it's a bit clunky
16:10 CampusD there seems to be two jobs folders on the minion, jobs and minion_jobs. I assume one if for jobs coming from the master the other is from using the salt-call command?
16:11 jas02 joined #salt
16:11 concerti joined #salt
16:19 SkyRocknRoll_ joined #salt
16:19 SkyRocknRoll_ joined #salt
16:20 AdamSewell lordcirth_work, what would i be looking for?
16:24 sp0097 joined #salt
16:24 kellyp joined #salt
16:25 zerocoolback joined #salt
16:27 Sammichmaker joined #salt
16:27 Sammichmaker joined #salt
16:27 lordcirth_work AdamSewell, well, you could run test.ping, record which ones don't respond, repeat that a few times, and when you get x duplicates, salt-key -d foo
16:27 lordcirth_work AdamSewell, although, using the python api might be better
16:29 ouemt joined #salt
16:29 ouemt morning gents
16:33 tiwula joined #salt
16:34 zerocoolback joined #salt
16:56 babilen AdamSewell: You might want to look at presence_events and https://docs.saltstack.com/en/latest/ref/runners/all/salt.runners.manage.html
16:56 whytewolf bildz: I did not. wanted to but ended up in a kind of blur and had no time to work on my talk.
17:03 DanyC joined #salt
17:04 DanyC joined #salt
17:05 DanyC_ joined #salt
17:09 SkyRocknRoll_ joined #salt
17:11 HTTP_____GK1wmSU joined #salt
17:13 quantumsummers joined #salt
17:14 aldevar left #salt
17:15 HTTP_____GK1wmSU joined #salt
17:17 HTTP_____GK1wmSU left #salt
17:19 impi joined #salt
17:21 t3rm how does salt's windows support compare to puppets?
17:21 lroe joined #salt
17:24 gtmanfred try it and see
17:24 gtmanfred it is pretty good
17:24 gtmanfred there are a lot of people using it
17:25 gtmanfred XenophonF: ^^
17:25 stooj joined #salt
17:26 lroe I am trying to create a pillar then apply a state based on that pillar.  I think this includes all of the relevant information: https://gist.github.com/anonymous/fa63c47eeb9f47c13e1c6ece7508acfd
17:27 lroe It looks like the pillar has been applied, but when I run salt 'schnoz*' state.apply test=True, I don't see that the state is going to applied
17:29 onlyanegg joined #salt
17:32 Hybrid joined #salt
17:33 astronouth7303 lroe: what is `logstack/conf.sls`?
17:33 astronouth7303 or is this something weird some formula is doing?
17:33 lroe astronouth7303, I don't follow.  I don't see a logstack/conf.sls
17:34 astronouth7303 s/logstack/logstash/
17:34 astronouth7303 line 4 in that gist is weird, i haven't seen anything like it
17:35 lroe line 4 is my attempt at matching the pillar
17:35 astronouth7303 that's not how that works.
17:35 lroe I figured
17:35 lroe (as it wasn't working)
17:35 lroe see line 14 - 17, that is my pillar
17:36 astronouth7303 https://docs.saltstack.com/en/latest/ref/states/top.html#advanced-minion-targeting
17:37 lroe oh, interesting
17:38 GMAzrael has anyone used pillar data to schedule a state run?
17:39 lroe so it would be something like this?: https://gist.github.com/anonymous/1162917a1a94e9ee62c89f1d19e537b9
17:39 bstevenson joined #salt
17:39 lroe astronouth7303, ^
17:39 astronouth7303 lroe: yes
17:39 lroe I found a hard time finding that documentation for some reason.  Thanks for the help
17:40 astronouth7303 GMAzrael: look at the scheduler https://docs.saltstack.com/en/latest/topics/jobs/#scheduling-jobs
17:40 nixjdm joined #salt
17:44 t3rm is it possible to copy only newer files (recursively) from master -> minion
17:45 ecdhe joined #salt
17:47 redkrieg joined #salt
17:49 redkrieg Hi, I tried searching the chat logs here but didn't find any references to the issue I'm experiencing.  I'm affected by this issue marked "Pending Discussion" in the latest release: https://github.com/saltstack/salt/issues/44050
17:50 Hybrid joined #salt
17:50 dxiri joined #salt
17:50 redkrieg There's a proposed patch from user jalandis in the thread, it is effective and looks more correct to me than the existing code (using pkgname instead of name, which could be None under certain circumstances)
17:51 redkrieg Just wondering what the best way to see about getting a fix in the next salt release would be.
17:51 CampusD t3rm, have you tried with the file.recurse https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.recurse
17:55 astronouth7303 redkrieg: turn it into a pull request and follow https://docs.saltstack.com/en/latest/topics/development/contributing.html
17:55 redkrieg astronouth7303: Thanks for the tip.
17:56 astronouth7303 #salt-dev exists but tbh, it's damn near catatonic
17:57 jab416171 joined #salt
17:57 Trauma joined #salt
17:57 robman joined #salt
17:58 mikecmpbll joined #salt
17:59 jab416171 joined #salt
18:01 astronouth7303 are there any restrictions on the saltenv name?
18:01 DammitJim joined #salt
18:02 DammitJim joined #salt
18:02 t3rm CampusD I have, but it seems to always copy files if the content differs instead of based on timestamp. Am I missing something?
18:03 astronouth7303 t3rm: i assume this is a thing because something unmanaged is overwriting it?
18:04 _JZ_ joined #salt
18:05 redkrieg apparently someone else already fixed it, just hasn't been released yet.  Sorry for the spam: https://github.com/saltstack/salt/commit/0692f442dbaf5a0b16ce696c8947d73ed14965a9
18:07 pipps joined #salt
18:07 astronouth7303 redkrieg: which means it'll be in the next major release (2018.something)?
18:08 redkrieg It's kind of a show-stopper for me and a number of other folks using the sources feature.  It'd be nice to get it in a point release :(
18:09 astronouth7303 you can try backporting it
18:10 astronouth7303 it looks like that was a direct developer commit, didn't go through the PR system?
18:10 astronouth7303 there's tooling around forward-porting PRs
18:11 astronouth7303 so you make a direct PR against the oldest supported branch, and stuff happens to apply it to later versions
18:13 pipps99 joined #salt
18:14 iggy redkrieg: alternatively, throw the patched version of yumpkg in /srv/salt/_modules and the minions will use that version
18:15 redkrieg iggy: thanks, didn't even know that was an option.  I appreciate it.
18:17 iggy yeah, most people don't realize that (even if they know about _modules)
18:17 wongster80 joined #salt
18:18 edrocks joined #salt
18:24 RandyT joined #salt
18:24 RandyT joined #salt
18:26 SkyRocknRoll_ joined #salt
18:29 pipps joined #salt
18:39 noobiedubie joined #salt
18:45 kellyp joined #salt
18:49 SlicerDicer joined #salt
18:49 SlicerDicer joined #salt
18:53 lordcirth_work I wish I had more time to do salt pull requests
19:07 felskrone joined #salt
19:15 relidy joined #salt
19:16 heaje joined #salt
19:38 SamYaple redkrieg: just be careful doing that for licensing reasons. you should normally be fine, but somethingto keep in mind
19:43 redkrieg what licensing implications does copying a salt module from master to minion among my own assets have?  it's apache licensed, are you saying I need to include the contents of the LICENSE file from the repo in any module I copy from salt to /srv/salt/_modules/?
19:45 redkrieg joined #salt
19:46 ChubYann joined #salt
19:54 yuhl joined #salt
19:59 usernkey joined #salt
20:02 toanju joined #salt
20:03 aldevar joined #salt
20:10 klaas joined #salt
20:11 ThomasJ|d joined #salt
20:16 nledez joined #salt
20:17 jas02 joined #salt
20:19 N-Mi joined #salt
20:19 N-Mi joined #salt
20:21 choke joined #salt
20:22 jas02 joined #salt
20:24 _KaszpiR_ joined #salt
20:29 jas02 joined #salt
20:33 jas02_ joined #salt
20:33 aviau joined #salt
20:36 pipps99 joined #salt
20:37 usernkey1 joined #salt
20:43 SkyRocknRoll joined #salt
20:59 jhauser_ joined #salt
21:00 pipps joined #salt
21:01 kellyp joined #salt
21:02 pipps99 joined #salt
21:02 kellyp joined #salt
21:03 yuhl joined #salt
21:04 dxiri joined #salt
21:05 CampusD so question, what is the difference between /var/cache/salt/minion/jobs/ and /var/cache/salt/minion/minion_jobs/ ?
21:12 onlyanegg joined #salt
21:15 dxiri joined #salt
21:16 dxiri joined #salt
21:25 aldevar joined #salt
21:31 GMAzrael joined #salt
21:40 fleaz joined #salt
21:41 pipps joined #salt
21:42 laertus has anyone ever tried to get salt working under pypy or cython?
21:46 xet7 joined #salt
21:50 sh123124213 joined #salt
21:54 pjs_ left #salt
21:55 pjs joined #salt
21:56 aldevar left #salt
21:56 dxiri joined #salt
21:59 Processus42 joined #salt
22:06 tom[] running the orchestrator, i got the error "An un-handled exception was caught by salt's global exception handler. UnicodeDecodeError: 'ascii' codec can't decode byte..." with traceback https://gist.github.com/spinitron/ccff209c754b46592218c6cec566615e
22:06 tom[] any suggestions how to debug?
22:07 tom[] i've no idea where in the orch sls this happened
22:09 tom[] i think the error was after the orch sls completed and salt-run was trying to display output
22:09 tom[] would that make it a bug?
22:10 tom[] a bug in salt, i mean
22:12 myii joined #salt
22:13 darix joined #salt
22:13 dxiri joined #salt
22:13 pipps joined #salt
22:16 major joined #salt
22:19 SkyRocknRoll_ joined #salt
22:20 dRiN joined #salt
22:20 theham @tom[] iirc i have seen the when people using cmd.run or cmd.script were sending bad output. might want to go back to the job and see what the output was
22:29 dxiri joined #salt
22:29 dxiri joined #salt
22:35 user-and-abuser joined #salt
22:42 bstevenson joined #salt
22:42 redkrieg left #salt
22:45 laertus i've just installed a salt master and minion on a test openbsd VM running in virtualbox on my laptop
22:45 laertus here's a summary of my configuration:  https://paste.pound-python.org/show/iAm2jk3IuVLc0ZgxMdEl/
22:45 laertus i've started the master and minion, and accepted the minion's key
22:46 laertus i want to use salt to install vim as a test
22:46 SkyRocknRoll_ joined #salt
22:46 laertus with the above config i tried:  salt '*' state.highstate
22:47 laertus but got an error:  https://paste.pound-python.org/show/JeSB9trsQeD0v7KhFl3O/
22:47 laertus "The following packages failed to install/update: vim"
22:47 laertus no details about why, though
22:47 cgiroua joined #salt
22:47 laertus i can do a test.ping fine and disk.usage also worked... so there seems to be successful communicaiton b/w master and minion
22:48 babilen Run the minion in debug mode and then "salt-call -ldebug pkg.install vim" -- I guess something did go wrong during the package installation
22:49 babilen (on the minion)
22:50 laertus ok, i'll try... thanks
22:52 bstevens_ joined #salt
23:06 bstevenson joined #salt
23:08 laertus here's the output of running "salt-minion -l debug"  https://paste.pound-python.org/show/7hoCH4bxdKjATA0g4sDH/
23:08 laertus i put a few blank lines in the bottom of that output, right before i ran the salt-call to install vim
23:08 laertus and here's the output of running "salt-call -ldebug pkg.install vim"   https://paste.pound-python.org/show/gD6QEp4qBPFyEHPPLNYS/
23:09 laertus nothing really jumps out at me to explain why salt isn't installing vim
23:09 tom[] theham: the sphinx indexer outputs a few warning messages with non ascii characters. but what can i do about that?
23:11 bstevenson joined #salt
23:12 laertus actually, i do see this:  Executing command 'pkg_add -x -I vim--%' in directory '/root'
23:12 laertus that 'pkg_add -x -I vim--%' looks a bit weird
23:13 laertus why is it "vim--%" and not just "vim"?
23:13 Processus42 joined #salt
23:15 CampusD @laertus , is vim a valid package for openbsd?
23:15 laertus yep
23:16 SkyRocknRoll__ joined #salt
23:17 laertus actually.. maybe not... i thought it was.. but actually "pkg_add vim" shows:  https://paste.pound-python.org/show/O8s2M6IHOVsK3JK4JKra/
23:17 CampusD so from the CLI "pkg_add vim" works?
23:17 CampusD I was going to ask that :)
23:17 laertus good call
23:18 laertus let me try changing my state to install vim-8.0.0987p0-no_x11
23:18 CampusD also found this https://rodolfo.io/2015/02/how-to-install-vim-on-openbsd/
23:18 CampusD looks like they loaded a custom repo perhaps to install it
23:19 CampusD or rather there might be multiple options
23:19 laertus this fresh openbsd install has it under the default repo
23:19 CampusD I see
23:22 laertus hmm... so i changed my vim state file to install vim-8.0.0987p0-no_x11 instead
23:23 laertus but now when i run "salt '*' state.highstate" i'm getting an error:  "myhost:  Minion did not return. [No response]"
23:23 laertus it responds to test.ping though
23:23 LordOfLA joined #salt
23:23 laertus i'm going to try running this under debug again...
23:25 CampusD anything if you pass -l debug or -l all ?
23:29 laertus the output is pretty much the same as before, only now instead of "Executing command 'pkg_add -x -I vim--%' in directory '/root'" it's doing "Executing command 'pkg_add -x -I vim-8.0.0987p0-no_x11--%' in directory '/root'"
23:30 laertus and then tells me "Command 'pkg_add -x -I vim-8.0.0987p0-no_x11--%' failed with return code: 1" and "Can't find vim-8.0.0987p0-no_x11--%"
23:30 laertus i don't understand why it's appending that "--%" to the package name
23:31 myii joined #salt
23:32 laertus looks like in salt's openbsdpkg.py it has:  "pkg = '{0}--{1}%{2}'.format(base, flavor, branch)"
23:32 laertus so that must be where the --% is coming from
23:34 CampusD yeah, not sure, what if you try altering the structure of your state yaml? There are a few ways to use the pkg.installed function, https://docs.saltstack.com/en/latest/ref/states/all/salt.states.pkg.html#salt.states.pkg.installed
23:35 laertus in that openbsdpkg.py i also see:  "__PKG_RE = re.compile('^((?:[^-]+|-(?![0-9]))+)-([0-9][^-]*)(?:-(.*))?$')"
23:35 laertus with a comment above it saying:  "FIXME: replace guesswork with `pkg_info -z` to correctly identify package flavors and branches"
23:36 CampusD a bug perhaps, could be listed on https://github.com/saltstack/salt/issues
23:36 laertus if i do a "pkg_info -z vim" i see one of the choices is "vim--no_x11"
23:37 laertus maybe that's what it's looking for instaed of "vim-8.0.0987p0-no_x11"
23:37 laertus i'm going to try it..
23:39 laertus yay!
23:39 laertus it worked!
23:39 pipps joined #salt
23:40 c4rc4s joined #salt
23:40 myii joined #salt
23:41 laertus yeah, that regex is pretty fragile, and there's no sanity in the openbsdpkg.py code at all regarding what it thinks the package name is/should-be
23:42 GMAzrael joined #salt
23:43 pipps joined #salt
23:50 justanotheruser joined #salt
23:50 justanotheruser joined #salt
23:52 bluemalkin joined #salt
23:55 Processus42 joined #salt
23:59 mikecmpbll joined #salt

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