Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-07-19

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

All times shown according to UTC.

Time Nick Message
00:00 major 2017.7.0
00:00 major and 2016.11
00:00 Edgan I have used 2016.11 before
00:00 Edgan Try setting it up exactly how I showed and see what it does
00:00 Edgan What OS?
00:00 major Linux
00:00 Edgan Distro?
00:01 major Ubuntu
00:01 Edgan I used salt-ssh on 14.04 and 16.04 without issue
00:01 major wondering if it is the lack of a .pub
00:01 Edgan You mean you say ssh_priv: /home/user/ida_rsa.pub?
00:01 major no
00:02 Edgan or you mean no .pub in .ssh?
00:02 major I mean there is no id_rsa.pub file along side the id_rsa file
00:02 Edgan Maybe
00:02 major would be kinda weird for the client to care if it isn't trying to deploy the .pub
00:03 Edgan Looking at the code, looks like it does look for .pub
00:03 * major sighs.
00:03 major that feels like it should be flagged as a bug
00:03 Edgan major: make a pull request :)
00:03 major bleh...
00:03 Edgan major: it probably will be easy
00:04 major people gonna make me fork bootstrap-salt.sh and salt-ssh now
00:04 Edgan major: I don't even use bootstrap-salt.sh. I just bake the salt-minion into the AMI.
00:04 major I don't use it either, only because it doesn't have a --update-repo-only option
00:05 major if it did then I would use it ;)
00:05 Edgan major: File a bug and I might fix it one day if it makes sense after reading the code to see why it might want .pub
00:05 major would tell my developers to wget it and run it w/ that option so I wouldn't have to walk them through updating their own repos for all their damn OS's
00:06 Edgan major: To side step things like OSX, salt in vagrant. Though I will admit, if people get picky it can get out of hand.
00:06 major I will likely just fork it and tell it to only test for the .pub if the --key-deploy is true
00:06 major else it doesn't make any sense to look for the .pub
00:06 major or none that I can currently think of
00:11 Edgan major: heading home
00:12 major Edgan, stay safe
00:13 major was just thinking .. one of the things I like about using ~/.salt/Saltfile is that I can be anywhere in the tree and use salt-ssh .. don't have to be in a specific directory... but thats just me
00:13 major also .. users can point leep their own random roster file for their random VM's and whatnot in ~/.salt/roster
00:13 major or wherever they want to stuff it
00:23 woodtablet left #salt
00:31 kerrick_ joined #salt
00:31 KevinAn2757 joined #salt
00:34 noraatepernos joined #salt
01:06 lorengordon joined #salt
01:12 major well .. I generated an id_rsa w/ id_rsa.pub and it is still trying to overwrite them every time I run salt-ssh ..
01:12 major wonder what it is missing
01:13 rpburkholder joined #salt
01:14 rpb joined #salt
01:23 ssplatt joined #salt
01:48 ilbot3 joined #salt
01:48 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.11.6, 2017.7.0 <+> 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 <+> The call for speakers for SaltConf17 is now open: http://tinyurl.com/SaltConf17
01:57 cyborg-one joined #salt
02:04 deuscapturus joined #salt
02:06 zerocoolback joined #salt
02:09 elektrix joined #salt
02:11 edrocks joined #salt
02:15 onlyanegg joined #salt
02:21 simmel joined #salt
02:31 onlyanegg joined #salt
02:38 karlthane joined #salt
02:45 evle joined #salt
02:57 sturlik joined #salt
03:01 kerrick_ joined #salt
03:04 kerrick_ joined #salt
03:12 edrocks joined #salt
03:27 beardedeagle joined #salt
03:29 beardedeagle Pretty sure there isn't, but thought I'd ask for a coworker anyway. Is there a way to randomly select a single minion from a glob or node list and run a command against it.
03:29 v3x i wish someone would slap together a gui for salt and release it
03:29 v3x without paying $1500 per instance for enterprise
03:29 beardedeagle v3x: there are a couple
03:30 beardedeagle the most prominent being https://github.com/Lothiraldan/saltpad
03:30 v3x last time i checked all there was was that Halite thing that was impossible to get working and more or less useless even if you managed
03:31 beardedeagle halite is depricated and no longer maintained
03:31 v3x last commit was a year ago .. not sure if i want to get into an abandoned project
03:31 beardedeagle https://github.com/martinhoefling/molten
03:31 MTecknology I remember halite... it was a cool concept for other things to spawn from
03:31 beardedeagle only other one I track
03:32 beardedeagle another old one https://github.com/yueyongyue/saltshaker
03:32 beardedeagle older*
03:32 beardedeagle or, v3x, alternatively you can use foreman with the saltstack plugin
03:32 beardedeagle there are plenty of options floating around out there
03:33 v3x i tried foreman but its functionality is way too limited.
03:33 v3x my real problem is our deployment is enormous and includes an in-house sql database to keep track of changes over time
03:34 v3x what i'm really asking for is someone to do all the annoying parts of my job for me so i can just play solitaire
03:36 beardedeagle I guess I don't see the value in a ui beyound reporting and metrics
03:37 v3x neither do it, but ... users
03:38 v3x because of what we use salt for, we have to have a bit more hands-on interaction with the minions than what's normal
03:38 v3x and i've got a call center full of support people who are scared of command lines
03:41 MTecknology reporting and metrics would convince me to use a UI for salt, but not to push commands, only to review.
03:41 donmichelangelo joined #salt
03:42 mosen haha i started writing one but figured theres already too many options
03:42 MTecknology actually, that seems like a stupidly easy task to write up by hand. A web app just needs read-only access to list completed jobs stored in a db.
03:42 mosen since it's all tornado based i figured something with realtime websocket feedback would be nice
03:43 MTecknology what's tornado based?
03:44 MTecknology If I build something, I'll have job history logged into a sqlite3 db and then I'd use bottle.py to write the front end.
03:44 beardedeagle yeah I wrote a "pepper on crack" application and abstracted out the saltapi client. If I have time I will also write a ui.
03:44 beardedeagle but time is pretty...sparse at the moment
03:45 MTecknology I'm cooking a beef brisket at the moment.
03:45 mosen MTecknology all the existing stuff around netapi
03:45 MTecknology smoking*
03:46 beardedeagle most ui implementations/attemps are still cherrypy based
03:46 beardedeagle saltpad is tornado based though I think
03:46 mosen it helps having job results delivered asynchronously via ws
03:47 mosen anyway cli is fine :)
03:49 beardedeagle reporting can easily be accomplished via returners...and a little custom code
03:49 beardedeagle which is kinda how enterprise does it anyway
03:50 MTecknology kinda ~= exactly
03:51 MTecknology and if that's the only thing you find exciting about enterprise, then... :P
03:51 MTecknology granted, enterprise != support; support is absurd.. cheap and effective
03:51 MTecknology I don't know anything about enterprise beyond the manuals
04:00 MTecknology beardedeagle: have you worked with enterprise?
04:01 beardedeagle Nope, just know a bit about it
04:01 stduolc joined #salt
04:02 onlyanegg joined #salt
04:05 rwaweber joined #salt
04:07 rwaweber joined #salt
04:21 sturlik joined #salt
04:22 asoc joined #salt
04:28 Ni3mm4nd joined #salt
04:30 coredumb beardedeagle: hey this molten UI looks simple enough for job reporting
04:30 gmoro joined #salt
04:37 vishvendra joined #salt
04:45 beardedeagle coredumb: yeah it's pretty basic, but useful
04:46 mbuf joined #salt
05:08 Bock joined #salt
05:08 sturlik joined #salt
05:14 edrocks joined #salt
05:37 coredumb beardedeagle: have to check how to deploy that :)
05:37 coredumb does it need a database returner or not even?
05:45 armyriad joined #salt
05:45 beardedeagle coredumb: no, pretty sure state is maintained internally to the spa
05:47 coredumb cool
05:47 beardedeagle the guy provides a salt formula for installing it
05:47 beardedeagle actually
05:48 beardedeagle https://github.com/martinhoefling/molten-formula
05:50 xet7 joined #salt
05:56 armyriad joined #salt
05:56 coredumb beardedeagle: will have to try that ^^
06:07 karlthane joined #salt
06:13 aldevar joined #salt
06:17 impi joined #salt
06:23 MTecknology that's one of the few salt formulas that doesn't make me angry to look at
06:25 kows joined #salt
06:30 sh123124213 joined #salt
06:34 gnomethrower joined #salt
06:44 armguy joined #salt
06:45 do3meli joined #salt
06:45 do3meli left #salt
06:45 gmoro joined #salt
06:45 do3meli joined #salt
06:45 do3meli left #salt
06:47 do3meli joined #salt
06:49 do3meli joined #salt
06:49 do3meli left #salt
06:53 xet7_ joined #salt
07:11 _KaszpiR_ joined #salt
07:20 seffyroff joined #salt
07:24 seffyroff joined #salt
07:28 vishvendra joined #salt
07:31 zulutango joined #salt
07:34 vishvendra1 joined #salt
07:41 kyuuri joined #salt
07:44 kyur joined #salt
07:44 pfallenop joined #salt
07:45 vishvendra1 joined #salt
07:46 kyur Hey I have a question regarding the design of a salt project I am working on.
07:48 kyur I wrote an execution module that collects information about the installed packages on the minions. Then I wrote a returner, that would return that data to an external database (running on the salt-master node).
07:48 kyur Lastly I wrote a runner so that the salt-master can query the database and return a certain list of packages with faulty version.
07:49 kyur Is that an okay-way to write this system (using a module, a returner AND a runner) or is there a more elegant, "salty" way of doing this?
07:50 coredumb kyur: I guess it depends what you need is in the end ?
07:51 Rumbles joined #salt
07:51 coredumb is it to just return the package list? you plan is to get this list when running a salt-run command?
07:52 xet7 joined #salt
07:53 Ricardo1000 joined #salt
07:54 kyur Basically yes, it should return a list of packages for each salt-minion, with only those packages that have a wrong version (wrong version means, that the majority of minions, that also have that package installed have it installed with a different version)
07:58 karlthane joined #salt
07:59 impi joined #salt
08:03 pfalleno1 joined #salt
08:04 preludedrew joined #salt
08:04 Ni3mm4nd joined #salt
08:09 mikecmpbll joined #salt
08:11 Hybrid joined #salt
08:12 EthPyth joined #salt
08:12 pbandark joined #salt
08:16 edrocks joined #salt
08:25 Mattch joined #salt
08:25 hojgaard joined #salt
08:27 vishvendra1 joined #salt
08:28 N-Mi_ joined #salt
08:31 Rumbles joined #salt
09:01 c06 joined #salt
09:01 c06 hi all
09:03 vishvendra joined #salt
09:04 kjsaihs joined #salt
09:09 vishvendra1 joined #salt
09:18 Naresh joined #salt
09:43 kyur Is there a way to access a module inside _utils from a runner? In my returner I could simply import the module and it worked. How can one do that with runners?
09:47 netcho joined #salt
09:48 netcho hi all
09:49 seb_ joined #salt
09:51 netcho having this error on one of the minions
09:51 netcho https://hastebin.com/hixotufimu.sql
09:51 netcho salt-minion 2017.7.0 (Nitrogen) ... salt-master 2016.3.4 (Boron)
09:53 netcho highstate runs on other minions
09:56 gmoro joined #salt
10:14 om2 joined #salt
10:15 netcho Salt's policy has always been that when upgrading, the minion should never be on a newer version than the master. Specifically with this update, because of changes in the fileclient, the 2017.7 minion requires a 2017.7 master.
10:15 netcho makes sense
10:18 edrocks joined #salt
10:25 Miouge joined #salt
10:31 cyteen joined #salt
10:33 smartalek joined #salt
11:23 vishvendra joined #salt
11:23 zer0def um… anyone able to provide me with quick pointers on how i'd approach using django_returner?
11:25 zer0def preferrably with applications that run within a virtualenv
11:26 gmoro joined #salt
11:27 evle1 joined #salt
11:27 rburkholder joined #salt
11:28 gmoro_ joined #salt
11:30 dendazen joined #salt
11:32 gmoro_ joined #salt
11:32 astronouth7303 zer0def: you can't have the app in a venv, then. The minion and the app have to be in the same Python environment.
11:33 zer0def astronouth7303: doesn't django signal usage imply they're within the same process?
11:34 zer0def i could technically toggle global site-packages to use the same salt, but i'm curious as to how the signal itself would be propagated between processes
11:35 astronouth7303 It wouldn't
11:35 zerocoolback joined #salt
11:36 zerocoolback joined #salt
11:36 zer0def so in essence i'm expected to run django in the same process as salt-call
11:36 astronouth7303 Salt loads your code and runs it, but it doesn't start your server
11:38 gmoro_ joined #salt
11:38 zer0def astronouth7303: in that case where do i run the receiver that interacts with the project proper?
11:39 astronouth7303 I would recommend writing your own webhook returner. (... Why doesn't it have one?)
11:39 astronouth7303 Sperate instances
11:40 astronouth7303 The minion loads a copy of your code just for the one signal
11:40 zer0def that much i would've figured, just was curious as to whether django_returner was actually usable code without whacking away at it
11:40 astronouth7303 Like running a celery job
11:41 zer0def yeah, that much i would've figured
11:41 astronouth7303 The problem is installation, since I think you pretty much have to install your app globally.
11:42 zer0def passing a message around is a lot more convenient, so i'll stick with that
11:43 astronouth7303 Much easier to reason about and doesn't require restarting the minion on deploy.
11:44 zer0def i'm actually surprised this uses signals instead of using similar logic to django_orm ext_pillar
11:50 astronouth7303 It's better, but still need to restart on deploy
11:52 zer0def yes, it would, but i think it would provide enough flexibility to be worthwhile
11:58 astronouth7303 I'd rather decouple. Write out a file for salt to grab or use the cmd pillars or do some custom network stuff.
12:01 zerocool_ joined #salt
12:09 hoonetorg joined #salt
12:09 XenophonF joined #salt
12:12 gmoro joined #salt
12:16 bluenemo joined #salt
12:18 numkem joined #salt
12:19 cablekev1n joined #salt
12:20 mbuf in an example from the "Mastering Salt" book, when watching for file changes using beacon, the SMTP setting is done on the minion, beacon is set to watch the same, the event is sent to the salt-master reactor, and then notified back to the minion to send e-mail
12:20 mbuf why can't we send e-mail straight away from the minion, instead of having to go to the master?
12:21 mbuf or, it is just so that this example has it like that? the master can take any other action if required
12:22 Diaoul joined #salt
12:22 coredumb mbuf: I don't know about this book, but I guess that's to illustrate the use of reactor on the server?
12:25 jansen4 joined #salt
12:25 jansen4 Hello, How do people deploy salt on windows computers in an active directory domain?
12:25 mbuf coredumb, the section was on using beacons
12:26 coredumb mbuf: the point of a beacon is to send an event to the server to "notify of a change"
12:26 coredumb be it file change, load avg change, etc
12:26 mbuf coredumb, I see
12:26 mbuf coredumb, so it just so happens that they use the minion to send e-mails
12:27 coredumb I think this an example
12:27 mbuf coredumb, yes
12:27 coredumb another thing could be
12:27 coredumb you have a file inotify beacon
12:27 coredumb watching over a managed file
12:27 mbuf coredumb, yes
12:27 coredumb on modification, you send the event
12:28 coredumb server reacts on it by telling the minion to apply the state that manages the file
12:28 mbuf coredumb, got it; the book is nice BTW
12:28 coredumb you get it repaired instantly
12:29 coredumb this event system is so neat that it makes me gigle everytime I think about what I can do with it
12:29 coredumb :D
12:30 Deliant joined #salt
12:30 mbuf coredumb, salt is very powerful, and I am glad I am learning it
12:31 coredumb yep
12:32 mbuf coredumb, thanks for your time
12:32 mbuf coredumb, later
12:43 ssplatt joined #salt
12:43 ecdhe joined #salt
12:45 ProT-0-TypE joined #salt
12:48 jansen4 Hello, How do people deploy salt on windows computers in an active directory domain?
13:02 jdipierro joined #salt
13:05 edrocks joined #salt
13:16 cgiroua joined #salt
13:22 jansen4 With the MSI installer, how do I set the minion id to pc1.domain.local? The MINION_HOSTNAME variable seems to always default to pc1
13:30 lorengordon joined #salt
13:30 dimeshake hmm... salt 2017.7.0 on cent 6.9 doesn't see libgit2 or pygit2 and complains no gitfs module available :|
13:34 jansen4 It seems that the MINION_HOSTNAME value is just ignored
13:42 jmedinar joined #salt
13:43 dimeshake jansen4: there's a switch for the msi installers IIRC
13:43 dimeshake unless i misunderstand your q
13:43 dimeshake https://docs.saltstack.com/en/latest/topics/installation/windows.html#silent-installer-options
13:45 jansen4 dimeshake: those seem to be for the .exe installer
13:45 jansen4 https://github.com/saltstack/salt-windows-msi
13:45 jansen4 The MSI installer has a few Properties but they dont seem to work
13:47 dimeshake ah. i knew it wasn't that simple :)
13:47 jansen4 I never worked with MSI installers this way, but following their readme this should work
14:01 bildz joined #salt
14:12 ivanjaros joined #salt
14:13 thinkt4nk joined #salt
14:14 cwright joined #salt
14:15 lompik joined #salt
14:22 EvaSDK joined #salt
14:25 _JZ_ joined #salt
14:31 Inveracity joined #salt
14:42 sarcasticadmin joined #salt
14:49 jmedinar Hello... I am getting the following error in a particular minion any idea why? [ https://pastebin.com/UNy3bEGe ]
14:51 dimeshake jmedinar: check the saltmaster log as it says. there is likely a syntax error in the pillar
14:51 jmedinar but even if I blank the pillar keeps sending the error
14:51 jmedinar and I already checked the log but doesn't provide any details
14:52 astronouth7303 try https://docs.saltstack.com/en/latest/topics/troubleshooting/#running-in-the-foreground for more information
14:54 astronouth7303 pillar data is evaluated on the master, so the master will likely have the most detailed information. Any information provided by the minion is just forwarded.
15:00 jmedinar here is the output of the master log [ https://pastebin.com/E7i2DDTe ]
15:00 om2 joined #salt
15:03 astronouth7303 ... what's your pillar topfile?
15:05 rebbdohr joined #salt
15:10 astronouth7303 jmedinar: don't PM.
15:11 rebbdohr joined #salt
15:13 unzunz joined #salt
15:20 jmedinar here is the top.sls [ https://pastebin.com/X2kLaiNV ]
15:21 do3meli joined #salt
15:21 unzunz hi I'm looking for some assistance with salt, a minion I had deployed with salt-cloud was doing just fine, then suddenly it just started throwing compile errors, I don't even know what changed to cause it. I have tried destroying and redeploying it over and over, and I still can't run a salt.highstate
15:21 do3meli left #salt
15:21 vishvendra joined #salt
15:21 unzunz I can on the other vms I deployed, those seem fine, but it seems this particular host just doesn't want to run a highstate or any state with out throwing the errors
15:21 dimeshake unzunz: what kind of errors
15:23 astronouth7303 jmedinar: did you create a `_uat_csa....._blc_.sls` file?
15:24 jdipierro joined #salt
15:24 unzunz https://gist.github.com/anonymous/b06706714668b683836806ac53f3ad28
15:27 unzunz it's also throwing these errors in the master log
15:27 unzunz [ERROR   ][20035] Received function _file_hash_and_stat which is unavailable on the master, returning False
15:27 donmichelangelo joined #salt
15:27 unzunz but if I run a salt highstate or any other state on any of the other servers I built, there's no issues
15:28 unzunz They are all centos 7, and basically identical configurations in the cloud.maps file
15:28 unzunz and this host did work up until it randomly just stopped working
15:30 jmedinar yes I do have the file created
15:30 jmedinar -rw-r--r--. 1 root root 1388 Jul 19 09:40 _uat_csa_cloudant_wa1_gz_blc_.sls
15:30 astronouth7303 jmedinar: valid YAML? Jinja syntax errors?
15:31 jmedinar well... it is failing on states with and without jinja
15:34 ivanjaros joined #salt
15:35 rebbdohr_ joined #salt
15:35 woodtablet joined #salt
15:43 jmedinar will try re-doing the file
15:43 darioleidi joined #salt
15:45 Guest73 joined #salt
15:45 fritz09 joined #salt
15:49 toastedpenguin joined #salt
15:52 mavhq joined #salt
15:52 mikecmpb_ joined #salt
15:57 ecdhe Anyone have salt working on a ubiquiti edgerouter?
15:58 onlyanegg joined #salt
16:04 onlyaneg1 joined #salt
16:06 ecdhe I have some 3 and 8 port edgerouters that I'd like to manage with salt.  They run debian 7 on a MIPS core.
16:07 ecdhe saltstack seems to have deprecated the packages for this platform, so I went for salt-ssh.
16:07 ecdhe A few minutes into my first test, I encountered this issue from 2015: https://github.com/saltstack/salt/issues/27355
16:07 ecdhe Not only did I have the same error, but there was a patch!
16:08 ecdhe However this patch was rejected.
16:08 ecdhe I tried to apply the patch to my exisiting salt installation, but i didn't succeed in getting salt-ssh to work.
16:12 GMAzrael_ joined #salt
16:14 MTecknology I really hope you're not running debian 7 on your edge routers... that's old-old-stable
16:17 Ambassador joined #salt
16:17 unzunz joined #salt
16:18 leonkatz joined #salt
16:18 Ambassador left #salt
16:18 secrgb joined #salt
16:19 unzunz does anyone have any ideas on the errors i pasted
16:20 astronouth7303 ubiquiti is more commercial black box than ops-managed hardware
16:21 MTecknology I use their unifi stuff, but it talks on a management vlan, not to the internet.
16:21 ecdhe MTecknology: it might be debian 8, like astronouth7303 said its a black box.
16:21 ecdhe It's excellently flexible/powerful kit for the money.
16:21 MTecknology You typically don't want to manage black box stuff with salt
16:22 astronouth7303 or, you manage it through the blessed API from a normal minion
16:22 astronouth7303 ie, write ubiquiti execution and state modules
16:22 ecdhe okay, so the api is that it's a linux system.
16:23 ecdhe apt-get install tayga
16:23 ecdhe file.managed -name /config/mydata
16:23 ecdhe etc etc
16:23 GMAzrael joined #salt
16:23 ecdhe I can type all this stuff by hand, but that's the stone age.
16:23 MTecknology unzunz: The actual error is "TypeError: 'bool' object is not iterable"  Run with the debug log level if you want to see more.
16:24 astronouth7303 ecdhe: not through UniFi?
16:24 astronouth7303 i didn't realize the official way to manage ubiquiti was with ssh
16:24 MTecknology heh.. I've been using their web ui
16:24 ecdhe astronouth7303: there is a UniFi product like that is 100% managed by the controller.
16:25 evle3 joined #salt
16:25 gmoro joined #salt
16:25 ecdhe *product line
16:25 ecdhe But the edgeos gear is different, and cannot be adopted by that system.
16:26 ecdhe The Edgerouters are more of a standalone PC.  You can even run OpenBSD on them, there's a Octeon build that's self-hosted!
16:26 astronouth7303 if you were to manage other linux-based routers with salt, how would that work?
16:27 ecdhe astronouth7303: I actually already do this; I use masterless salt.
16:27 astronouth7303 i think the only hard requirement for running a salt minion is a modern python?
16:27 MTecknology 2.7+
16:28 vishvendra joined #salt
16:28 ecdhe While you might use salt-cloud to provision tons of temporary minions, your routers are more core to the network -- they're much less ephemeral, so masterless salt gets me reproducible configs without adding another running service.
16:28 unzunz MTecknology: I did but it does not reveal anymore :(
16:29 MTecknology unzunz: you're trying to loop over something that is not iterable
16:29 astronouth7303 so you have to compile py2.7 for mips and load it and a base python environment
16:29 astronouth7303 run salt from source?
16:30 astronouth7303 (am I missing something?)
16:30 ecdhe astronouth7303: python is already there.  But the installer fails.
16:30 ecdhe The salt installer
16:30 ecdhe salt_bootstrap sees the MIPS arch and tries to fetch a mips package from repo.saltstack.com
16:31 ecdhe There USED to be one, but saltstack doesn't package it any more.
16:31 astronouth7303 send over a source tarball and build a package yourself?
16:31 aldevar left #salt
16:32 ecdhe I'll have to give it a try.
16:32 ecdhe I would be totally fine with salt-ssh too
16:33 astronouth7303 or just run it from source; it doesn't look like salt itself has any compiled extensions
16:34 jdipierro joined #salt
16:36 censorshipwreck joined #salt
16:37 major okay .. salt-ssh insanity
16:37 major or python insanity..
16:39 major if not os.path.isfile(priv): salt.client.ssh.shell.gen_key(priv) .. gen_key() is getting called, but priv exists, and is a file..
16:39 major I am seriously pondering calling an exorcist...
16:39 astronouth7303 that's when i pull out pdb or start spraying print()
16:40 debian112 joined #salt
16:42 major yah .. I fired up python in interactive mode and ran the same code manually .. and the isfile() test confirms that the file exists
16:43 major might need to clobber some pyc files
16:43 astronouth7303 wouldn't hurt
16:43 astronouth7303 `find -iname "*.pyc" -delete` can do amazing things
16:43 ecdhe install_salt.sh says "* ERROR: repo.saltstack.com doesn't have packages for your system architecture: mips"
16:44 major not suprising
16:44 GMAzrael joined #salt
16:44 astronouth7303 ecdhe: i think we discussed this already?
16:45 MTecknology pudb is probably the sexiest debugging tool I've ever seen.
16:45 ecdhe astronouth7303: just trying it again.  Going to try for a git install now.
16:46 astronouth7303 what you probably want is `pip install /path/to/git/salt`
16:46 major ++
16:48 vishvendra1 joined #salt
16:49 astronouth7303 you just have to make sure they have python2.7 first (which is a toss-up, given the age of the base distribution)
16:49 ecdhe Python 2.7.3
16:50 impi joined #salt
16:51 scarcry joined #salt
17:01 ecdhe Resolveing deltas on the git repo, it's slow going on this 500MHz MIPS core.
17:01 ecdhe Also, I'm installing check_install so I don't have to do this again.
17:01 astronouth7303 could clone locally and rsync it over?
17:02 ecdhe That's a thought.  I hope I never have to use rsync again.
17:03 astronouth7303 it's a useful tool. Beats scp'ing a tarball?
17:04 ecdhe I've been burned by data loss when copying large samba shares.  All directories would copy, but no files... but point it at just a subfolder and it works.  Odd behaviour on Cent7.
17:05 ecdhe Nevermind the rsync in cygwin that can't support filenames over a certain length (255 bytes?)
17:05 astronouth7303 whatever works for you
17:05 ecdhe haha
17:05 astronouth7303 that's a windows thing, MAX_PATH is 260
17:06 astronouth7303 https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx discusses it (actually kinda complicated...)
17:06 twooster Is there a shell-escape filter? I want to use cmd.run, and do so with properly escaped strings
17:06 twooster see no mention in the doc'm about this
17:10 leonkatz joined #salt
17:13 kerrick_ joined #salt
17:15 wendall911 joined #salt
17:16 vishvendra joined #salt
17:18 mikecmpbll joined #salt
17:21 vishvendra1 joined #salt
17:22 riftman joined #salt
17:23 major nuking the pyc files didn't fix it..
17:32 donmichelangelo joined #salt
17:42 deep-book-gk_ joined #salt
17:43 _KaszpiR_ joined #salt
17:43 deep-book-gk_ left #salt
17:47 leonkatz joined #salt
17:52 Edgan joined #salt
17:58 edrocks joined #salt
17:59 major okay .. I found it
17:59 major and I guess I need to submit a patch
17:59 major totally a bug in salt-ssh
18:01 leonkatz joined #salt
18:02 major Edgan, os.path.isfile(os.path.expanduser(priv))
18:02 major :(
18:02 major salt-ssh has stacks of places where '~' isn't being expanded
18:04 leonkatz joined #salt
18:09 smartalek Anyone have experience with environments? I have several environments in file_roots and sometimes when I issue salt commands like saltutil.sync_all, I'm getting errors unless I specify saltenv=…
18:09 smartalek Ideas on where to start looking?
18:13 noraatepernos joined #salt
18:14 netcho i upgraded to 2017.7 today and salt-cloud gives me `[WARNING ] There's no master defined on the 'qa-rabbitmq-testing-lebo' VM settings.`
18:15 major is salt-ssh part of the general salt repo?
18:16 major think I just answered my own question
18:16 u_nuSLASHkm8 joined #salt
18:16 netcho did something changed?
18:17 u_nuSLASHkm8 left #salt
18:19 netcho this is my provider https://hastebin.com/litemocesu.php
18:19 netcho it worked on 2016
18:19 schemanic joined #salt
18:22 tobiasBora joined #salt
18:23 druonysus joined #salt
18:23 druonysus joined #salt
18:23 major soooo ... how soon till 2017.7.1? ;)
18:23 major or is it too late for that?
18:25 druonysus_ joined #salt
18:25 * whytewolf twiddles his thumbs and mentions that an rc2 would have been nice. and more people testing the rc1
18:25 major is there a doc for the magic process for submitting PRs?
18:25 major like, do I open a bug first and submit a PR against the bug or which?
18:27 netcho anyone?
18:27 whytewolf https://docs.saltstack.com/en/latest/topics/development/contributing.html
18:27 whytewolf https://docs.saltstack.com/en/develop/topics/development/pull_requests.html
18:27 whytewolf https://docs.saltstack.com/en/latest/topics/development/tutorial.html
18:27 major :P
18:27 major mostly just curious about the second link :)
18:27 major thanks though
18:27 netcho i don't see anything in changelog for cloud provider config
18:27 netcho or am i blind
18:29 netcho only thing related `Support for using the keyword provider in salt-cloud provider config files has been removed. Please use driver instead. The provider keyword should now only be used in cloud profile config files.`
18:31 major whytewolf, that PR page is ... insane
18:32 major and .. never mind .. it was the 1st link that actually had the data I was curious about
18:32 major open an issue and submit the topic branch as a PR referencing the issue
18:32 Eugene That looks like an entirely reasonable set of items to consider for a PR in a large, mature project like SaltStack
18:32 nixjdm joined #salt
18:33 major Eugene, just feels like common sense to me
18:33 major I wouldn't even considering it reasonable .. its like telling people to wash their hands after going to the bathroom..
18:33 Eugene Which is itself uncommon, if you have dealt with other humans for any length of time. God they are so stupid
18:33 Eugene Yeah, exactly
18:33 whytewolf as not everyone has sense. common or other wise it does need to be spelled out
18:34 major I know .. there are signs on the bathroom wall :(
18:34 netcho https://github.com/saltstack/salt/blob/d36f0ec0f035f48a0379420e12f0548461f7e033/salt/cloud/__init__.py#L1210
18:34 major its just like John Deer's warning on their tractor "Avoid Death"
18:34 major like .. wtf
18:34 major "I weep for the species"
18:34 Eugene Generally good advice
18:35 whytewolf major: the worst part is that some of those signs exist because people have done the stupid thing the sign warns against
18:35 jrklein joined #salt
18:35 major Baby Formula Label: Do not feed to infant dry.
18:36 major just .. I had always sort of hoped that the analytical nature of developers would be such that there was some sort of insulation against that level of ... yah....
18:36 Eugene This IRC channel contains opinions known to the state of California to cause cancer
18:36 major Eugene, thats just the whiskey talking
18:37 Eugene major - see also: #salt-offtopic ;-)
18:37 major fair enough
18:37 Eugene I'm bad about using it too
18:38 ecdhe astronouth7303: pip install failed from the 2017.7 and 2016.11 branch, just after running egg_info.  I upgraded pip, which caused it to not be in $PATH anymore.  I called pip directly /usr/bin/pip install ./salt but ran out of space on /tmp.  I bind-mounted a bigger storage device to /tmp...  Now pip downloads some dependencies, but fails on a setup() call; turns out pycrypto can't compile something, there's an autoconf error.
18:38 whytewolf netcho: that line of code is 2 years old.
18:38 schemanic__ joined #salt
18:38 netcho lol
18:39 astronouth7303 ecdhe: oh god, i'm so sorry
18:39 schemanic_ joined #salt
18:39 ecdhe haha, no worries.  It's been an adventure.
18:39 astronouth7303 i'm trying to decide if it's easier to cross-compile or fix autotools
18:39 netcho trying to figure out why uts not working
18:40 netcho any ideas?
18:40 ecdhe I'll take "autotools" for $400, Alex!
18:40 netcho whytewolf
18:40 whytewolf netcho: it only logs a warning so i don't see how it isn't working
18:41 schemanic_ joined #salt
18:41 netcho it sets default "salt" as master in minion config
18:41 netcho does not pull data from provider
18:42 whytewolf not in that line of code it doesn't
18:42 whytewolf and that is the default behavour
18:42 ecdhe astronouth7303: I also considered emulation.  There's kernel support for qemu-mip64
18:42 netcho what do you mean
18:42 schemanic joined #salt
18:43 netcho it used to work for me on older versions
18:43 netcho if i set master IP in provider it should be in minion config
18:43 netcho can you taker a glance at my provider?
18:43 ecdhe I could copy / from the target into an emulator and use checkinstall to build a package based on whatever autotools does.
18:43 whytewolf netcho: i mean it isn't filling in master in the provider long before that code runs
18:43 netcho s/taker/take
18:43 netcho bmv the code, i jsut searched warnimng trouygh the repo
18:44 jdipierro joined #salt
18:44 netcho similar issue https://github.com/saltstack/salt/issues/32619
18:45 netcho just different provider
18:45 whytewolf yes. I'm not saying it isn't a issue. just not in the code you provided
18:45 netcho gotcha
18:46 netcho well i am screwed
18:46 netcho :D
18:46 whytewolf the provider software should have filled in "master"
18:47 netcho instead of ip ity sets master: salt
18:47 misconfig joined #salt
18:47 ChubYann joined #salt
18:47 whytewolf yes. that is the default for master when one isn't set
18:47 netcho yep i know
18:48 whytewolf so, somewhere between the provider starting and that warning the master setting isn't getting set.
18:48 whytewolf that is what you need to find. what changed that caused master to not get set
18:48 netcho good luck me :D
18:50 misconfig Does anyone know if you can retrieve an ip address from a particular network interface with salt reactors?
18:52 astronouth7303 misconfig: if you know the interface name and minion ID? I think you might need to use `salt.function` or similar
18:52 whytewolf misconfig: to be sure personally i would setup a mine for that and call the mine in the reactor [using the runner version of mine] using network.ipaddrs
18:53 astronouth7303 wishlist: FUSE mount for the salt fileserver.
18:53 misconfig I do know the interface name. I'm trying to register new minions to route53 with salt-cloud. Everything is working great except I just can't extract the IP from the minion the same way I can set the id. {{ data['id' }}
18:54 astronouth7303 salt.function(data['id'], 'network.ipaddrs') or similar?
18:54 misconfig I could do it with grains like so: {{ salt['network.interfaces']()['eth0']['inet'][0]['address'] }} but not with reactors.
18:54 netcho well
18:54 netcho doomed
18:54 misconfig interesting, let me try that out
18:54 astronouth7303 misconfig: the latter executes on the minion
18:55 astronouth7303 reactors happen on the master
18:55 astronouth7303 so you have to get the master to dispatch to the minion
18:55 misconfig exactly. I just need the same functionality through the reactor
18:55 astronouth7303 (salt.function is what you would do in orchestrate, but reactors have slightly different environments i believe)
18:55 misconfig Currently the reactor is executing on the master - boto_route53 state run - pass the id of the new minion that called the reactor and now I need to do the same with its IP to finish the A record creation
18:56 netcho whytewolf: can you help finding?
18:56 bowhunter joined #salt
18:56 whytewolf netcho: sorry no, I have my day job to do. so just don't have the time to dig into salt code right now
18:56 netcho no worries, thanks
18:58 XenophonF hey I just installed a 2017.7 minion, and I can't run test.ping on it from the master
18:58 XenophonF but if i run cp.list_master from the minion itself, it can see everything
18:58 XenophonF what gives?
18:58 whytewolf is your master on 2017.7
18:58 XenophonF yup just upgraded it too
18:59 XenophonF i can run test.ping on the master from the master (i.e., via the salt cmd)
18:59 swills joined #salt
18:59 swills joined #salt
18:59 XenophonF but not on the test minion
18:59 whytewolf so you get an error?
18:59 XenophonF it just times out
19:00 whytewolf sounds like the test minion isn't connected.
19:00 XenophonF that's what i thought, except the minion can run cp.list_master
19:00 netcho salt-key -L
19:00 XenophonF i just accepted the minion key so that's ok
19:00 whytewolf XenophonF: salt-call cp.list-master?
19:00 XenophonF yeah, ran that on the minion and it worked
19:01 whytewolf check the salt-minion daemon is actually running
19:02 netcho whytewolf:  anyt idea how to get out of this issue? i updated half of my minions to 2017 .. if i revert masterr they won't be available to me :/
19:02 XenophonF oh good point
19:02 XenophonF didn't even think to check that
19:02 XenophonF that's it
19:02 XenophonF omg thanks whytewolf
19:03 XenophonF my intern missed that step ;)
19:03 XenophonF we're good now!
19:03 onlyanegg joined #salt
19:04 aldevar joined #salt
19:05 whytewolf netcho: well you could you know set a master in your minion config setup portion.
19:05 netcho the i need to ssh into every new minion and do it manually?
19:06 whytewolf um no,
19:06 swills joined #salt
19:06 swills joined #salt
19:06 netcho in profile?
19:06 whytewolf map file
19:07 whytewolf A map file can include grains and minion configuration options:
19:07 whytewolf https://docs.saltstack.com/en/latest/topics/cloud/map.html#cloud-map-file
19:07 netcho yea i know and i use them
19:07 netcho but nbot for everything
19:07 netcho i will try setting it up in default config
19:08 netcho default profile
19:08 netcho from which i extend other profiles
19:08 whytewolf also put in a bug.
19:10 pdayton joined #salt
19:10 CampusD joined #salt
19:12 N-Mi_ joined #salt
19:17 pdayton joined #salt
19:17 tinyurl_comSLASH joined #salt
19:18 tinyurl_comSLASH left #salt
19:18 leonkatz Hi guys, didn't the minions always get created with the same version as the master?
19:18 leonkatz of salt
19:19 leonkatz with salt-cloud
19:20 whytewolf no
19:21 whytewolf it has never done that. it always installs the latest. possable that it knows the repo for. [and since the switch to repo.saltstack.com that has been all latest] unless you tell the script a version.
19:22 whytewolf https://docs.saltstack.com/en/latest/topics/cloud/deploy.html#deploy-script-arguments
19:26 dynamicudpate joined #salt
19:28 tinyurl_comSLASH joined #salt
19:28 kerrick_ joined #salt
19:29 tinyurl_comSLASH left #salt
19:34 leonkatz thanks whytewolf don't know why i thought that
19:34 leonkatz been seeing strange errors for the last few days turns out they are version related
19:38 XenophonF epel-formula broke?
19:38 XenophonF grrr
19:38 oida_ joined #salt
19:40 Miouge joined #salt
19:41 beardedeagle joined #salt
19:42 XenophonF hm looks like salt-formula broke too
19:47 CampusD joined #salt
19:48 nixjdm joined #salt
19:48 fl3sh XenophonF: how can I add localy new winrepo packet?
19:49 XenophonF you want your own winrepo-ng package?
19:49 fl3sh yes I create new .sls file and I want to use it
19:50 astronouth7303 [2017.7] when highstating a minion from orchestrate, I'm getting `Rendering SLS 'base:ops.network' failed: Jinja variable 'salt.pillar object' has no attribute 'cidr'` but `pillar.items` from that minion shows the `cidr` variable right there.
19:50 XenophonF the simplest way to do that is to make your own winrepo-ng repository
19:50 XenophonF e.g., https://github.com/irtnog/salt-winrepo-private
19:51 fl3sh so I can't use localy create packet definitions?
19:52 XenophonF you can
19:52 XenophonF just specify the path to the folder, i think
19:52 XenophonF the winrepo-ng docs should have instructions
19:53 smartalek joined #salt
19:53 fl3sh I have my .sls in /srv/salt/win/repo-ng/salt-winrepo-ng
19:53 kerrick_ joined #salt
19:55 ahrs joined #salt
19:58 XenophonF I'm not sure you can just modify an existing repo like that
20:00 fl3sh yes, sure I can always put my packet in putty or something
20:04 fl3sh omfg I made typo
20:05 aldevar1 joined #salt
20:06 fl3sh FYI create file -> put it in repo dir -> refresh db (pkg.refresh_db) = works!
20:06 aldevar2 joined #salt
20:14 jmickle joined #salt
20:15 unzunz joined #salt
20:15 unzunz hi guys
20:15 unzunz can anyone assist with this error https://gist.github.com/anonymous/b06706714668b683836806ac53f3ad28
20:15 jmickle hi does anyone have experience with kitchen-salt and using dependencies
20:16 jmickle unzunz: have you tried looking at /var/log/salt to see the error?
20:17 astronouth7303 unzunz: somebody had that earlier. What are the versions of your minions and master?
20:19 leonkatz joined #salt
20:20 unzunz sec ill paste that
20:20 ujjain joined #salt
20:20 ujjain joined #salt
20:23 whytewolf astronouth7303: salt.pillar object as no attribute cidr? that error makes it look like you are trying to call salt.pillar.cidr
20:24 astronouth7303 it's the error i get for missing keys, too
20:25 whytewolf but salt.pillar.cidr wouldn't work anyway
20:25 ssplatt joined #salt
20:25 astronouth7303 i'm using `pillar['cidr']`
20:26 whytewolf humm, interesting.
20:27 astronouth7303 ... show_full_context() is reporting an empty pillar?
20:27 kerrick joined #salt
20:27 unzunz version report is here astronouth7303
20:27 unzunz Salt: 2016.11.3
20:27 unzunz for master ^
20:27 astronouth7303 unzunz: and the minions?
20:27 unzunz https://gist.github.com/anonymous/7cd67ab3f5adb342f024a991e9a10707
20:29 astronouth7303 why is the pillar empty when i highstate a minion with orchestrate in 2017.7?
20:30 unzunz 2017.7.0
20:30 unzunz on the minion that isn't working
20:30 astronouth7303 unzunz: you can't use newer minions with older masters
20:30 unzunz I don't even know why it decided to deploy the newer version of salt on that minion, the others I just deployed have the older, that must be it
20:30 unzunz weird
20:30 whytewolf astronouth7303: is it not empty when not using orchestration for your highstate?
20:30 astronouth7303 did you create it in the last ~24hrs?
20:31 astronouth7303 whytewolf: yeah, using state.apply works
20:31 whytewolf unzunz: if you use salt-cloud for deployment the bootstrap script by default installs the newest version. you need to flag the version you want to install using the boot strap script_args
20:32 Rumbles joined #salt
20:33 astronouth7303 `salt minion state.apply` works, but `salt-run state.orchestrate orch.myapp.deploy` (which includes a highstate block) doesn't
20:35 whytewolf astronouth7303: I'm testing now.
20:35 DammitJim joined #salt
20:36 astronouth7303 (for the record, this was working in 2016.11)
20:36 whytewolf well didn't think you would be mentioning it if it didn't
20:37 astronouth7303 figured it was worth saying explicitly
20:37 whytewolf humm, odd. pillar.get in a salt.function is "working" [it pulls the info just doens't render all that great]
20:38 unzunz ok it's definitely got 2017 defined in the bootstrap-salt.sh script
20:39 unzunz hrm.. to test id definitely like to just define the lower version in a profile, instead of the entire salt master, just until I iron it out, then I can tell the whole team that isn't working (and im not sure how they didn't notice)
20:39 testtest joined #salt
20:39 testtest left #salt
20:40 olivervscreeper joined #salt
20:40 mpanetta joined #salt
20:40 olivervscreeper Hey! Are there any known ways to use OVH with Salt Cloud?
20:42 whytewolf astronouth7303: I'm afraid i have bad news. it works for me in 2017.7.0
20:42 astronouth7303 me, too
20:43 astronouth7303 well, a simple pillar.get called from orch works
20:43 whytewolf astronouth7303: through orchestration. with rendering
20:43 mikecmpbll joined #salt
20:44 astronouth7303 time to build up a minimum failure, i guess
20:44 astronouth7303 uggh
20:44 astronouth7303 i don't want to be dealing with this at quarter to 5
20:44 debian1121 joined #salt
20:45 whytewolf I might have to build a more complicated test case. but so far i have not gotten it to fail.
20:49 nixjdm joined #salt
20:50 astronouth7303 whytewolf: https://gist.github.com/astronouth7303/3d17cf6679a9a395bb93f1648fd8ceb0
20:51 fl3sh XenophonF: how you manage packets updates? Are you checking it manually and change it in you repo?
20:51 unzunz ok bumped that version down, here's a dumb question for anyone willing to humor me
20:51 unzunz im testing it now
20:51 whytewolf you have a log module?
20:52 astronouth7303 whytewolf: ? I just pulled from the standard minion log?
20:52 astronouth7303 or do you mean the use of https://docs.saltstack.com/en/latest/topics/jinja/index.html#logs ?
20:53 unzunz why and how did salt suddenly update that bootstrap version in the file on me... I don't think anyone on my team updated it, the file had an old timestamp, I suppose that depends how these boxes update salt on their own..
20:53 unzunz because they were all deploying with the older matched version prior
20:53 unzunz to 24 hours ago
20:54 astronouth7303 the bootstrap version isn't tied to the salt version
20:54 astronouth7303 2017.7.0 was released yesterday
20:55 astronouth7303 i would argue that maybe salt-cloud shouldn't deploy broken minions by default, though :P
20:55 unzunz hehe, agreed.. ok hrm.. so yes that did not fix it, it's still deploying it with the new version
20:56 unzunz I thought telling the bootstrap version what to do would force it down to the one defined, am I missing something?
20:58 astronouth7303 (fun trick: I think you can treat that gist as a formula)
20:58 astronouth7303 unzunz: i would think so, too? How are you configuring that?
20:59 whytewolf unzunz: what does your script_args look like?
20:59 whytewolf https://docs.saltstack.com/en/latest/topics/cloud/deploy.html#deploy-script-arguments
20:59 leonkatz i'm having an issue getting my script_srgs to work
20:59 whytewolf along with https://github.com/saltstack/salt-bootstrap
21:00 leonkatz script_args: git 2016.11.4
21:00 leonkatz in profile
21:02 leonkatz but was getting an error
21:02 astronouth7303 leonkatz: missing git ref? I think that needs 2016.11 or v2016.11.4
21:02 astronouth7303 leonkatz: check the branches/tags available at https://github.com/saltstack/salt
21:03 unzunz looks like no script args are defined in cloud.profiles.d/vmware.conf
21:03 unzunz and from what I am reading they can go in the map file as well
21:03 leonkatz https://gist.github.com/leonkatz/7ae1c400de2e1efc4f646fffaa972ee0
21:03 leonkatz ok i'll give it a try
21:06 Hybrid joined #salt
21:06 whytewolf okay. astronouth7303 the test you posted was invalid. basilcy there is no salt.log.* so nothing did anything [i would have expected an error but none was printed] your render of {} is exactly what was in that yml file as it would be blank as you didn't output anything to it. basicly there was nothing there. however i was able to get the error you reported by limited down to {{pillar['roles']}}
21:07 unzunz ok basically im adding this to my maps file
21:07 unzunz script_args: git v2016.11.3
21:07 astronouth7303 so the docs lie. cute.
21:07 unzunz so that's the master version of salt
21:07 smartalek joined #salt
21:07 unzunz look good to you guys?
21:07 winsalt joined #salt
21:07 whytewolf astronouth7303: what doc are you following?
21:08 astronouth7303 https://docs.saltstack.com/en/latest/topics/jinja/index.html#logs
21:08 whytewolf oh,
21:08 whytewolf huh okay maye there is a logging system ... that is new.
21:09 whytewolf although it didn't log anything... so thats a huh thing
21:09 whytewolf maybe it needs to actually have a message to log
21:10 whytewolf tried with just {{pillar}} and it did act just like a blank yaml which it shouldn't
21:10 whytewolf anyway. bug report. to add to the pile
21:10 astronouth7303 time to roll back salt...
21:11 whytewolf that one will probley get marked major
21:11 unzunz whytewolf: does this look good to you script_args: git v2016.11.3
21:11 astronouth7303 let me build a clearer test case
21:11 unzunz basically in my maps file to test, then ill put it in the vmware.conf
21:12 whytewolf unzunz: yeah that looks good.
21:12 whytewolf it will try installing from git like that if thats what you want.
21:12 unzunz ah balls, hrm.. i think it's been doing it via rpm
21:12 whytewolf then just drop the git
21:13 unzunz lovely :3
21:13 unzunz thank you
21:13 unzunz here we go.. *paws crossed*
21:13 Guest73 joined #salt
21:14 astronouth7303 whytewolf: updated https://gist.github.com/astronouth7303/3d17cf6679a9a395bb93f1648fd8ceb0
21:14 astronouth7303 clearer now?
21:15 whytewolf yeap.
21:15 mikecmpbll joined #salt
21:16 noraatepernos joined #salt
21:16 major whytewolf, what am I getting marked on?
21:16 joe_n joined #salt
21:17 whytewolf lol. i meant the status of a major error.
21:17 major my momma disagrees :(
21:17 major anyway ..
21:17 major soo .. you are saying I need to hurry up and submit this PR ..
21:17 whytewolf the pillar dict object being blank when called through salt.state orchestration
21:18 major yah .. not good .. but .. you know .. my bug is a higher priority to me and all that ;)
21:18 whytewolf everyones bug is a higher priority to them :P
21:19 astronouth7303 https://github.com/saltstack/salt/issues/42403
21:19 unzunz I don't think it liked that v2016.11.3 'v' prefix
21:19 unzunz in my script args
21:20 unzunz * ERROR: Installation type "v2016.11.3" is not known...
21:20 whytewolf astronouth7303: if you want to have a crack at the bug most likely the culprit from what i was seeing in a difference between salt.state and salt.function is that salt.state killed it so is most likely transfering over the master pillar object which salt will happly try to merge into the pillar which will overright it will a blank dict [cause master pillar is generally blank]
21:21 astronouth7303 unzunz: https://github.com/saltstack/salt-bootstrap/blob/develop/bootstrap-salt.sh#L282
21:21 whytewolf i completly forgot the v was part of the git naming.
21:22 astronouth7303 whytewolf: ... i'll look? I only sort of have an understanding what's going on
21:22 whytewolf astronouth7303: if you are lucky. the fix is just is salt.state wasn't given a - pillar field directly then don't pass the pillar to the minion
21:24 whytewolf damn it. that isn't it. i just tried with master pillar data in place and it still was blank. so it is passing a blank pillar not the master pillar
21:25 Hybrid joined #salt
21:25 astronouth7303 from a quick read of states/saltmod.py, it's not passing any pillar data?
21:26 unzunz it's still unhappy about the script_args hrm
21:26 unzunz * ERROR: Installation type "2016.11.3" is not known...
21:26 whytewolf stable 2016.11.3
21:26 astronouth7303 unzunz: https://github.com/saltstack/salt-bootstrap/blob/develop/bootstrap-salt.sh#L286-L297
21:27 major I mean .. to be fair .. the fact that I can't use '~' and '~<user>' as part of the ssh_priv file prefix for salt-ssh is pretty messed up
21:27 major particularly since it works in other areas of salt-ssh
21:28 major It took me forever to figure out what the bug was simply because I can't comprehend not supporting it
21:29 major well .. I mean .. I can use it .. but salt-ssh thinks the file doesn't exist and then tries to overwrite it
21:29 major >.<
21:31 unzunz whytewolf: and this goes in my cloud.maps file correct?
21:32 whytewolf it should be able to me in map files i think. iirc maps can take anything that profiles can
21:33 whytewolf ahh "script_args can be specified in either the profile or the map file" from the documentation
21:33 astronouth7303 whytewolf: it looks like saltmod.state shouldn't be passing a `pillar` kwarg at all, so my guess is it's in the minion side somewhere? I should see if I can spy on what traverses the message bus and see what the difference is between applying it directly and and applying it throuch orch
21:33 whytewolf astronouth7303: you are right, saltmod state is not passing a blank pillar if pillar isn't set.
21:34 whytewolf the next item in line is saltutil.cmd
21:34 whytewolf which did have changes in 2017.7.0 ...
21:34 jmickle joined #salt
21:34 svij1 joined #salt
21:35 censorshipwreck joined #salt
21:37 astronouth7303 but doesn't make any references to pillar, so i would have to traverse down to client.cmd_iter
21:38 unzunz bah well no error on the scriptargs, but it's still installing 2017 from the yum repo
21:38 unzunz Installed:   salt-minion.noarch 0:2017.7.0-1.el7
21:38 unzunz so the original problem remains
21:39 whytewolf well, there is  the next option of writing your own custom bootstrap script that installs salt.
21:40 whytewolf cause it sounds like script_args is also not working
21:42 merlincorey joined #salt
21:43 nethershaw joined #salt
21:43 merlincorey does anyone know offhand what salt-minion does when the network route changes, and/or where I can look to find out more?  source is fine, I can read it, just not sure where in the massive list of sources to start
21:44 astronouth7303 merlincorey: ... standard network stuff? The TCP connection will time out and it'll attempt to reconnect?
21:44 astronouth7303 whytewolf: i'm getting pretty far down and i'm not seeing anything that cares about pillars?
21:46 whytewolf astronouth7303: maybe downgrade and put your bug.
21:47 astronouth7303 that's what I'm thinking i have to do for production, yes
21:47 astronouth7303 "put your bug"?
21:47 merlincorey astronouth7303: it doesn't seem like its doing that, or at least it might not have a "standard" timeout (which IIRC is typically 60 seconds).  Is this perhaps a configurable value or do you have any investigatory directions I can run in? :)
21:47 whytewolf sorry, my head is hurting.
21:47 merlincorey to expound slightly
21:47 astronouth7303 i know that feel
21:47 sh123124213 is anybody using remote rsyslog with : file:///dev/log ?
21:48 nixjdm joined #salt
21:48 merlincorey I have a device that is multihomed with one of the networks used as a fallback in case the primary DSL line goes down (don't ask :P).  I have salt-minion running with the minion accepted to my master and working with `test.ping`.  I then remove the ethernet cable for the DSL.
21:49 merlincorey I have a daemon that checks connectivity and does some network route changing stuff every 5 minutes
21:49 merlincorey and I have a cron running that is curl'ing a web page every minute
21:49 astronouth7303 whytewolf: thanks for the help. maybe i'll get some progress tomorrow.
21:50 merlincorey so I unplug the ethernet for the DSL and within a minute I see the curl reaching my webserver from the backup ISP's address
21:50 merlincorey 20 minutes later, 20 pings later, `test.ping` to the minion is still not working :/
21:51 merlincorey errr by `20 pings later` I meant the `curl` pings to my webserver of course :)
21:51 merlincorey so anyway... I'm looking for any threads to investigate this further
21:52 Miouge joined #salt
21:56 joe_n joined #salt
21:57 mikecmpbll joined #salt
21:59 onlyanegg joined #salt
22:01 ssplatt joined #salt
22:05 high_fiver joined #salt
22:07 v3x why does salt-api keep giving me "setval expects 2 arguments, 1 given" when i try to set a grain value
22:07 v3x i am including 2 arg statements.
22:08 xet7 joined #salt
22:22 ecdhe joined #salt
22:25 mikecmpbll joined #salt
22:30 DoomPatrol hrm, "No function declared in state '$foo'in SLS '$state/$foo'
22:30 DoomPatrol weird in logs it appears that everything renders appropriately
22:33 leonkatz {%- set salt_version = salt['test.version']() %}
22:33 leonkatz script_args: git v{{ salt_version }}
22:33 leonkatz this fixed it for me
22:36 gareth__ joined #salt
22:37 DoomPatrol hmm, did some change and still that error
22:43 DoomPatrol ha figured it out
22:44 DoomPatrol pfft pebkac
22:48 icebal joined #salt
22:59 mikecmpbll joined #salt
23:16 icebal joined #salt
23:35 woodtablet arghh...
23:36 woodtablet nitrogen is messing with me.
23:36 woodtablet oh goodie pillar encyrption is added!!
23:36 pdayton joined #salt
23:37 Renich joined #salt
23:37 woodtablet does anyone know if Nitrogen has the pillar list merging feature added ? i did a quick search on the release notes and dont see it
23:38 woodtablet where if a pillar has a list, and another pillar of the same name comes up, it can merge the lists, instead of cobblering ? (for example packages list)
23:51 ssplatt joined #salt
23:52 om2 joined #salt
23:54 joe_n joined #salt
23:57 woodtablet hmm.. other cool things in nitrogen, nice

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