Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-12-13

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

All times shown according to UTC.

Time Nick Message
00:00 saltslackbridge joined #salt
00:04 Manor joined #salt
00:09 saltslackbridge <james> Uhm, do outputters respect the order states were done in?
00:10 saltslackbridge <james> I know there's a `__run_num__` key
00:10 saltslackbridge <james> but do I have t manually sort by that?
00:17 pipps joined #salt
00:22 zerocoo__ joined #salt
00:24 threwahway_ joined #salt
00:28 Nahual joined #salt
00:30 dlloyd thats the only way i found
00:31 dlloyd and it was a horrible jq string to sort it
00:40 pipps joined #salt
00:41 hemebond Does env_order matter when using merge?
00:42 mvensky joined #salt
00:43 kettlewell joined #salt
00:45 zerocoo__ joined #salt
01:02 rem5 joined #salt
01:08 chutzpah joined #salt
01:12 pipps joined #salt
01:22 pipps joined #salt
01:36 jcrites joined #salt
01:42 Manor joined #salt
01:42 cyteen_ joined #salt
01:45 rem5 joined #salt
01:53 oida joined #salt
02:05 san joined #salt
02:07 penguincoder joined #salt
02:13 zerocoo__ joined #salt
02:14 penguincoder joined #salt
02:15 penguincoder Heya. Got a few questions I hope someone can help with.
02:16 penguincoder I have read the docs, and setup a salt master and minion for testing. Salt minion connects to and talks fine to the salt master.
02:16 penguincoder salt-mater -l debug shows communication, and SOME playbooks are being run fine
02:17 penguincoder however, I'm trying to get the salt-minion to run a playbook on connect (or start, I guess). I have tried configuring this in a few places. In /etc/salt/minion, I have set startup_states: highstate
02:17 hemebond "playbooks" wrong program :-)
02:17 penguincoder I see the salt-master log showing that the minion authenticated and ran the top.sls
02:18 penguincoder :P yeah... I know it's not a 'playbook' but...
02:18 penguincoder thing is, it's not actually running the top.sls :(
02:18 hemebond highstate
02:18 hemebond You will need to paste the relevant information somewhere.
02:18 penguincoder if I do a salt-call state.apply, everything applies properly.
02:18 penguincoder but I want it to be automatic.
02:19 pipps joined #salt
02:20 penguincoder lemme pull config real quic, would appreciate the help. Been beating my head for a few. Reading docs, and still doesn't work
02:23 Manor joined #salt
02:27 masber joined #salt
02:29 penguincoder okay
02:29 aidin joined #salt
02:30 penguincoder so the deal is, I have a salt-master configured. I have a kickstart file, setting up a server (ks-test) for now.
02:30 penguincoder https://oasis.sandstorm.io/shared/nOL7kPvtEAyXaNX8KVYTEWGdzg68MLys0C0WBSP6ATH
02:30 penguincoder snippet of the salt config for each, that I BELIEVE should have the salt-minion running the top.sls
02:30 penguincoder kickstart goes fine
02:30 penguincoder salt-minion connets, says it's running the job
02:30 penguincoder but it never runs the full job
02:31 penguincoder restarting the ks-test server, when salt-minion reconnects, runs a job, it updates.
02:31 penguincoder but still doesn't do everything
02:31 penguincoder running a salt-run state.apply from the minion, everything gets applied as expected.
02:32 penguincoder no other changes. So, what gives? how come the initial highstate, and reactor.sls doesn't get applied until I manually run state.apply?
02:32 penguincoder the scheduled task to check for salt updates every min, I don't see hitting the logs in salt-master -l debug, either
02:33 penguincoder I see the salt-call state.apply in those logs though
02:36 penguincoder it seems like the salt-minion service doesn't properly apply portion of the config. It applies part of it... for some reason, but then a salt '*' test.ping shows the salt-minion as not connected.
02:36 penguincoder restarting the salt-minion service picks it back up
02:37 penguincoder but why does salt-minion stop or crash after applying a portion of the configuration
02:39 threwahway joined #salt
02:57 threwahway joined #salt
02:59 ilbot3 joined #salt
02:59 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, and https://saltstackcommunity.herokuapp.com (for slack) <+> We are volunteers and may not have immediate answers
02:59 hemebond Okay. You have to restart the master after changing any part of the master config.
03:00 penguincoder restarted master, and salt-key -d the test server
03:00 hemebond Can you see the start event coming through? Anything in the master log when it does?
03:00 penguincoder gotta let the KS run
03:00 hemebond okay (I don't know what that is)
03:00 penguincoder sorry, Kickstart. CentOS/RHEL automated install
03:01 penguincoder trying to combine the two (though not reliant on each other) to automate my server setups
03:01 penguincoder KS works fine
03:01 penguincoder server is setup with packages, disk config, etc as expected. I have it installing salt-minion, setting up iptables rules
03:01 penguincoder restarting the salt-minion service, etc
03:02 penguincoder the salt-minion/config is weird
03:02 penguincoder to me :P
03:02 penguincoder I have it setting up sshd, but it (config) doesn't take, even though I tell it to watch sshd_config file
03:02 penguincoder and restart
03:02 penguincoder and it (Salt) doesn't install my SSH key
03:02 penguincoder but it creates my user
03:05 penguincoder still waiting for KS to finish. This will be a 'brand new' server setup for the salt-minion
03:05 penguincoder salt-master is the already configured server
03:10 evle joined #salt
03:12 hemebond What do you mean by "watch sshd_config file"?
03:12 hemebond Salt can't watch files, only states.
03:12 penguincoder okay, kickstart finished.
03:12 penguincoder salt-minion checked in
03:12 penguincoder tail -f /var/log/salt/master on the salt-master shows
03:12 penguincoder auth request
03:12 penguincoder auth accepted
03:13 penguincoder Got return from ks-test for job <numbers>
03:13 penguincoder two times
03:13 hemebond btw, restarting the minion service also sends a `start` event.
03:13 penguincoder which is good, because that should pick up my reactor to run the top.sls right?
03:14 penguincoder so here's the issue
03:14 penguincoder from salt-master
03:14 penguincoder # salt '*' test.ping
03:14 penguincoder ks-test.domain.com:
03:14 penguincoder True
03:14 penguincoder saltstack.domain.com:
03:14 penguincoder True
03:14 penguincoder y
03:14 penguincoder ping test is good
03:14 penguincoder salt config SHOULD setup ssh key, and sshd_config
03:14 onlyanegg joined #salt
03:16 hemebond Can you see it running highstate in the event log?
03:17 penguincoder how do I determine that
03:18 hemebond When you watch the event bus
03:18 hemebond You should be able to see new jobs and the return data.
03:18 pipps joined #salt
03:19 penguincoder [INFO    ] Authentication request from ks-test.domain
03:19 penguincoder [INFO    ] Authentication accepted from ks-test.domain
03:19 penguincoder [INFO    ] User sudo_chris Published command state.highstate with jid 20171213031123875515
03:19 penguincoder [INFO    ] Authentication request from saltstack.domain
03:19 penguincoder [INFO    ] Authentication accepted from saltstack.domain
03:19 penguincoder [INFO    ] Got return from ks-test.domain for job 20171213031123875515
03:19 penguincoder [INFO    ] Got return from ks-test.domain for job 20171213031129693865
03:19 penguincoder [INFO    ] MWorkerQueue under PID 1384 is closing
03:19 penguincoder That's what I saw, when it ran
03:19 penguincoder so I'd assume that connected
03:19 penguincoder and ran the states
03:20 penguincoder howeve, the state that says 'ssh config, save auth keys, and restart
03:20 penguincoder did NOT get applied
03:20 penguincoder my user is created
03:20 MTecknology holy crap...
03:20 penguincoder but no authorized_keys
03:20 penguincoder and I can't ssh as my user
03:20 MTecknology penguincoder: you're really spamming the channel hard.
03:20 penguincoder so I don't know what I'm doing wrong.
03:21 penguincoder MTecknology it was pretty dead before I got here :) and really just looking for help. If that's not what the channel is for I'll bail
03:21 hemebond Wait, so it's running the highstate but your SSH states are not applying?
03:21 MTecknology penguincoder: Use a pastebin for blobs of copy/paste stuff you want to share and try to keep at least a couple of your thoughts to a line. You can ask for help, but lrn2irc.
03:21 hemebond That's a different issue.
03:21 hemebond Sounds like your states are at fault there.
03:22 hemebond I still have that Etherpad thing open so add info to that.
03:22 penguincoder I don't like pastebin.
03:22 MTecknology doesn't matter if you do or not, use it
03:23 penguincoder hemebond, if the states were erroring, I could understand there being an issue. But, when I run the salt state.apply on minion, everythign runs, changes are made/applied
03:23 akar joined #salt
03:25 hemebond Then you need to watch the event bus.
03:25 hemebond https://salt.readthedocs.io/en/stable/ref/runners/all/salt.runners.state.html#salt.runners.state.event
03:25 hemebond Do "# Watch the event bus forever in a shell while-loop."
03:25 hemebond Then restart the salt-minion service.
03:26 penguincoder hemebond: etherpad demo expired, does this work? https://hackmd.io/CwMwHARgbATAxgTgLRgCaoIZOAZmAUyQRGiQFYQB2YM1YSM4DIA=#
03:26 hemebond I'm on there now.
03:26 penguincoder don't want to piss Mtecknology off more with my basic ass questions less he have a coniption fit
03:27 hemebond All output should go to something outside of IRC.
03:27 hemebond So paste it all into that page for me.
03:27 MTecknology well, I thought about trying to read the backlog and figure out what's up, but that killed my interest. Good luck.
03:27 hemebond Watch the event bus for the start event and paste what you see in the event output.
03:29 akar_ joined #salt
03:30 penguincoder MTechknology, would still appreciate you looking at w/e and the advice/help. That's why I am here. I didn't see anything wrong with posting the short 4 line message from a log output, but I see that you do find offense to that, so I'm changing it up. Didn't the the snark of 'lrn2irc', if that's going to be your attitude.
03:32 penguincoder hemebond, if I'm reading that CLI example correctly, I need to run the salt-run with state.apply ? If I do that though, the highstate is applied properly from master -> mminion
03:33 hemebond No
03:33 hemebond You run it exactly as shown.
03:33 hemebond On the master.
03:33 hemebond Then restart salt-minion (on the minion) and you will see lots of output from that salt-run
03:33 hemebond You're doing the "# Watch the event bus forever in a shell while-loop." part, nothing else.
03:33 akar joined #salt
03:34 penguincoder right
03:34 penguincoder lmao, no jq.. lemme install that
03:37 penguincoder so, all of that runs, pretty colour ouput after changing to -C instead of -color-output
03:37 penguincoder after restart salt-minion, on minion, and jq output
03:37 penguincoder SSH key is in place, I can connect, and FW rules are correct. Everything was applied as expected
03:38 hemebond They weren't immediately before restarting the minion?
03:38 MTecknology There's about three pages of scrollback. Is there a tl;dr version of the problem at hand?
03:38 hemebond MTecknology: Trying to get highstate to work on start event.
03:39 hemebond penguincoder: Is the problem with the highstate not running when the minion is completely new?
03:39 hemebond If restarting the minion doesn't work, is there some other part not working?
03:39 MTecknology using the reactor then?
03:39 hemebond (maybe this kickstart thing?)
03:39 hemebond MTecknology: Yes
03:40 hemebond Seems to be working.
03:40 penguincoder hemebond, the ssh-key and fw rules were not proper before salt-minion restart
03:40 penguincoder MKtechkonlogy, I am trying to have salt-minions connect to master, and pull top.sls (and run) on first connect/auth
03:40 hemebond Okay, have you checked the minion log (/var/log/salt/minion) for errors?
03:41 MTecknology penguincoder: If you type "mt<tab>" you'll start getting my nick correct. ;P
03:41 penguincoder it is not working, either using reactor, or startup_states: highstate
03:41 penguincoder I don't care which method makes it work, I just want ONE to work without having to manually go login as root, and restart the salt-minion
03:41 penguincoder sorry MTecknology, thank you.
03:42 penguincoder habit of typing out tech :)
03:43 penguincoder the only errors in minion
03:43 penguincoder are warnings, minion recieved a SIGTERM
03:43 penguincoder which is me killing the daemon, and running in salt-minion -l debug
03:44 MTecknology man.. none of my reactors are sane or pretty... they're almost all from when the reactor was new
03:44 penguincoder ahh, one other error which souldn't affect this, 'stderrL no crontab for root'
03:44 MTecknology Wanna pbin the reactor portion of your master config as well as the reactor sls?
03:44 penguincoder so you'd advise not using reactor for start states?
03:45 hemebond penguincoder: So is the problem when you're using kickstart to create the minion?
03:45 penguincoder sure, I'll put it on that hackerpad link.
03:45 MTecknology that doesn't load without javascript so I won't be seeing it..
03:45 penguincoder ahh. okay. Anything else aside from pbin you can?
03:45 MTecknology dpaste.com is a preference of mine
03:45 penguincoder roger
03:47 penguincoder MTecknology: is that what you need - http://dpaste.com/3VXZK50
03:47 penguincoder hemebond: the kickstart is just setting the minion/master connection
03:48 penguincoder I'll paste the relevent portion
03:48 aidin joined #salt
03:48 MTecknology that's perfect
03:48 MTecknology s/local.state.highstate/cmd.state.highstate/
03:49 penguincoder hemebond: http://dpaste.com/28SMDQZ
03:49 penguincoder so replace local with cmd in the start.sls?
03:49 MTecknology yup
03:49 penguincoder ok, I got that line direct from salt docs.
03:50 hemebond I use local.state.apply
03:50 penguincoder can you paste me your local.state.apply hemebond? full stanza?
03:50 penguincoder going to try with MTecknology's advice, and run kickstart/salt again see if that pulls
03:50 hemebond penguincoder: Pasted into that hackmd thing.
03:51 penguincoder thanks
03:52 penguincoder okay removed minion key
03:53 penguincoder running kickstart, and listening to event bus on master.
03:53 MTecknology Here's some neutered snippets from a past life -- http://dpaste.com/2JPA263
03:55 penguincoder thanks, relevent section seems to be the commented out portion? for what i'm trying to do?
03:55 MTecknology yup
03:55 penguincoder can you elaborate or explain on why you commenented that out and went to the reactor version?
03:55 penguincoder is it more robust?
03:56 hemebond That is a reactor, no?
03:56 MTecknology ya, it is
03:56 hemebond The top part is the reactor.
03:56 hemebond The bottom is the master config.
03:56 MTecknology It turned out to be waaaay too much for 500 systems to reconnect and all kick off a highstate at the exact same time.
03:56 penguincoder ahh, okay. My confusion. Still new to salt. Coming from ansible
03:56 MTecknology especially when a single highstate on one could take >30 minutes
03:56 hemebond 500 at once? Cripes.
03:57 penguincoder yeah I don't have that many
03:57 penguincoder is salt better at scaling, iyo/
03:57 hemebond Mmmm, yes?
03:58 hemebond I'm not that familiar with Ansible. I know another part of my company has used it. But it's likely been abandoned now.
03:58 Manor joined #salt
03:58 MTecknology It used to not scale for crap in my set of edge cases, but that's all been fixed up now.
03:59 MTecknology I have ~200ish systems all in various remote facilities where I was given a throttled portion of a pair of T1's.
04:00 MTecknology had*
04:01 penguincoder Thanks for looking at configs, and the help thus far, MTecknology and hemebond. One of the reasons I still like IRC.
04:01 hemebond 👍
04:01 penguincoder waiting on post-install KS to finish up and will check event bus for salt
04:02 penguincoder if I can just get it to run through the tasks at checkin, I'll be happy, and live to fight another battle
04:04 MTecknology If this attempt doesn't work, I'd make a long running state (cmd.run: -name: "sleep 120"), restart the minion, watch the event bus, and also check /var/cache/salt/minion/proc/ on the minion and see if it pops up (in case you missed the event)
04:04 MTecknology That'd at least let you know for sure if it's a problem with the config setup or the deploy
04:05 sjorge joined #salt
04:05 MTecknology If nothing starts, then doing a fresh deploy each time is just wasting your time
04:06 penguincoder well I would appreciate the help in figuring out which it is
04:06 penguincoder redacting and posting the event bus in a moment
04:07 penguincoder but, user was created, ssh key not copied.
04:07 MTecknology that pile of stuff I just said is the best advice I can give for figuring out which ;)
04:08 hemebond penguincoder: If part of the highstate works, then you need to check the minion log to find out why.
04:08 hemebond And also check the highstate return.
04:08 penguincoder /var/log/salt/minion?
04:08 hemebond You can see the job ID (jid) in the event output
04:08 hemebond Yes
04:08 penguincoder aha, interesting.
04:09 penguincoder so after making MTecknology change for cmd.
04:09 penguincoder Failed to add the ssh key. Is the home directory available, and/or does the key file exist?
04:09 hemebond Have you pasted your states yet?
04:09 MTecknology yay! now it's just broken states :)
04:09 penguincoder which, yes I know what it's saying.
04:09 penguincoder but, if I have it creating the user
04:09 penguincoder AND adding the ssh key
04:09 MTecknology no.. not the enter thing again :(
04:09 penguincoder how does the home dir not exist?
04:09 hemebond But... are your SSH states dependent on your user states?
04:10 hemebond Or are your SSH states trying to run _before_ your user states?
04:10 penguincoder I don't know what that means in this context, so, probably not
04:10 hemebond https://docs.saltstack.com/en/latest/ref/states/requisites.html
04:10 penguincoder does the top.sls run in order of tasks?
04:11 MTecknology One of the things I'm going to mention in my next talk is that you *must* make sure that *all* states apply cleanly during first execution.   Deploy a fresh system, run a highstate, and *prove* that everything works perfect the *first* time.   You can't really do automation until you have that.
04:11 hemebond Nope.
04:11 hemebond top.sls just says "these state files should be included"
04:11 penguincoder ahh, so that might be the problem. I was under the assumption that the salt tasks ran procedueraly.
04:11 MTecknology everything except sls tends to fire top down, unless things manipulate the order. I tend to just always do explicit requisites
04:11 MTecknology except top.sls*
04:12 penguincoder this is a new error though, which means that MTecknology suggestion for cmd. vs local. did something
04:13 hemebond Not if your user was being created before.
04:13 penguincoder so the next issue is non procedural tasks in top.sls, which I need to fix by resuqietes.
04:13 hemebond (might also have been an issue though)
04:13 penguincoder if I tell the sshkeys: object that the resquite (sp, I know) needs to be the user is created first
04:13 penguincoder will it create the user, THEN do that task? or just bail on the task
04:14 hemebond It will do them in the order required, yes.
04:14 hemebond Requisites are used to order the states.
04:14 penguincoder cool. okay. Reading the doc for that now.
04:14 hemebond States are applied one at a time.
04:14 penguincoder unrelated question. Say you want your salt-minion to check in every so often to the master and update state
04:15 penguincoder what is salt best practice for that? Cron it out? or salt scheduler?
04:15 hemebond I would probably use salt scheduler.
04:16 MTecknology I've had enough issues with the salt scheduler that I maintain cron entries
04:16 hemebond Yeah, I use cron at the moment because of issues removing scheduled things.
04:16 hemebond But I thought they were better in 2017.
04:16 penguincoder okay :) cron it is!
04:16 penguincoder how often do you have it checking? I know it's env dependent, but is every hour too often?
04:17 hemebond I don't.
04:17 penguincoder so you maintain a push schedule only?
04:17 zerocoo__ joined #salt
04:17 hemebond I update when I want to, yeah.
04:17 MTecknology My issues is usually with things not running when I expect them to because something jammed.
04:17 hemebond I hated that part of Puppet.
04:17 penguincoder hmm. So reason I'm trying to learn salt and move from Ansible, is the push only aspect.
04:18 penguincoder I really want the minions/clients checking in and getting the approved system state often. Very often
04:18 beardedeagle joined #salt
04:18 penguincoder but I also know the limitations and issues of that, like messing up a config and having every client pull it down
04:19 MTecknology I have a highstate "timer" that I start when I push to certain git repos and when that hits X, it runs a global highstate. New git pushes can't effect that timer if 0 < timer <=X
04:19 hemebond For that I'd use a cron job and batching on the master.
04:19 penguincoder can you link or explain batching on the master? like salt-call -b 10% etc etc
04:19 penguincoder ?
04:19 MTecknology and just for good measure, a weekly global highstate, but I always expect zero changes from that
04:20 penguincoder hmm. So essentially weekly backups, and not a constant checkin
04:20 MTecknology backups?
04:20 hemebond MTecknology: I don't understand. Does the git push reset the timer?
04:20 penguincoder well, weekly incremental, 'check state, push to clients' ?
04:20 MTecknology hemebond: yup
04:20 hemebond And what is your timer reset to each time?
04:20 penguincoder vs 'client check, update self'
04:21 hemebond Is that just to give yourself time to reverse changes?
04:21 hemebond penguincoder: Easier to manage.
04:21 hemebond Works the same way.
04:21 hemebond Doing it from the master allows for batching.
04:21 MTecknology hemebond: git push -> if tick == 0 or tick >= 10: set tick = 15
04:22 MTecknology it's not actually those numbers, but something like that.. the numbers themselves are arbitrary preference
04:22 hemebond Oh, so not based around the Git refresh interval?
04:23 MTecknology git refresh?
04:23 hemebond The git remotes thing.
04:23 MTecknology OH! no..
04:23 hemebond I think it's 1 minute intervals.
04:23 penguincoder generic hopefully fully redacted salt-bus events - http://dpaste.com/3VWD9K5
04:23 MTecknology a git push on the git server on those repos will send an event up the bus for the reactor
04:23 penguincoder which shows the failed to create key, due to user homedir not created yet
04:24 MTecknology to* the git server
04:24 penguincoder which you've explained I need to look at resq's docs
04:24 hemebond penguincoder: Where are your states?
04:25 penguincoder I'm sorry, can you clarify that?
04:25 penguincoder only state I know of explicity, is highstate?
04:26 hemebond "enforcing" is a state
04:26 MTecknology hemebond: I got the impression he was reading requisite docs to work on the clean first highstate
04:26 penguincoder yes, selinux enforcing
04:26 hemebond MTecknology: Yeah, but I don't see any dependencies in the output they just pasted.
04:26 hemebond penguincoder: Right, we need to see those states.
04:26 hemebond To check your dependencies.
04:27 penguincoder so the *.sls files?
04:27 penguincoder that would be a salt state, correct?
04:27 hemebond Yes, states inside the sls files.
04:27 penguincoder hackmd link
04:28 hemebond I mean all of them :-)
04:28 penguincoder working on it
04:28 hemebond Okay.
04:28 hemebond Also, what is "confs"?
04:28 penguincoder config dir for states
04:28 MTecknology or... just read the docs and fiddle (learn) a little bit?
04:29 MTecknology penguincoder: The only requisite you likely need is -requires:
04:29 penguincoder Been fidling :) and trying
04:31 penguincoder hemebond: that's all the confs I have for salt, currently.
04:31 MTecknology debian is working on bringing in apparmor by default, and enforcing by default
04:32 hemebond Okay. I don't see any requirement to the user state.
04:32 tiwula joined #salt
04:32 hemebond Your sshkeys ssh_auth.present state needs to require the user state.
04:33 hemebond - user; user
04:33 penguincoder so in the ssh conf.sls, user: I need a requires, or in the sshkeys: ?
04:33 hemebond On the ssh_keys
04:33 penguincoder ssh_auth.present, - requires: user ?
04:33 hemebond (require_in lets you do it the other way around)
04:33 hemebond - user: user
04:34 hemebond - (module): (statename)
04:34 hemebond In your case, you have state "user" that uses the "user" module.
04:34 penguincoder hmm
04:34 MTecknology hemebond: c'mon
04:35 hemebond Oh, I just realised I could update the state myself.
04:36 penguincoder :P so in the sshkeys:, - require: user: user, where second user is username?
04:36 hemebond penguincoder: I'll update the hackmd to clarify
04:38 penguincoder I see.
04:38 MTecknology I've had people comment that because you can name the state pretty much anything, you should make it as descriptive as possible, to the point of sentences w/ spaces.  That makes it hard to use in a requisite.
04:38 GnuLxUsr joined #salt
04:39 hemebond Yeah, my states are like that.
04:39 penguincoder so I understand that, and I think I see what's going on now
04:39 penguincoder without the require, the ssh-key wasn't written
04:39 hemebond 👍
04:40 penguincoder but the user was created. so after logging on to console and running state.apply
04:40 penguincoder user dir existed, so key was created
04:40 penguincoder thus, to automate, I need to make sure that require is set so the key isn't attempted to be written before user home DIR is set
04:40 penguincoder and top.sls doesn't go in top down order :P ?
04:40 hemebond 👍
04:41 penguincoder time to rebuild and test
04:41 * MTecknology wonders was 01F44D is
04:41 hemebond MTecknology: Thumbs up :-)
04:42 MTecknology ah.. I suppose I could also have joogled it
04:42 MTecknology my stuff is fast... not pretty :P
04:43 hemebond
04:44 MTecknology most unicode stuff is fine, I just run on only a handful of font packages
04:45 penguincoder straight CLI?
04:46 MTecknology lemme smudge..
04:49 MTecknology https://ibin.co/3kVgUElPJJ9j.png
04:50 pewpew joined #salt
04:51 penguincoder shit, nice.
04:51 penguincoder lots of chans. I'm a weechat fan myself :P irssi was a little to complicated for me
04:51 DoomPatrol looks like a thumbs up to me
04:51 * DoomPatrol uses weechat
04:52 hemebond DoomPatrol: Yeah, depends on whether or not you have the fonts installed.
04:52 penguincoder MTecknology: some of your channels look appealing to my interest :P Nginx, debian...
04:53 MTecknology terminator can get /really/ fun... https://i.imgur.com/RFtd3hO.png
04:53 penguincoder hahha
04:54 penguincoder guake here :( works fine with tmux
04:54 DoomPatrol mmm, termite & tmux
04:54 penguincoder tmux is a must-have
04:54 MTecknology I use terminator and screen
04:54 penguincoder screen is so lacking though
04:54 MTecknology how so?
04:55 shripadr joined #salt
04:55 MTecknology actually, this is kinda OT and should probably be in #salt-offtopic
04:56 penguincoder pane re-org, commandlets, re-binding ctrl commands, window renaming, re-attach
04:56 penguincoder ahh. okay.
04:56 Manor joined #salt
05:07 penguincoder can anyone help me determine what this error message means? "The require statement in state 'sshkeys' in SLS 'ssh.keys' needs to be formed as a list
05:08 swa_work joined #salt
05:08 hemebond penguincoder: Put it in hackmd
05:09 MTecknology or dpaste!
05:09 onlyanegg joined #salt
05:10 MTecknology but we don't need it for that.. you forgot the - probably
05:10 MTecknology penguincoder: you familiar with python data structures?
05:10 penguincoder thanks hemebond: in hackmd
05:10 penguincoder yeah I'm familar with python
05:10 MTecknology http://yaml-online-parser.appspot.com/
05:11 hemebond ^ great site
05:12 MTecknology I've almost never used the python convert since json prints in a pretty way and is pretty much identical
05:14 penguincoder using that convertor, appears to be an issue in the 'keys' dict?
05:14 penguincoder but why
05:14 hemebond That hackmd isn't loading for me now.
05:15 threwahway_ joined #salt
05:16 Kax joined #salt
05:17 penguincoder sec
05:18 penguincoder hemebond: https://hackmd.io/CwMwHARgbATAxgTgLRgCaoIZOAZmAUyQRGiQFYQB2YM1YSM4DIA=?both ?
05:19 threwahway joined #salt
05:21 hemebond App isn't loading for me at all.
05:21 penguincoder damn
05:22 hemebond Will have to just use pastebin. But like MTecknology said, you're missing a hyphen somewhere.
05:22 hemebond Or maybe your indentation is broken.
05:22 hemebond It's a problem with your YAML.
05:22 penguincoder okay.
05:24 MTecknology "The require statement [...] needs to be formed as a list"
05:24 penguincoder just strange that it wouldn't work with the saltstate on reactor
05:24 MTecknology that's why I asked if you were familiar with the data structures. The converter shows you
05:24 penguincoder but works fine with the explicit salt apply.state
05:24 penguincoder the converter didn't show any issues?
05:24 hemebond pastebin your state.
05:25 hemebond The one mentioned in the error.
05:26 penguincoder hackrmd, full pub key and all. don't haxx me
05:27 MTecknology You're enjoying making sure I don't also look at it, eh?
05:27 penguincoder I don't trust you :D
05:27 penguincoder but I DID post the link like 500 lines ago
05:27 penguincoder https://hackmd.io/CwMwHARgbATAxgTgLRgCaoIZOAZmAUyQRGiQFYQB2YM1YSM4DIA=#
05:28 penguincoder does that work?
05:28 penguincoder bottom of the paste
05:28 * MTecknology sighs
05:28 hemebond No, it no longer loads for me.
05:28 penguincoder shit.
05:28 hemebond Use pastebin and everyone can see it
05:28 MTecknology ^ +1
05:28 hemebond The app itself is failing, not just your link.
05:28 MTecknology none of this javascript-required crap ;0
05:29 penguincoder ugh pastebin
05:29 MTecknology penguincoder: You said you're a power user! No javascript!
05:29 MTecknology Did you already forget dpaste?
05:29 penguincoder dpaste it is - http://dpaste.com/3YM1GGN
05:30 penguincoder I like the ones I can edit with new things
05:30 MTecknology http://dpaste.com/3YM1GGN#line-50  <-- This is the thing I was saying you should /not/ do
05:30 penguincoder and that ISN'T indexed by google
05:30 hemebond Should not.... use file.managed?
05:30 penguincoder hmm can you epxplain why not to use file.managed?
05:30 penguincoder that's in the docs as the approved method
05:30 MTecknology err.. 49*
05:30 hemebond I did that.
05:31 penguincoder right, okay, line 49 - previously you said the task can be anything, including names , words , spaces
05:31 penguincoder that fits?
05:31 hemebond To demonstrate the state references in dependencies.
05:31 MTecknology read the whole thing I said ;)
05:32 threwahway_ joined #salt
05:32 hemebond Right. You said people have done it and it causes problems.
05:32 penguincoder hmm " you should make it as descriptive as possible, to the point of sentences w/ spaces.  That makes it hard to use in a requisite"
05:32 penguincoder sentences w/ spaces?
05:32 penguincoder :P
05:32 penguincoder but then... to not
05:33 MTecknology 22:38 < MTecknology> I've had people comment that because you can name the state pretty much anything, you should make it as descriptive as possible, to the point of sentences w/ spaces.  That makes it hard to use in a requisite.
05:33 penguincoder so rename that crap is MTecknology suggestion
05:34 threwahway joined #salt
05:35 MTecknology Why am I seeing 4-space indents?
05:35 penguincoder ?? I hit the space bar four times for first level, and two spaces for second level?
05:35 MTecknology no
05:36 Manor joined #salt
05:36 * MTecknology hits the yaml parser, surprised that it worked at all
05:36 hemebond Yeah, everything parses. I don't see an issue with the require either.
05:36 penguincoder same damn error
05:36 penguincoder "The require statement in state 'sshkeys' in SLS 'ssh.keys' needs to be formed as a list"
05:37 hemebond Oh, that's different.
05:37 penguincoder but as soon as I restart the service, or salt state.apply
05:37 penguincoder it runs fine
05:37 penguincoder so what gives?
05:37 MTecknology apparently yaml is forgiving the first time you do that. That's surprising
05:37 hemebond MTecknology: Yeah, the indentation is per-block, which is gross.
05:38 MTecknology penguincoder: stick to two spaces, unless you run into a situation where you know you need four  (it's rare)
05:38 penguincoder so, right now I can't connect via SSH.
05:38 penguincoder but when I hit the minion, run a systemctl restart
05:38 penguincoder I can ssh fine
05:38 penguincoder (key is put in its place)
05:39 penguincoder you're saying if I fix indent to two spaces, it should work the first time?
05:39 penguincoder or am I missing somethign else that is confusing the crap out of me
05:39 hemebond It's at least good practice.
05:39 MTecknology I didn't say that... I said that it's a thing you shouldn't do
05:39 penguincoder :P
05:39 penguincoder just weird that I dont' have to change anything, except restarting the minion
05:39 penguincoder and it pulls the config
05:39 penguincoder why is it failing the initial pull
05:40 penguincoder I just want some consistiencey
05:40 hemebond You mean the first highstate?
05:40 hemebond It fails on the first highstate?
05:40 penguincoder the sshkeys: state
05:40 MTecknology penguincoder: before you press enter, wait 0.5 seconds. If you're already trying to append more to the same though, finish the though first, please.
05:40 penguincoder :(
05:40 MTecknology It's annoying to read something and have to stop because we're waiting for five more lines for the rest
05:41 penguincoder thought that was better than a five line wall of text
05:41 MTecknology the five line wall is what I'm complaining about.
05:41 hemebond Maybe try "pkg.installed: []" instead of letting it dangle.
05:41 penguincoder seems opposite of what you're saying, to continue typing instead of hitting enter ;)
05:42 MTecknology just continue typing, don't enter :)
05:42 penguincoder hemebond: pkg.installed [] on what section? and salt docs didn't explain well what the [] means... is that name expanding for the package/titular section?
05:42 MTecknology http://dpaste.com/3YM1GGN#line-25 <-- You don't need to force a list, but the : means more is coming.   pkg.installed: []  vs.  pkg.installed
05:43 hemebond Yeah, anywhere you just have "pkg.installed" by itself.
05:43 penguincoder hmm but it's not failing on that. the .tmux.conf is installed just fine
05:43 MTecknology Hah!
05:43 hemebond It's supposed to work without but... for reasons I've forgotten I always add the empty list now.
05:43 MTecknology Here's your break ->  http://dpaste.com/3YM1GGN#line-124
05:44 penguincoder can you explain?
05:44 hemebond lol, some non-breaking space character or something.
05:44 hemebond Or maybe a funky hyphen.
05:44 penguincoder ahh I see
05:44 MTecknology the former
05:45 penguincoder no space in the hypen
05:45 penguincoder *after
05:45 hemebond Retype, manually, lines 44 and 45
05:45 penguincoder okay I'll edit that and run KS + salt again, tough I expect it to fail again :P
05:45 penguincoder I have used the same editor (vim) for writing out the configs, manually.
05:46 MTecknology penguincoder: I gave you a bunch of tips. Did you fix things up and make it more readable?  If so, re-paste so we can start again from where you're at
05:47 penguincoder you did give a lot of tips and I appreciate it. Running through the *.sls now to trim leading spaces. Will paste to dpaste moment
05:47 MTecknology You don't need to start a fresh system, just "userdel -rf user" and it should break again
05:47 penguincoder on the minion? but that doesn't test the fresh ssystem pull.
05:47 penguincoder I already know it works with a salt-call state.apply.
05:47 MTecknology old salties can identify oopsies *MUCH* faster in a well-structured data file.  We're basically angry computers.
05:48 _beardedeagle joined #salt
05:50 MTecknology (well, I am anyway)
05:51 hemebond (lol... we didn't want to say anything)
05:52 penguincoder okay I've modified all *.sls to be indented two spaces each level
05:53 penguincoder user us deleted from minion
05:53 penguincoder so now.... run state.apply from master? or minion?
05:53 MTecknology I broke the bridge?
05:53 saltslackbridge joined #salt
05:53 penguincoder I would think run from minion
05:54 hemebond penguincoder: You can do. They work the same way.
05:54 hemebond salt-call might show you more output though.
05:55 Felgar joined #salt
05:56 penguincoder gotta re run in tmux. so re-kickstarting. on minion, salt-call state.apply first run 8 tasks ran, 1 failed. ran salt-call state.a--ply, and all tasks ran fine. no failiures
05:56 penguincoder can't scroll back so need to redo that in tmux so I can tell what's failing.
05:56 MTecknology penguincoder: oh... you weren't automatically in tmux? :(
05:56 penguincoder no :( just have .tmux.conf setup, not set as login
05:57 MTecknology setting it as a login shell sounds like a horrible idea...
05:57 penguincoder I agree
05:57 penguincoder too many possible failures.
05:57 MTecknology you could likely do the thing I mentioned in -ot ;)
05:57 penguincoder -ot ?
05:57 MTecknology #salt-offtopic
05:57 penguincoder oi,
05:58 MTecknology salt-call -l debug state.highstate
05:58 MTecknology also- https://michael.lustfield.net/linux/persistent-ssh
05:58 penguincoder all this crap for a semi-auomated install ... shit. maybe time to just sleep on it
05:59 MTecknology Did you repaste stuff? I was waiting for that before digging at it further
05:59 penguincoder well yeah, that's nice, but doesn't help when you factory reboot the system with a min-iso and ks= :P
05:59 penguincoder what files did you need/want to look at? just *.sls? or al
05:59 MTecknology just the states you're trying to run; nothing else should be needed
06:01 MTecknology and line 124 in that paste.. definitely make sure you get that fixed because that /should/ be a parse error
06:01 MTecknology and it's like.. exactly the cause of the previous error, verbatim
06:02 penguincoder here's everything I have for *.sls http://dpaste.com/1GGGGX1
06:02 onlyanegg joined #salt
06:03 MTecknology oh, that's prettier
06:03 penguincoder :)
06:03 hemebond server.sls is the same :-)
06:03 penguincoder running KS + salt on it now, IF the salt-minion checks in automatically and runs like I want it to
06:03 penguincoder same as in wrong?
06:04 penguincoder all that should be doing is installing openssh, and the sshd_config ?
06:04 hemebond 4-space indentation and pkg.installed without the ":[]"
06:04 penguincoder pkg.installed doesn't have the []. correct, but  it is two space indented. file.managed, two space, and the objects beneath it, two more
06:05 penguincoder is that incorrect?
06:05 MTecknology http://dpaste.com/1GGGGX1#line-18  s/: []//
06:06 hemebond Line 65 has four spaces
06:06 penguincoder yes for tmux, so that needs to be the same openssh-server
06:06 hemebond It doesn't really affect the parsing.
06:06 penguincoder ahh shit.
06:06 MTecknology the rest looks good
06:07 penguincoder I need a yaml linter. shit
06:07 MTecknology oh, and line 9 shouldn't ever match anything, but that's a different thing for later
06:07 MTecknology that online parser /is/ my linter
06:07 penguincoder it would. I have a grain set for the saltstack server
06:07 penguincoder it's lxc role
06:07 penguincoder which I don't have selinux enabled on
06:08 penguincoder so don't want it failing out on enabling that on other servers
06:08 MTecknology it doesn't match.. but don't worry about that now
06:08 hemebond Oh yeah, line 9 won't work
06:08 penguincoder but it does? :( okay. fixing spacing
06:08 hemebond confd.selinux applies?
06:08 MTecknology the spacing also won't break anything.. it's just pedantics
06:09 penguincoder before I put in that 'not p@' role, the saltstack master (lxc) was failing on enabling selinux
06:09 penguincoder with that rule, it doesn't fail on the lxc container
06:09 MTecknology don't worry about it now
06:09 MTecknology (because it doesn't match, and applies to nothing)
06:09 MTecknology based on what I see here, I would expect things to work
06:09 penguincoder what should I worry about now then? you're saying the spacing doesn't matter, but it obviously does?
06:10 MTecknology you're trying now, ya?
06:10 sjorge joined #salt
06:10 penguincoder fixing sshd: spacing , yes
06:12 MTecknology strictly personal preference, but I *VERY* strongly suggest avoid using "roles". Absolutely especially if they come from grains, but even from pillar.  It's a server concept that I abhor.
06:13 penguincoder I would appreciate you explaining that further. What do you mean? How else would you apply certain rules to subsets of systems?
06:13 penguincoder also, just ran the KS, which checked the minion into the master
06:13 penguincoder user wasn't created
06:13 penguincoder thus ssh-key wasn't created
06:13 penguincoder :( wtf
06:14 penguincoder how the hell
06:14 MTecknology what's the highstate output?
06:14 penguincoder sparse as shit
06:14 MTecknology meaning?  I need data
06:15 MTecknology fyi- I'm gonna go pop a sleeping pill since it's after midnight. I'll probably crash in about an hour.
06:15 penguincoder http://dpaste.com/0G6QZCJ
06:15 penguincoder yeah I'm heading out soon, this shit is frustating as fuck and about to just go back to ansible. at leastit works.
06:16 MTecknology that's not highstate return
06:16 hemebond Well, you've kinda skipped a few of the basics.
06:16 penguincoder so why didn't highstate run then?
06:17 penguincoder I ran through the salt docs tutorials. from how to make the base system, setup master/minion, and supposedly how to get the top.sls to run when a minion checks in
06:17 MTecknology Like I said before... it would be better if you started by making sure you can run a clean state.highstate from a fresh install
06:18 MTecknology you're already trying to automate something that doesn't work in the first place
06:18 penguincoder I have been doing that each time. Fresh Kickstart, fresh install, running the state.apply on the minion.
06:18 MTecknology then show me the highstate return
06:18 MTecknology I don't care about what events I see
06:18 MTecknology you* see
06:19 penguincoder okay, hemebond was interested in that command output for events
06:19 penguincoder what do you want to see for highstate return?
06:19 MTecknology for a completely different issue
06:19 MTecknology I want to see the highstate return, all of it
06:19 MTecknology what broke? what error?
06:19 hemebond penguincoder: Are you running highstate manually or relying on the reactor?
06:19 penguincoder again, running salt apply.state works from the minion for all states/roles
06:19 MTecknology ah...
06:19 penguincoder why didn't it run when start/authed
06:20 MTecknology "you're already trying to automate something that doesn't work in the first place
06:20 penguincoder I WANT it to run automatically
06:20 penguincoder it DOES work MTecknology
06:20 MTecknology crap, grabbed a newline..
06:20 penguincoder when I apply it manually
06:20 penguincoder manually works
06:20 MTecknology prove it
06:21 MTecknology Remove the reactor, deploy a fresh system, add it to salt, and run "salt-call state.highstate" and paste that output.
06:21 penguincoder remove the reactor, okay. remove all reactor files from the master. Then run salt-call state.highstate on the minion ?
06:21 penguincoder and you want logs/output from.... ?? /var/log/salt/master ? /var/log/salt/minion ?
06:22 MTecknology no... there was more in between those two things
06:22 MTecknology and I don't need logs
06:23 penguincoder rm: remove regular file '/etc/salt/master.d/reactor.conf'? y
06:23 MTecknology well that would just cause your master to get cheesed off at you
06:23 penguincoder # systemctl restart salt-master
06:23 MTecknology you have reactor config pointing at the removed file
06:24 penguincoder rm: remove regular file '/srv/salt/reactor/start.sls'? y
06:24 penguincoder there is no reactor file, listener, etc on the salt-master
06:24 * MTecknology blinks
06:24 penguincoder removed them , see above. Anywhere else reactor should be removed?
06:24 MTecknology hemebond: ^ you're up!
06:25 hemebond penguincoder: Can you `salt minion state.apply` from the master and pastebin the result?
06:25 MTecknology eh..
06:25 MTecknology penguincoder: Where else did you configure reactor stuff?
06:25 penguincoder those are the only files I configured reactor stuff in, according to the salt docs
06:26 MTecknology ooooooh... shit, that's my bad
06:26 MTecknology nevermind!
06:26 penguincoder deleted now... soooo
06:26 penguincoder only other things I have set in KS for it,....
06:26 MTecknology yup, that, restart the master process, and deploy a fresh clean system
06:26 hemebond That's fine. We can put that back once the highstate is 100%.
06:27 penguincoder http://dpaste.com/1A1NH73
06:27 MTecknology penguincoder: I saw /srv/salt, and not /etc/salt/master.d/
06:27 penguincoder kickstart salt config.
06:27 penguincoder /srv/salt is the base configs?
06:27 MTecknology noo... no scheduled highstate
06:27 MTecknology and no roles either
06:27 hemebond You can remove the startup_states and schedule parts for now. COmment them out.
06:28 penguincoder :/ well WTF then?
06:28 hemebond We want to do things manually for now.
06:28 MTecknology make things work ... and THEN add more automation to it
06:28 penguincoder but that's not the point. I want the servers to grab their configs when they're kickstarted and provision
06:28 MTecknology you're trying to fit fifty shades of puzzle together instead of a couple pieces at a time
06:29 penguincoder removing the roles and schedule, but that means /etc/salt/minion is default.
06:29 hemebond penguincoder: That's fine, but first the highstate needs to be 100% first.
06:29 hemebond (I said first twice, my bad)
06:29 penguincoder leave startup_states in that?
06:29 MTecknology NO!
06:29 hemebond Comment out.
06:29 penguincoder ........
06:29 MTecknology penguincoder: just comment out lines 4-15
06:30 penguincoder then explain how the minion will get config from master without intervention
06:30 hemebond We will manually tell it to highstate.
06:30 hemebond So we can watch it.
06:30 MTecknology penguincoder: You're choosing to make this a very complicated thing out of the gate
06:30 hemebond Then, when highstate works 100% manually, we can automate the highstate.
06:30 MTecknology ^ that
06:31 penguincoder I don't want it to be complicated. I want it to be useful, and to work how I had expected based off research and docs. Minion pulls configs from masters based on config
06:31 MTecknology also- line 3  ... don't edit the default minion config.  It's 100% comments for a really amazing reason
06:31 penguincoder however, Commented out everything except master: <ip> in the config
06:31 hemebond penguincoder: It will, we'll get there.
06:32 MTecknology lemme help
06:32 MTecknology http://dpaste.com/3ZXWKQH
06:32 penguincoder /etc/salt/minion now reads http://dpaste.com/3FJF8MF
06:33 MTecknology err... no, not that
06:33 MTecknology http://dpaste.com/1G75ESR
06:33 MTecknology penguincoder: ^ start with this
06:34 penguincoder can you explain why minion.d/master.conf vs /etc/salt/minion?
06:34 penguincoder that's not explained in the salt docs
06:34 hemebond It's the same.
06:34 MTecknology sort of.. not the same when it comes updates time
06:35 hemebond minion.d is like the Debian way to override configs.
06:35 MTecknology Is it debian-centric?
06:35 Manor joined #salt
06:35 hemebond I thought so. I don't think it's exclusive to Debian but I thought it started with them.
06:36 penguincoder running on CentOS 7
06:36 penguincoder and trying to standarizez on that
06:36 penguincoder so is minion.d/master.conf still the correct location?
06:36 MTecknology standardize on using .d directories for configs when possible
06:36 MTecknology yes
06:37 penguincoder and I swear I'm not trying to be all newbish to you guys. I'm a long time Linux sysadmin and I know my way around the CLI. Ive been trying to get salt working how I expect for the past week after redaing docs and tutoorials
06:37 penguincoder haven't gotten it, so it's why I'm here, asking for help.
06:37 MTecknology use the KS I provided, and spin up a system with it.
06:37 MTecknology Let us know when you've approved the salt key and stop there
06:37 hemebond penguincoder: It can take a while for the basics to click. That's why it's best to start with really simple stuff.
06:38 hemebond Took me a long time to grok the module.function structure in YAML.
06:38 MTecknology I started back in the 0.12 days :P
06:39 hemebond Yikes.
06:39 MTecknology penguincoder: c'mon! hurry up! I'm excited!
06:40 MTecknology We gonna squash this mofo!
06:40 penguincoder I started in slackware in 98
06:40 penguincoder sooooo not a greybeard, but  still.
06:40 penguincoder Commented out the items I specified, changing auto accept to no (for now, since I Was testing) deleted ks-test key.
06:40 penguincoder anything else before I KS it off?
06:41 MTecknology I have a multi-colored beard.. a few greys, mostly black, some red, some silver, some other colors
06:41 MTecknology penguincoder: Nope! c'mon! My debugger is itchy!
06:41 penguincoder ok old man :D
06:41 MTecknology almost 30...
06:44 penguincoder kickstart running package install
06:46 threwahway_ joined #salt
06:49 threwahway joined #salt
06:52 MTecknology is it there yet?
06:52 onlyanegg joined #salt
06:52 LocaMocha joined #salt
06:55 penguincoder it's booting
06:55 MTecknology already?!
06:55 MTecknology :P
06:55 penguincoder :D fast as lighting. So, root prompt now. hitting master to accept key
06:56 MTecknology well... nobody ever accused rhel of being fast
06:56 penguincoder after accepting key, what do you want me to watch?
06:56 penguincoder master log? event bus? something else?
06:56 hemebond Nope, all manual from here on out.
06:56 MTecknology on the minion, run "salt-call state.highstate"  and pbin the output
06:57 MTecknology (all output)
06:58 penguincoder one failure, for my tmux.conf. Due to the user not existing yet.
06:58 penguincoder so that'll need a requires user
06:59 penguincoder http://dpaste.com/3B3FE9H
07:00 MTecknology Fix that cause and then 1) repeat everything you did  2) make sure your second highstate makes *ZERO* additional changes
07:01 hemebond The user is called "user"?
07:01 MTecknology also- noted that the crontab gone dun booped up
07:01 MTecknology note*
07:01 dcrouch joined #salt
07:02 MTecknology hemebond: I'm wanting to assume he just did a find/replace/all
07:02 penguincoder the crontab is commeneted out because I was under the impression that the salt schedular was better to use
07:02 penguincoder and no, the user is not 'user' :P
07:02 penguincoder %s/user/realname/g
07:03 penguincoder when you say fix that, I don't see any changes inthat link.
07:03 penguincoder what did you mean to fix?
07:04 MTecknology there was a failure in a state
07:04 penguincoder for crontab, yes. But shouldn't salt create the crontab file??
07:04 penguincoder if I have to create it manually again, what's the point of salt automation?
07:04 MTecknology Before you attempt *ANY* automation, you need to make sure that 1) state.highstate completes with *ZERO* issues and 2) the second highstate applies *ZERO* changes
07:05 pualj joined #salt
07:05 penguincoder user is not available. Means the user is not created yet. but it's the root damn user, how is it not created yet?
07:05 MTecknology I only see "user" and "user" != "root"
07:06 penguincoder root is created by default. I can login as root at the install phase
07:06 penguincoder prior to running any salt command
07:06 penguincoder root is there, and has a PW, a home dir, a crontab, cron is installed
07:06 penguincoder why does salt not recognize it?
07:06 penguincoder that's the problem.
07:07 penguincoder how do you think I logged in to run the salt-call command
07:07 MTecknology again with the enter spam?
07:07 zerocoo__ joined #salt
07:08 MTecknology penguincoder: did you read line 2 of that output? or the Comment in the failed state?
07:08 MTecknology Fix that.
07:08 LocaMocha joined #salt
07:09 MTecknology At this point, you really shouldn't need help knowing what to do.
07:09 MTecknology (not for that failure)
07:09 penguincoder I can read, thanks. The user exist, as I can login with said user, and run commands as said user.
07:09 * MTecknology sighs
07:10 MTecknology You claim you can read... but you seem to be ignoring the failure.
07:10 MTecknology Why did it fail?
07:11 MTecknology You've already run into (and solved) this problem in a different state. Why is it happening now?.. what happened before what?
07:12 penguincoder it claims the user does not exist.
07:12 MTecknology I want you to actually understand without telling you exactly what lines to edit and how.
07:12 MTecknology it claims... no... It SAYS
07:12 MTecknology penguincoder: try this... run the highstate again and see what changes
07:12 penguincoder I say claims. because later down that same output, IT CREATES THE DAMN SSH KEY.
07:12 penguincoder how can the user not exist
07:13 MTecknology don't paste the output because I know what it'll say
07:13 penguincoder when it creates the key
07:13 penguincoder for the user
07:16 MTecknology Why does it make sure the ssh key was created?... you've been through this
07:16 penguincoder reading the configs now, and docs. I see what it needs, and said this before, it needs the require statment for user
07:17 hemebond Yip. MTecknology wants you to fix that and run the same highstate command and paste the new output
07:17 MTecknology Fix that, deploy a new system, and then make sure a highstate completes
07:17 penguincoder naw, he doesn't want the new output, he knows what it'll say. faield: 0
07:18 MTecknology no...
07:18 penguincoder rebuilding KS system, removing current key, and running salt highstate on it for output.
07:18 MTecknology If you rerun the highstate, you'll have one changed state
07:18 penguincoder can I paste two lines here?
07:18 MTecknology no
07:18 penguincoder :(
07:18 MTecknology but you can probably stick it in here using a single line
07:19 MTecknology ..and that changed state will be because it now has the requisites in place to run itseld
07:19 akar joined #salt
07:20 penguincoder thank you for the help, and patience.
07:21 MTecknology hemebond: Did someone call me patient?... I feel like something is out of place.
07:22 felskrone joined #salt
07:22 Ricardo1000 joined #salt
07:23 hemebond lol, penguincoder is being terribly polite with you MTecknology
07:23 hemebond They themselves have an amazing amount of patience imo
07:26 LocaMocha joined #salt
07:26 akar any comment.. why we need more speed bus in salt.. rather than relying on ssh conn?
07:26 hemebond akar: What?
07:28 akar saltstack use MQ right?
07:28 akar messaging queue
07:28 hemebond ZeroMQ, yes, or a new TCP protocol.
07:30 MTecknology or raet!!
07:30 akar new tcp protocol? ... what that
07:30 akar why saltstack use ZeroMQ... and when we need to use it
07:31 akar or every single command was send through ZeroMQ?
07:31 hemebond Everything goes over ZeroMQ
07:31 hemebond Unless you change to a different protocol, e.g., TCP
07:32 hemebond (TCP is the name of the protocol, not talking about the regular TCP)
07:32 hemebond Or raet, yes :-D
07:32 hemebond (but don't)
07:32 MTecknology penguincoder: So... when you get your first highstate completing, and subsequent highstates produce zero changes, *THEN* you can start thinking about additional automation.   In your case, the only thing you need is to re-introduce that reactor.
07:33 MTecknology nah, raet got dropped to the wayside because issues with 0mq were cleaned up, as well as other security things.
07:34 MTecknology Unless you know you need something else, it's usually best to stick with 0mq
07:36 penguincoder MTecknology: rebuilt sys, accepted ks-test key. Testing from minion, the command is... salt-minion state.apply ?
07:36 penguincoder no, highstate... so state.highstate ?
07:37 penguincoder salt-call state.highstate. okay.
07:37 hemebond It's `state.apply` now.
07:37 penguincoder ....
07:38 hemebond `state.apply` is equal to `state.highstate`
07:38 penguincoder salt-call state.apply on minion? that'll do the highstate check?
07:38 hemebond yip
07:38 penguincoder shit's confusing yo :P
07:38 hemebond It changed to be simpler and more consistent
07:39 LocaMocha joined #salt
07:39 MTecknology I don't like state.apply
07:39 penguincoder salt-call state.apply on minion returns succeeded 9, failed 0.
07:39 penguincoder So that's good..!!!
07:39 MTecknology penguincoder: now re-introduce your reactor and try again
07:39 penguincoder ssh-key connect worked.
07:39 MTecknology see... one piece at a time- makes things way easier to debug
07:40 penguincoder :( I removed the reactors. So now to recreate them.
07:40 MTecknology I was gonna go to sleep, but now I really want a burrito. :S
07:40 penguincoder pizzzzzaaaa
07:40 hemebond A burrito before bed? That's not going to be good :-D
07:41 penguincoder I got a working state for now, so Gonna leave it alone before I Spend the next 10 hours fixing the next piece.
07:41 penguincoder again, thanks for the help.
07:41 MTecknology my chemo stuff requires a high-protein diet so things like that are totally allowed. :D
07:41 MTecknology penguincoder: nah... you should just drop the reactor in place and try again
07:41 penguincoder I already forgot those :P Need to look at docs again.
07:42 hemebond You wrote it in chat :-)
07:42 penguincoder don't make me scroll shit...
07:42 MTecknology and I shared my own
07:42 MTecknology oooh... too many lines?  is too many lines a problem?
07:43 penguincoder MTecknology can tell you I'm bad at lines
07:43 hemebond LOL, alright MTecknology :-D
07:43 MTecknology :D
07:43 MTecknology that was pretty awesome, actually
07:46 Elsmorian joined #salt
07:48 MTecknology btw- /lastlog would probably help with that :)
07:48 hemebond What does that do?
07:49 aldevar joined #salt
07:50 MTecknology search backlog for things
07:50 hemebond psh, CTRL+F :-) y'all should use Pidgin
07:51 MTecknology pidgin for IRC? .. I actually feel sad for you.
07:51 penguincoder CTRL+r FTW
07:52 penguincoder pidgin is awesome for a lot of things
07:52 penguincoder IRC is not one of them
07:58 yuhl joined #salt
07:59 toanju joined #salt
08:00 DanyC joined #salt
08:00 Elsmorian joined #salt
08:00 yuhl joined #salt
08:04 MTecknology penguincoder: did you try the reactor?
08:06 penguincoder MTecknology: Trying it now
08:07 penguincoder but it didn't work? (as expected)
08:07 MTecknology why was that expected?
08:07 penguincoder minion key accepted, no errors in event log/bus.
08:07 penguincoder but I ssh to the test minion asks for password
08:07 hemebond Do you see the start event coming through?
08:07 penguincoder (it shouldn't, as my salt config says disable password only accept pub key)
08:08 MTecknology after the key is accepted, the minion should re-attempt auth is <= 10 sec, and the reactor should trigger the highstate
08:08 MTecknology in*
08:08 penguincoder I see salt/auth, minion/refresh and minion_start events
08:08 penguincoder says my pub key was pushed
08:08 penguincoder and result: true
08:08 saltslackbridge <james> Is there any way to get more info about what `salt` was called with within a module or outputter?
08:09 penguincoder so by all accounts, it should be ready to login with pubkey, but its not.
08:09 saltslackbridge <james> I'm trying to make my outputter support all the different return types, but it's difficult having to parse all of the different return types. Just wondered if I could simplify it by saying `if foo == 'state'`
08:10 Manor joined #salt
08:13 penguincoder weird, it looks like the reactor didn't run any states??
08:13 penguincoder http://dpaste.com/20SXBWC ( sorry for multiple enters MTecknology )
08:13 hemebond Did you restart the master after putting the reactor config back?
08:13 penguincoder yeah. before I did KS
08:14 hemebond Need to check your reactor config. Paste it if you want.
08:14 MTecknology try the long-running state thing so that you can check /var to actually see the highstate running.
08:14 MTecknology or paste the reactor stuff for verification
08:15 Manor_ joined #salt
08:15 penguincoder from minion, salt-call state.apply, all changes succeeded. Will post reactor moment
08:16 penguincoder except, trying to reconnect as my user and not root, it still asks for PW. it's not restarting the sshd service afer updating config
08:16 penguincoder that's annoying
08:19 MTecknology An extremely downvoted comment on imgur was "ilovelobbying.com" and a reply was "I'm surpriesd this doesn't exist yet" ... So I went ahead and created it. :P
08:20 penguincoder MTecknology, hemebond : http://dpaste.com/3H3JCRE
08:20 penguincoder reactor configs I think is all that's needed. salt-master was restarted
08:21 hemebond And you definitely restarted the master?
08:21 penguincoder looks like the salt-minion didn't pick up the configs though, nothing ran on minion. But it did check in
08:21 hemebond Anything in the master log?
08:21 penguincoder pretty damn sure I did. removed the key and restarted.
08:22 penguincoder that's interesting. master logs says the file doesn't exist
08:22 * MTecknology groans at the continued use of state.apply, especially in a reacotr
08:22 penguincoder :D pretty sure I used cmd?
08:22 hemebond MTecknology: What you got against state.apply?
08:22 MTecknology too crashing to care, g'night
08:23 penguincoder k. G'night.  Thanks again.
08:23 hemebond good night
08:23 Elsmorian joined #salt
08:23 MTecknology penguincoder: tomorrow you can ask me about my opinion of "roles" and that invalid top.sls target
08:24 Hybrid1 joined #salt
08:29 Manor joined #salt
08:36 hammer065 joined #salt
08:37 chowmeined joined #salt
08:43 robman joined #salt
08:48 pualj joined #salt
08:53 onlyanegg joined #salt
08:55 Kax joined #salt
08:56 sybix joined #salt
09:09 seano joined #salt
09:14 seano joined #salt
09:17 seano joined #salt
09:22 seano joined #salt
09:24 seano joined #salt
09:27 _KaszpiR_ joined #salt
09:32 seano joined #salt
09:34 aidin joined #salt
09:36 dcrouch joined #salt
09:38 seano joined #salt
09:52 zerocoo__ joined #salt
09:52 GrisKo joined #salt
09:56 seano joined #salt
10:00 Mattch joined #salt
10:30 aidin joined #salt
10:32 seano joined #salt
10:54 onlyanegg joined #salt
11:03 akar left #salt
11:05 Yuras_ joined #salt
11:08 GrisKo joined #salt
11:13 permalac joined #salt
11:15 evle joined #salt
11:17 sol7 joined #salt
11:18 mikecmpbll joined #salt
11:28 pbandark joined #salt
11:56 aidin joined #salt
12:08 losh joined #salt
12:27 kettlewell joined #salt
12:29 netcho_ joined #salt
12:33 masuberu joined #salt
12:39 jespada joined #salt
12:39 jespada joined #salt
12:46 usernkey joined #salt
12:47 oida joined #salt
12:52 zerocoo__ joined #salt
12:52 zerocoo__ joined #salt
12:53 sol7 joined #salt
12:55 onlyanegg joined #salt
12:59 J0hnSteel joined #salt
13:01 aidin joined #salt
13:01 jeremytiki joined #salt
13:08 Manor_ joined #salt
13:10 shripadr joined #salt
13:12 Manor joined #salt
13:26 dhwt joined #salt
13:30 cgiroua joined #salt
13:41 felskrone joined #salt
13:51 edrocks joined #salt
13:54 aidin joined #salt
14:00 numkem joined #salt
14:10 Romero joined #salt
14:13 robman joined #salt
14:17 gh34 joined #salt
14:20 megamaced joined #salt
14:40 onlyanegg joined #salt
14:40 mchlumsky joined #salt
14:46 oida joined #salt
14:46 jeremytiki joined #salt
14:54 aidin joined #salt
15:02 racooper joined #salt
15:06 ouemt joined #salt
15:07 KaczuH joined #salt
15:10 onlyanegg joined #salt
15:11 jdipierro joined #salt
15:13 aphor joined #salt
15:18 numkem joined #salt
15:20 shripadr_ joined #salt
15:24 darix joined #salt
15:25 numkem joined #salt
15:27 user-and-abuser joined #salt
15:28 _JZ_ joined #salt
15:35 ikarpov joined #salt
15:36 wevanscfi joined #salt
15:37 onlyanegg joined #salt
15:42 aneeshusa joined #salt
15:43 aneeshusa left #salt
15:45 om2 joined #salt
15:45 aidin joined #salt
15:47 heaje joined #salt
15:53 Manor joined #salt
15:53 cico joined #salt
15:59 shripadr joined #salt
16:00 Manor joined #salt
16:04 cgiroua joined #salt
16:05 nixjdm joined #salt
16:11 XenophonF joined #salt
16:12 aldevar left #salt
16:14 edrocks joined #salt
16:25 aldevar joined #salt
16:26 Heartsbane joined #salt
16:26 Heartsbane joined #salt
16:27 jeremytiki joined #salt
16:31 _JZ_ joined #salt
16:41 tiwula joined #salt
16:44 DammitJim joined #salt
16:45 alker joined #salt
16:46 aidin joined #salt
16:48 penguincoder joined #salt
16:50 deuscapturus joined #salt
16:51 heaje Is there a way to determine if a salt state exists?  Like state.exists (I know this doesn't work) or something?
16:52 pbandark1 joined #salt
16:52 heaje My use case is that I'm looping through a pillar and adding states based on pillar data.
16:52 lordcirth_work heaje, I suspect that's not the best way to get what you want (XY problem) what is the end goal?
16:53 heaje lordcirth_work: The end goal is that based on pillar data that specifies state names, I will include those states.  If the state doesn't exist, I want to do something else.
16:54 lordcirth_work Including the same state twice is a no-op, isn't it?
16:54 heaje This is specifically for a state the has something like 100 possible plugins.  Some of those plugins have custom states (xxxx.plugin_name), whereas others don't.
16:55 heaje In the case of those that don't, I want to just run a file.managed.  If there is a custom state for the plugin, I want to execute that state.
16:55 penguincoder joined #salt
16:55 penguincoder join #salt-offtopic
16:55 alker joined #salt
16:56 heaje This helps me avoid creating 75 or so custom states that all do the exact same thing...
16:56 heaje I guess the other option is that I just maintain a list of plugins that don't have custom states and ignore adding those to the include.
16:57 alker joined #salt
16:57 saltslackbridge <gtmanfred> you can list all the states using `cp.list_master` and iterating over it
16:57 edrocks joined #salt
16:58 saltslackbridge <gtmanfred> that will list all the files in the fileserver though
16:58 alker joined #salt
16:58 saltslackbridge <gtmanfred> There is a `cp.cache_file` function that will return false if the file does not exist on the salt master fileserver https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.cp.html#salt.modules.cp.cache_file
16:59 saltslackbridge <gtmanfred> there isn’t directly cp.file_exists, but i don’t see a reason it couldn’t be added pretty quickly
16:59 deuscapturus joined #salt
17:02 lordcirth_work Is there likely to be a Salt major release soon?
17:02 gtmanfred how soon is soon?
17:03 lordcirth_work A month or two?
17:03 lordcirth_work Why would a pkgrepo.absent return False when the repo doesn't exist?
17:04 gtmanfred maybe
17:04 gtmanfred i refuse to hard commit on when our expected date is right now
17:04 lordcirth_work Hmm, both the absent and present refer to the same sources.list.d file, that's probably what triggers the bug
17:19 deuscapturus left #salt
17:19 socket- joined #salt
17:19 deuscapturus joined #salt
17:21 gtmanfred lordcirth_work: fyi, we just made a releases channel on the saltstack community slack to move all our talk about releases to be more public
17:21 gtmanfred move all of our internal talk (except CVEs)
17:22 socket- Hey all, I have a top file like this: https://apaste.info/EHAi and when a new resources comes online it does all the states defined in the ipcidr match, but not tha states defined in the grain match.  However, if I do salt -S 10.0.0.1/8 state.apply it applies all the states in both ipcidr, and grains.  Am i running into some sort of timing issue, like the top file being processed before the minion
17:22 socket- determines grains?
17:22 babilen gtmanfred: So you guys use Slack internally?
17:22 gtmanfred yes
17:23 babilen No wonder the bridge appeared
17:25 alker joined #salt
17:27 saltslackbridge joined #salt
17:40 wongster80 joined #salt
17:48 jdipierro joined #salt
17:49 cgiroua joined #salt
17:50 zerocoo__ joined #salt
17:51 mkoskar joined #salt
17:51 vexati0n anyone else having a problem with reg module/state hanging forever on Windows 10 ?
17:52 aidin joined #salt
17:53 edrocks joined #salt
17:56 pipps joined #salt
18:00 Deliant joined #salt
18:01 saltslackbridge joined #salt
18:10 g3cko_ joined #salt
18:15 jasperla is there a way to only run a single test file instead of having to fireup the entire testsuite?
18:15 scbunn joined #salt
18:15 scbunn joined #salt
18:16 saltslackbridge <gtmanfred> you can specify the test name with -n, so like -n unit.modules.test_docker
18:16 lordcirth_work gtmanfred, cool thanks
18:17 pipps joined #salt
18:22 CampusD joined #salt
18:28 losh joined #salt
18:30 zerocoo__ joined #salt
18:50 jasperla gtmanfred, thanks!
18:51 aidin joined #salt
18:57 skinkitten joined #salt
18:57 pipps joined #salt
18:58 Nazca joined #salt
19:04 numkem joined #salt
19:05 pseudonymous joined #salt
19:09 dhwt joined #salt
19:11 om2 joined #salt
19:20 dhwt joined #salt
19:22 ymasson joined #salt
19:28 _KaszpiR_ joined #salt
19:29 dhwt joined #salt
19:35 toanju joined #salt
19:40 Hybrid1 joined #salt
19:40 jeremytiki joined #salt
19:41 kettlewell joined #salt
19:42 dhwt joined #salt
19:42 lastjedi joined #salt
19:44 pbandark1 joined #salt
19:45 dhwt joined #salt
19:47 aidin joined #salt
19:51 dhwt joined #salt
19:54 oida joined #salt
19:55 pipps joined #salt
19:56 dhwt joined #salt
19:56 pppingme joined #salt
19:57 Hybrid1 joined #salt
20:01 onlyanegg joined #salt
20:03 dhwt joined #salt
20:04 pipps joined #salt
20:05 saltslackbridge joined #salt
20:06 saltslackbridge joined #salt
20:07 saltslackbridge joined #salt
20:07 saltslackbridge joined #salt
20:08 pipps joined #salt
20:09 MTecknology and to break the bridge one last time... :(
20:09 saltslackbridge joined #salt
20:10 dhwt joined #salt
20:14 cgiroua joined #salt
20:19 pipps joined #salt
20:20 netcho joined #salt
20:20 netcho joined #salt
20:36 jeremytiki joined #salt
20:41 MTecknology penguincoder: Did you figure out the kickstart thing?
20:43 ksa joined #salt
20:43 saltsa joined #salt
20:43 coldbrewedbrew joined #salt
20:43 coldbrewedbrew joined #salt
20:43 utahcon_ joined #salt
20:43 frots joined #salt
20:43 zach_ joined #salt
20:43 q1x joined #salt
20:43 vexati0n joined #salt
20:44 dmaphy joined #salt
20:44 mauli joined #salt
20:44 revellion joined #salt
20:44 farcaller joined #salt
20:44 coldbrewedbrew_ joined #salt
20:46 ipmb Is there a graceful way to handle minions that are only connected periodically?
20:48 shortdudey123 joined #salt
20:49 Kax joined #salt
20:50 saltslackbridge joined #salt
20:53 MTecknology ipmb: I have a separate salt master I use for endpoints, which are devices that only connect long enough to run a highstate.
20:58 pipps joined #salt
20:59 numkem joined #salt
21:02 dhwt joined #salt
21:04 evilet joined #salt
21:06 pipps joined #salt
21:13 pipps joined #salt
21:17 niluje joined #salt
21:17 darix joined #salt
21:38 saltslackbridge joined #salt
21:48 beardedeagle joined #salt
21:49 aldevar joined #salt
22:01 Manor joined #salt
22:08 saltslackbridge <vedr> how do i get bridge working?
22:09 netcho oh it's working
22:10 saltslackbridge <vedr> there we go
22:11 aidin joined #salt
22:11 saltslackbridge <vedr> test
22:12 netcho joined #salt
22:12 netcho joined #salt
22:12 saltslackbridge <vedr> test2, sorry for spam
22:13 pipps joined #salt
22:13 penguincoder Heya, me again. I'm working on trying to get a salt reactor firing on minion/start. http://dpaste.com/1CK5K2F
22:14 penguincoder That link is to some configuration files I have for the reactor. Unfortunately, the reactor doesn't fire. I have confirmed that a salt state.apply when called from the minion, succeeds without errors though.
22:14 penguincoder Anyone able to help me toubleshoot why the reactor isn't firing as I expect?
22:14 ahrs joined #salt
22:14 dcrouch joined #salt
22:15 saltslackbridge <vedr> try ```reactor_highstate:   local.state.highstate:       - tgt: {{ data['id'] }}```
22:16 saltslackbridge <gtmanfred> netcho, don’t send multiline comments to this channel, they do not convert well to irc
22:16 saltslackbridge <gtmanfred> use gist
22:16 saltslackbridge <vedr> ok sorry
22:17 saltslackbridge <vedr> why does bridge use firs 4 letters of my name instead of display name?
22:17 hemebond There is/was a bug with using state.highstate in a reactor.
22:18 saltslackbridge <vedr> works for me since i started using salt
22:18 saltslackbridge <vedr> never had issues
22:18 saltslackbridge <vedr> maybe i skipped buggy versions? :slightly_smiling_face:
22:18 saltslackbridge <gtmanfred> it should be fixed in 2017.7.2
22:19 hemebond 👍
22:19 saltslackbridge <gtmanfred> well, i am not sure
22:19 saltslackbridge <gtmanfred> which bug were you talking about?
22:19 penguincoder So what should I use instead of state.highstate? I am on the lastest version 2017.7.2
22:19 saltslackbridge <gtmanfred> if it was just the one about args and kwargs, that is fixed in 2017.7.2
22:19 penguincoder Changed that stanza, restarted salt-master and restarted salt-minion on minion. I see the minion start on bus, but the reactor still doesn't fire - http://dpaste.com/0NX23EC
22:19 saltslackbridge <gtmanfred> state.apply is the same as state.highstate if you don’t pass any other arguments to it
22:20 saltslackbridge <gtmanfred> so, your reactor config is wrong
22:20 saltslackbridge <gtmanfred> you don’t name those config options
22:20 saltslackbridge <vedr> uh yea
22:20 saltslackbridge <vedr> line 55
22:20 saltslackbridge <gtmanfred> penguincoder https://gist.github.com/gtmanfred/78be915e397f7f6fae16f0d82cb65240
22:20 saltslackbridge <gtmanfred> File uploaded https://saltstackcommunity.slack.com/files/U7KH2HJ0K/F8ED9G1MJ/gistfile1.txt / undefined
22:23 netcho gtmanfred: how come i get wron handle from your bot? :P
22:24 saltslackbridge <vedr> and yours seems fine :S
22:24 saltslackbridge <gtmanfred> change your slack login username
22:25 penguincoder ahh, damnit. Alright thanks gtmanfred, fixing that to jsut reactor: made it fire.
22:25 saltslackbridge <vedr> it's changed
22:26 saltslackbridge <gtmanfred> no it isn’t
22:26 tom[] what write permissions does salt-run need? /var/log/salt/master  anything else?
22:26 saltslackbridge <gtmanfred> you probably signed up with an email that is vedr@something.com
22:27 netcho vedr@nlebo.com yea
22:27 tom[] running salt-run from systemd service limits it
22:27 saltslackbridge <gtmanfred> go to your account info, and change the login username
22:27 saltslackbridge <gtmanfred> not the display name
22:27 saltslackbridge <gtmanfred> and not in your profile
22:28 saltslackbridge <netcho> aaa
22:28 saltslackbridge <netcho> thanks
22:44 pipps joined #salt
22:48 aneeshusa joined #salt
22:52 aneeshusa left #salt
22:52 aidin joined #salt
22:58 gomerus[m]1 joined #salt
22:58 hackel joined #salt
22:58 tom29739 joined #salt
23:02 deuscapturus joined #salt
23:02 tikedbus joined #salt
23:15 dxiri joined #salt
23:25 onlyanegg joined #salt
23:31 tikedbus joined #salt
23:31 onlyanegg joined #salt
23:47 zerocoo__ joined #salt
23:50 pipps joined #salt
23:52 pipps99 joined #salt
23:54 sjorge joined #salt

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