Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-08-01

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

All times shown according to UTC.

Time Nick Message
00:17 KingOfFools joined #salt
00:18 rpb joined #salt
00:23 KingOfFools joined #salt
00:35 nick123 joined #salt
00:40 _aeris_ joined #salt
00:40 sh123124213 joined #salt
00:52 onlyanegg joined #salt
00:54 https_GK1wmSU joined #salt
01:00 https___GK1wmSU joined #salt
01:00 onlyanegg joined #salt
01:00 https__GK1wmSU joined #salt
01:00 https_GK1wmSU joined #salt
01:05 astronouth7303 this is why i made myself something with autocomplete
01:12 cyteen joined #salt
01:26 onlyanegg joined #salt
01:40 https_GK1wmSU joined #salt
01:40 onlyanegg joined #salt
01:41 https_GK1wmSU left #salt
01:51 ilbot3 joined #salt
01:51 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:52 DammitJim joined #salt
01:58 nick123 joined #salt
02:27 usernkey joined #salt
02:40 sh123124213 joined #salt
02:50 svij4 joined #salt
03:16 DammitJim joined #salt
03:20 ekristen joined #salt
03:21 swa_work joined #salt
03:22 donmichelangelo joined #salt
03:22 DammitJim joined #salt
03:22 ekristen I'm having problems getting publish.publish to work all of a sudden, I've even tried setting the peer config to .* but nothing will return
03:22 ekristen I try and run publish.publish '*' test.ping and it just comes back empty
03:23 ekristen I see no errors anywhere
03:41 _aeris_ joined #salt
03:54 om2 joined #salt
04:00 zerocoolback joined #salt
04:01 evle1 joined #salt
04:04 mvensky joined #salt
04:14 ninjada joined #salt
04:18 svij4 joined #salt
04:27 gmoro joined #salt
04:32 gmoro joined #salt
04:34 nick123 joined #salt
04:38 treaki_ joined #salt
04:52 hasues joined #salt
04:53 hasues left #salt
04:54 mbuf joined #salt
04:57 golodhrim|work joined #salt
05:00 lessthan joined #salt
05:00 lessthan does anyone have a chart showing users/popularity of puppet/chef/ansible/salt?
05:02 nku debian has popcon, which of course is only debian, and only for users who enable it.. other than that it's really hard to measure usage
05:02 nku or you could look at google trends..
05:02 lessthan nku, how would you get an accurate measure of google trend for salt?
05:02 nku but ofc salt/puppet/chef would suck as queries..
05:02 lessthan yea haha
05:03 nku yeah, popcon
05:03 hemebond I would guess puppet > chef > ansible > salt
05:03 nku lessthan: you could do puppet + linux or somesuch
05:03 nku define >
05:03 lessthan hemebond, I haven't seen anyone so far say puppet or chef are actually superior though
05:03 hemebond greater-than
05:03 lessthan is it just that they were first to market?
05:04 hemebond lessthan: Oh I thought you were talking about popularity
05:04 nku greater number of users? managed hosts?
05:04 lessthan hemebond, I was
05:04 lessthan I'm trying to tease out if there is a trend towards salt
05:04 lessthan I want to use it, but not if the industry is stuck on puppet/chef for years
05:04 hemebond I certainly hope there is.
05:04 svij4 joined #salt
05:05 hemebond I don't care what others are using, Salt is better.
05:05 nku lessthan: just try them all and see what you like
05:05 lessthan the one downside to salt I'd heard was that it was buggy
05:05 nku personally, chef/puppet just seemed... not so well designed
05:05 hemebond Salt has more bugs than Puppet, yes.
05:05 KingOfFools joined #salt
05:05 hemebond It's also bigger and does more.
05:06 hemebond And is newer.
05:06 hemebond But also completely open and updates very frequently.
05:06 nku lessthan: what's your use case anyway?
05:06 nku i usually recommend ansible over salt for smaller setups, but mostly because the learning curve is a little smoother
05:07 lessthan I don't actually have a use case
05:08 nku lessthan: find one :) automating things at home is nice first step
05:10 https__GK1wmSU joined #salt
05:11 https_GK1wmSU joined #salt
05:13 hemebond "some of SaltStack's customers include LinkedIn, Comcast, Rackspace, and NASA"
05:15 https___GK1wmSU joined #salt
05:15 https__GK1wmSU joined #salt
05:15 nku yeah, certainly can't go wrong with salt
05:16 nku also helps that python is getting more and more popular
05:16 sgo_ joined #salt
05:16 https___GK1wmSU left #salt
05:16 https__GK1wmSU left #salt
05:17 Bock joined #salt
05:27 hemebond Yes, the language underneath is reason enough to drop Puppet and Chef.
05:36 impi joined #salt
05:41 https_GK1wmSU joined #salt
05:43 https___GK1wmSU joined #salt
05:43 zerocool_ joined #salt
05:44 hoonetorg joined #salt
05:50 ahrs joined #salt
05:53 sjorge joined #salt
06:02 ecdhe joined #salt
06:16 Ricardo1000 joined #salt
06:26 Ni3mm4nd joined #salt
06:27 https_GK1wmSU joined #salt
06:32 om2 joined #salt
06:34 https_GK1wmSU joined #salt
06:35 mvensky joined #salt
06:44 preludedrew joined #salt
06:48 lessthan one last question if anyone's still around
06:49 lessthan one of the cons listed for salt is that it requires daemons
06:49 lessthan a con for chef is that it doesn't have push (is this still true?)
06:50 lessthan why does salt use daemons? is it sort of necessary for master to client pushes?
07:09 usernkey joined #salt
07:19 twiedenbein joined #salt
07:28 ninjada_ joined #salt
07:35 _KaszpiR_ joined #salt
07:36 Hybrid joined #salt
07:38 sjorge joined #salt
07:42 kukacz joined #salt
07:42 haam3r_ salt also has salt-ssh this way you don't need daemons, but you lose some functionality
07:43 haam3r_ salt uses daemons, because the minion connects to the master
07:43 viq < hemebond> But also completely open and updates very frequently.
07:43 viq salt is about as open as puppet
07:47 impi joined #salt
07:48 ninjada joined #salt
07:50 mikecmpbll joined #salt
07:52 Electron^- joined #salt
07:59 _KaszpiR_ joined #salt
08:01 Rumbles joined #salt
08:06 cyborg-one joined #salt
08:15 sriman joined #salt
08:23 nick123 joined #salt
08:30 Mattch joined #salt
08:33 rewbycraft joined #salt
08:35 jhauser joined #salt
08:36 Elsmorian joined #salt
08:40 ecdhe joined #salt
08:40 pbandark joined #salt
08:42 bartuss7 joined #salt
08:44 bartuss7 left #salt
08:44 bartuss7 joined #salt
08:44 bartuss7 left #salt
08:45 bartuss7 joined #salt
08:45 bartuss7 left #salt
08:45 bartuss7 joined #salt
08:45 bartuss7 left #salt
08:46 bartuss7 joined #salt
08:47 bartuss7 left #salt
08:47 bartuss7 joined #salt
08:48 bartuss7 Hello Guys. When I run saltutil modeule, new job is created on minion for saltutil?
09:00 kennydude joined #salt
09:01 kennydude Hi, I'm having a problem with salt complaining about "too many functions defined in state 'cmd'" https://gist.github.com/kennydude/61c6468ed1fd899f1ac6971e56d801a7
09:02 viq kennydude: what is this on line 15?
09:02 abulford joined #salt
09:03 kennydude viq: i think it refers to the yarn section, i'll add the whole file
09:03 kennydude it should be on the top of that link now
09:04 viq kennydude: you're missing something on that line, just "- yarn" means absolutely nothing.
09:05 viq https://gist.github.com/kennydude/61c6468ed1fd899f1ac6971e56d801a7#file-salt-yaml-L78 - try removing that line and see if it works. Or tell me what you think it's supposed to be doing ;)
09:06 kennydude i think it's supposed to require yarn to run
09:06 kennydude would making it `name: yarn` run yarn?
09:07 viq I think you may want "- cmd: yarn" under require then
09:07 impi joined #salt
09:09 kennydude ah, i tried adding `name: yarn` as it requires yarn to be installed, and to just run it in that directory
09:10 kennydude and it still comes out with the same error :/
09:10 viq oh, and yes, currently "yarn_jsapp" will run command "yarn_jsapp", if you want to run command "yarn" then you need "name: yarn" in there indeed
09:10 Hybrid joined #salt
09:10 viq Does it give you line number?
09:11 viq or name?
09:11 kennydude all i can get is `Too many functions declared in state 'cmd' in SLS 'app'` due to our setup right now :/
09:12 avasiu joined #salt
09:14 viq any chance pillar['project']['log'] or pillar['project']['repository'] is 'cmd' ?
09:23 kennydude viq: nope
09:28 viq kennydude: try putting all the name parameters in quotes
09:28 viq so eg - name: "{{ pillar['project']['venv'] }}/bin/python manage.py migrate --noinput --settings={{ pillar['settings']['import'] }}"
09:32 ProT-0-TypE joined #salt
09:41 N-Mi joined #salt
09:41 N-Mi joined #salt
09:44 redonkuless joined #salt
09:46 ikarpov joined #salt
09:54 onmeac joined #salt
10:07 Rumbles joined #salt
10:25 mugsie joined #salt
10:25 mugsie joined #salt
10:29 _KaszpiR_ joined #salt
10:33 mugsie joined #salt
10:33 mugsie joined #salt
10:45 kennydude huh, turned out to be the weird block at the top (which i didn't write, i have barely any idea how to use salt)
10:53 Ni3mm4nd joined #salt
11:30 tacoboy joined #salt
11:31 karlthane joined #salt
11:34 xet7 joined #salt
11:47 nf joined #salt
11:48 nfahh joined #salt
11:48 johnkeates joined #salt
11:51 _KaszpiR_ joined #salt
11:52 nfahldieck joined #salt
11:56 NV joined #salt
11:59 nfahldieck hello, all my minions (around 1500) trigger a pillar.get towards the master every 3 hours. I don't know why, might this be an internal function or can you guide me in a direction of analysing this behaviour? I guess I'm stuck. This consumes around 10% of CPU usage on the master, which is bad whenever it happens parallel with a highstate.
12:03 kukacz joined #salt
12:06 hoonetorg joined #salt
12:10 numkem joined #salt
12:15 Neighbour nfahldieck: Try the 'pillar_cache_ttl' setting
12:19 nfahldieck isn't this a master config option? My minions execute a 'pillar.get', so shouldn't this be a minion setting? Also pillar_cache is set to FALSE in my master config. 'pillar_cache_ttl' is only used if the prior option is set to TRUE.
12:22 Neighbour hmm, I thought the pillar cache was minion-driven...guess I was wrong then
12:24 DammitJim joined #salt
12:33 Horgix joined #salt
12:39 xet7 joined #salt
12:40 cgiroua joined #salt
12:41 xet7 joined #salt
12:44 ivanjaros joined #salt
12:48 ArawN left #salt
12:48 Lazypete joined #salt
12:55 kedare joined #salt
13:02 DammitJim joined #salt
13:02 Salteer5 joined #salt
13:03 whyzgeek joined #salt
13:06 kukacz joined #salt
13:19 Cloudskipper joined #salt
13:20 J0hnSteel joined #salt
13:21 racooper joined #salt
13:23 Cloudskipper I have a question regarding becaons. I have a beacon defined in pillar and see it applied to the minion with "salt 'MINION' beacons.list" ... now I change a parameter like interval: TIME .. how do I get this propagated to the minion? A highstate doesnt work. salturil:refresh_pillar etc doesnt work.
13:23 Cloudskipper Only a minion restart works .. is this intended?
13:27 Cloudskipper if I run this "salt 'minion1' pillar.items" the updated info shows up ...
13:35 carlpett joined #salt
13:35 babilen Cloudskipper: You just update the pillar
13:35 babilen saltutil.refresh_pillar
13:36 Cloudskipper thats what im doing .. and apparently the pillar data gets to the minion .. but when I run salt MINION beacons.list it still shows to old data
13:36 spiette joined #salt
13:36 Cloudskipper once i restart the minion the beacon has the updated pillar data as well
13:40 jmiven joined #salt
13:42 gmoro joined #salt
13:43 psychi[m] joined #salt
13:54 dendazen joined #salt
13:55 babilen Cloudskipper: saltutil.refresh_pillar followed by saltutil.refresh_beacons ?
13:55 tapoxi joined #salt
13:59 ssplatt joined #salt
14:00 benjiale[m] joined #salt
14:00 hackel joined #salt
14:00 ThomasJ|m joined #salt
14:00 toofoo[m] joined #salt
14:00 jerrykan[m] joined #salt
14:00 freelock joined #salt
14:00 theblazehen joined #salt
14:00 gomerus[m] joined #salt
14:00 fujexo[m] joined #salt
14:00 kukacz_ joined #salt
14:01 kukacz__ joined #salt
14:02 Cloudskipper doesnt work ... the pillar data is there, and refresh_beacons returns true ....
14:02 Cloudskipper yet beacons.list still returns the old beacon
14:02 babilen Which version is that?
14:02 Cloudskipper salt-minion 2017.7.0 (Nitrogen)
14:02 Cloudskipper master same
14:17 bartuss7 left #salt
14:17 carlpett joined #salt
14:24 XenophonF joined #salt
14:25 XenophonF does anyone have advice for troubleshooting SaltReqTimeoutError exceptions?
14:25 XenophonF I'm at my wits end.
14:25 XenophonF master in Ireland, minions in the U.S., Mali, Uganda, and India
14:25 XenophonF RTTs all under 300 ms
14:26 XenophonF plenty of bandwidth
14:26 XenophonF Mali probably has the worst Internet link, and I've deployed minions there before without any difficulties.
14:26 XenophonF all of a sudden everything except for stuff in Ireland and the U.S. can't talk to the master
14:27 XenophonF I don't know if it's due to changes in 2017.7 or 2016.11
14:27 XenophonF Setting auth_safemode=True and ping_interval=1 doesn't seem to help.
14:29 tiwula joined #salt
14:31 dunz0r XenophonF: Tried setting tcp_keepalive to true and tcp_keepalive_idle to something like 60?
14:32 mikea joined #salt
14:32 XenophonF no but I can try that next
14:33 XenophonF looks like tcp_keepalive defaults to True
14:34 XenophonF and tcp_keepalive_idle defaults to 300
14:40 pewpew joined #salt
14:44 mikecmpbll joined #salt
14:52 zerocoolback joined #salt
14:54 dunz0r XenophonF: I've got mine at 120, did notice a difference in the amount of minions that stay connected
14:56 XenophonF gotcha
15:00 bowhunter joined #salt
15:01 sarcasticadmin joined #salt
15:01 XenophonF man this packet capture is weird
15:01 XenophonF the minion makes and then quickly tears down a connection to 4506 on the master
15:02 XenophonF over and over and over again
15:02 mikea check minion_master.pub
15:03 mikea I've seen that when the minion distrusts the masters public key
15:03 XenophonF OK
15:03 mikea you can actually remove minion_master.pub and the minion will recreate it
15:04 zerocoolback joined #salt
15:04 om2 joined #salt
15:05 impi joined #salt
15:06 XenophonF the file on the broken minion is identical to the one on the master itself
15:06 XenophonF but i'm going to try deleting it anyway
15:08 XenophonF same behavior as before - multiple, repeated connections to 4506
15:09 keltim joined #salt
15:10 svij4 joined #salt
15:10 mikecmpbll joined #salt
15:10 XenophonF i'm going to restart the master and the minion with debug or maybe trace logging enabled
15:11 XenophonF same versions of CentOS and Salt on both sides (CentOS 7 and Salt 2017.7.0)
15:11 XenophonF firewalls are open
15:15 fatal_exception joined #salt
15:23 onlyanegg joined #salt
15:25 Inveracity joined #salt
15:28 zerocoolback joined #salt
15:47 mrrc joined #salt
15:52 JohnnyRun joined #salt
15:53 JohnnyRun joined #salt
15:57 drawsmcgraw joined #salt
15:57 tapoxi anyone know of ovirt support for salt-cloud?
16:03 rmelero joined #salt
16:05 om2 joined #salt
16:06 AdamSmithSundanc joined #salt
16:06 AdamSmithSundanc left #salt
16:07 AdamSmithSundanc joined #salt
16:12 SundanceAdamSmit joined #salt
16:14 svij4 joined #salt
16:16 SundanceAdamSmit I have been building a saltOSS system for configuration management and would like to have a web gui for it but we can't implement enterprise edition right now.  I have tried to use molten and it seems a bit buggy,  I was wondering if anyone has used saltpad or foreman with salt, what their experiances are and if it is even worth it right now to try to use a webui that is not built by saltstack.
16:19 aneeshusa joined #salt
16:21 bowhunter joined #salt
16:23 wendall911 joined #salt
16:24 XenophonF With debug logging on the minion, I see "Initializing new AsyncAuth" over and over and over
16:24 XenophonF which corresponds with the repeated connections on 4506
16:24 XenophonF it says "returning information for job"
16:25 capn-mor1an left #salt
16:26 XenophonF so maybe those are normal?
16:26 XenophonF still seeing "minion function caused an exception"
16:26 XenophonF this doesn't make any sense
16:28 XenophonF this is weird
16:28 XenophonF on the master, it says initializing new AsyncZeroMQReqChannel for ... tcp://127.0.0.1:4506
16:28 XenophonF shouldn't that be 0.0.0.0?
16:29 XenophonF maybe that's just the salt command querying the salt-master service
16:30 Lionel_Debroux joined #salt
16:33 XenophonF but which minion function? state.apply? but where's the error from that?
16:39 SundanceAdamSmit joined #salt
16:42 XenophonF time to rtfs
16:46 debian112 joined #salt
17:05 beardedeagle joined #salt
17:08 impi joined #salt
17:11 usernkey joined #salt
17:24 Ni3mm4nd joined #salt
17:27 censorshipwreck joined #salt
17:27 XenophonF nothing weird in the packet captures
17:29 XenophonF sometimes, if I restart the salt-master and salt-minion services, I can run state.apply on the minion and it works
17:30 astronouth7303 XenophonF: run them manually with `-l DEBUG` and see if that gives any insight?
17:30 astronouth7303 s/them/salt-master and salt-minion/
17:31 XenophonF i tried that earlier today
17:31 XenophonF i see a bunch of debug and info log messages, but nothing indicating why zeromq times out
17:32 astronouth7303 are you sure you can make the TCP connection between the minion and the master?
17:32 XenophonF yes
17:32 astronouth7303 matching versions?
17:32 XenophonF I can see the activity in tcpdump on both sides
17:32 XenophonF yes but let me double check
17:33 XenophonF odd on the master msgpack-python is 0.4.8, while on the minion it's 0.4.6
17:35 XenophonF there are a few extra packages on the master that aren't on the minion (dateutil, gitdb, gitpython)
17:37 XenophonF huh - on the master it's python2-msgpack-0.4.8-1.el7 built by the fedora project, and on the minion it's python-msgpack-0.4.6-1.el7 built by saltstack
17:38 XenophonF I wonder if that discrepancy is the source of my troubles.
17:39 astronouth7303 shouldn't, since msgpack is a standard? Check the msgpack changelog
17:39 rmelero I've seen similar issues related to MTU
17:40 rmelero connection establishes but data packets get dropped
17:40 bowhunter joined #salt
17:40 XenophonF I thought it could be path MTU, too, but I'm not seeing unusual drops or errors in the packet captures.
17:41 J0hnSteel joined #salt
17:53 XenophonF I enable EPEL on all my CentOS minions via Salt.
17:53 XenophonF So the broken minions don't have it enabled yet.
17:54 XenophonF Manually enabling EPEL and running `yum upgrade` shows it upgrading python-crypto, python-futures, and python-msgpack with versions from EPEL.
18:01 J0hnSteel joined #salt
18:03 XenophonF Installing epel-release and then upgrading to sync packages with the master didn't fix it.
18:10 ssplatt my dependencies: are completely broken in the latest kitchen-salt :(
18:16 ssplatt oh, open bug.  sigh.
18:16 J0hnSteel joined #salt
18:19 Guest73 joined #salt
18:21 J0hnSteel joined #salt
18:22 mikecmpbll joined #salt
18:26 onlyanegg joined #salt
18:32 ChubYann joined #salt
18:33 Guest73 joined #salt
18:35 J0hnSteel joined #salt
18:37 nixjdm joined #salt
18:38 darioleidi joined #salt
18:44 colabeer joined #salt
18:46 druonysus joined #salt
18:57 XenophonF well running state.apply locally via salt-call seems to be working, although it's taking forever
18:57 onlyanegg joined #salt
19:00 DammitJim joined #salt
19:00 _KaszpiR_ joined #salt
19:00 stuart07 joined #salt
19:05 Hybrid joined #salt
19:09 Hybrid joined #salt
19:10 stuart07 joined #salt
19:12 stuart07 joined #salt
19:21 mpanetta joined #salt
19:25 fatal_exception joined #salt
19:25 _KaszpiR_ joined #salt
19:26 jhauser joined #salt
19:26 cgiroua_ joined #salt
19:28 censorshipwreck joined #salt
19:31 Hybrid joined #salt
19:33 XenophonF completed successfully
19:34 XenophonF WTF is wrong with my Salt deployment?
19:34 XenophonF I'm going to try setting up a syndic next week.  Maybe a local master will make things work better.
19:35 J0hnSteel joined #salt
19:36 astronouth7303 XenophonF: try running the setup steps in local VMs first? Sounds like you've got something really weird going on.
19:37 colabeer joined #salt
19:39 onlyanegg joined #salt
19:40 sh123124213 joined #salt
19:41 J0hnSteel joined #salt
19:45 oida joined #salt
19:47 J0hnSteel joined #salt
19:53 J0hnSteel joined #salt
19:53 lordcirth_work I have a nodegroup glob that works on the command line but not as a nodegroup.  Any tips?
19:54 function07 joined #salt
19:56 astronouth7303 lordcirth_work: nodegroups have some pretty big caveats because by default, only the master has the nodegroup information but the minions evaluate matchers
19:57 lordcirth_work astronouth7303, it's a standard glob on minion id, doing it in lots of other nodegroups, just this one doesn't work
19:57 astronouth7303 oh, defining the nodegroup, not using it
19:58 lordcirth_work astronouth7303, yeah, if I paste the glob definition into a salt command, it matches, but -N nodegroup doesn't.
19:58 lordcirth_work And it doesn't say the group doesn't exist, it says no minion matched
19:58 darioleidi joined #salt
20:09 nixjdm joined #salt
20:14 function07 Is there any way to get the contents of a file that sits on master into either a jinja variable or pydsl variable?
20:17 whytewolf someone actually still uses pydsl?
20:19 whytewolf anyway, best way to get a file into jinja is to put it either in file_root or pillar_root
20:19 whytewolf other wise the minion just won't see it
20:20 function07 I stumbled upon it the other day, basically I need to run a compare on a master package list on master to an 'rpm -qa' output on centos7 or rhel7 hosts and install the missing packages
20:22 whytewolf that sounds like something that should be a pillar then
20:22 DammitJim what is this about not using sha256 for a hash_type on minions
20:22 DammitJim do I need to edit my minion files on /etc/salt/minion?
20:23 function07 thanks @whytewolf I'll check into that
20:24 whytewolf DammitJim: what? default is sha256
20:25 XenophonF yeah I get that error all over the place too
20:26 ssplatt gtmanfred: thanks for merging that file path dependency in kitchen-salt
20:26 whytewolf what error? I havn't seen an error about hash_type
20:27 ssplatt hash_type used to default to md5 iirc
20:27 ssplatt salt minion will spit a warning to set sha256 if it is not set to that.
20:28 XenophonF so one must explicitly set it to sha256 even though that's the default?
20:29 whytewolf must be much older. minions i have been upgrading since at least 2015.* have never thrown that error
20:29 XenophonF that's almost as annoying as the IPv6 slow grains warning
20:29 ssplatt it may not be set to the default. i thought they updated the default value
20:29 ssplatt at any rate, if you are seeing that warning you should explicitly set it.
20:31 whytewolf humm, maybe oldminions setup with bootstrap script. it used to set all the config options to default
20:31 whytewolf and if the default did change at some point
20:32 DammitJim oh, my minion doesn't have that set
20:33 DammitJim so, I guess the default is md5
20:33 whytewolf salt-call config.get hash_type
20:33 whytewolf that should tell you
20:33 whytewolf also how old is your minion
20:34 DammitJim weird
20:34 DammitJim I wonder why the minion log was throwing that
20:38 gtmanfred ssplatt: no problem, if the guy with the yum pr doesn't get it fixed by tomorrow morning, I am going to add a patch onto it to fix the comments, and merge that one and do another release
20:43 mpanetta joined #salt
20:56 Hybrid joined #salt
21:00 darioleidi joined #salt
21:11 _aeris_ joined #salt
21:33 blueelvis joined #salt
21:37 cro joined #salt
21:39 keltim joined #salt
21:42 cro joined #salt
21:45 Hybrid joined #salt
21:47 censorshipwreck joined #salt
21:48 darioleidi joined #salt
22:01 cro joined #salt
22:03 blueelvis joined #salt
22:10 hemebond viq: Puppet is not as open as Salt
22:10 hemebond viq: None of the Salt docs are specific to a paid version of Salt that isn't yet available to the general public.
22:17 fredricK joined #salt
22:19 bigjazzsound joined #salt
22:20 cyborg-one joined #salt
22:22 J0hnSteel joined #salt
22:25 fredricK so getting To repair this issue, delete the public key for this minion on the Salt Master and restart this minion. But salt-key shows the minion is not know
22:25 fredricK Any idea how to fix?
22:26 hemebond ?
22:27 cro joined #salt
22:29 fredricK Sorry have minion that will not startup.  Verfied it is not on the salt-master. via salt-key and it is not in /etc/salt/pki/master as a known minion.
22:30 hemebond Okay, what does the minion say?
22:30 hemebond If you stop the salt-minion service and run it manually in the foreground what does it say?
22:30 fredricK [CRITICAL] The Salt Master has rejected this minion's public key!
22:30 keldwud joined #salt
22:30 hemebond What does `salt-key --list-all` say?
22:30 hemebond Have you checked that it's connecting to the correct master?
22:31 fredricK Yes verified the correct master, verified it is not in the salt-key listall
22:31 hemebond Are the master and minion using the same hash type?
22:32 fredricK should be it configured itself from salt originally and as nothing version wise has changed.
22:32 hemebond So master and minion are the same version? Confirmed?
22:33 fredricK yes
22:33 hemebond What does the master log say? Anything?
22:33 hemebond If you watch the master event bus does it show the minion trying to connect?
22:33 fredricK Nothing for since it did not recognize a sls from it.
22:34 hemebond "recognize a sls"?
22:34 fredricK yes started when it was not recognizing a new state I added for it for new user group.
22:35 fredricK restarted the minion and now it will not accept or recognize the key.
22:35 hemebond Tried reinstalling the minion?
22:37 Ni3mm4nd joined #salt
22:41 sh123124213 joined #salt
22:43 fredricK Not yet since it is 2016.3.6
22:48 fredricK Same result with reinstall of minion
22:49 hemebond Then you need to run the minion and master with debug logging and check the output.
22:49 hemebond Seems very odd.
22:49 hemebond Have you deleted the master and minion keys from the minion?
22:50 fredricK I deleted the /etc/salt/pki directory and /var/cache/salt before reinstalling on minion
22:51 hemebond And it recreated the files?
22:51 fredricK https://gist.github.com/anonymous/4417885139954345a11f319b0aaa4ae8  Debug info from minion.  Master debug did not see it try
22:52 fredricK It did
22:52 https_GK1wmSU joined #salt
22:52 hemebond What is the value of hash_type on the master?
22:53 hemebond Certainly looks like the minion key is still on the master.
22:53 hemebond How did you delete the key from the master?
22:53 hemebond Have you tried restarting the master?
22:53 fredricK Ahh found it with a salt-call grains.items it thought it was a different host name
22:53 https_GK1wmSU left #salt
22:54 hemebond ????
22:55 fredricK Thanks got me thinking outside the box
22:59 J0hnSteel joined #salt
23:22 lkolstad joined #salt
23:29 lkolstad joined #salt
23:30 ninjada joined #salt
23:30 rpb joined #salt
23:38 Ni3mm4nd joined #salt
23:44 zerocoolback joined #salt
23:50 xMopxShell Does anyone have a strong opinion on *how* static data should be to be put in grains vs salt mine?
23:59 usernkey joined #salt

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