Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2018-01-28

| 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:00 alexlist joined #salt
00:26 jas02 joined #salt
00:36 darix left #salt
00:37 evle joined #salt
00:43 sh123124213 joined #salt
00:55 stanchan joined #salt
01:27 jas02 joined #salt
02:04 nomeeed joined #salt
02:08 jas02 joined #salt
02:23 shiranaihito joined #salt
02:57 ilbot3 joined #salt
02:57 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
03:39 jas02 joined #salt
04:17 stanchan joined #salt
04:18 jas02 joined #salt
04:40 stduolc joined #salt
05:01 jas02 joined #salt
05:42 MajObviousman joined #salt
05:43 jas02 joined #salt
05:45 chesty joined #salt
05:47 aneeshusa joined #salt
06:07 chesty joined #salt
06:19 jas02 joined #salt
06:34 saltslackbridge <leo> Tryind to get the script to create some users (http://russell.ballestrini.net/understanding-salt-stack-user-and-group-management/) via salt-ssh but running this state:  salt-ssh machine123 state.sls common.users  machine123:  Summary for machine123 ----------- Succeeded: 0 Failed:   0 ----------- Total states run:    0 Total run time:  0.000 ms  Can't seem to see any pillars via salt-ssh  salt-ssh machine123 pillar.show --refresh machine123:
06:34 saltslackbridge ----------     retcode:         0     stderr:         'pillar.show' is not available.     stdout:  Any pointers ??? Thanks a lot in advance!
07:02 saltslackbridge <leo> OK - ignore - missed entry in top.sls pillar .....
07:03 sh123124213 joined #salt
07:05 evle joined #salt
07:15 jas02 joined #salt
07:20 stanchan joined #salt
07:24 jas02 joined #salt
07:47 justanotheruser joined #salt
07:52 aldevar joined #salt
08:03 jas02 joined #salt
08:11 saltslackbridge <leo> Still can't get users created on Ubuntu 16.04 hosts.  There seems to be an issue from the past that was similar: https://github.com/saltstack/salt/issues/7690  Function: user.present   Result: False  Comment: The following requisites were not found:                              require:                                  group: sudo   Any pointers? Cheers, Leo
08:14 jas02 joined #salt
08:21 pualj joined #salt
08:22 stanchan joined #salt
08:31 pualj_ joined #salt
08:31 MTecknology Stick what you have now in a gist or on dpaste.com
08:32 jas02 joined #salt
08:36 pilatii joined #salt
08:46 sh123124213 joined #salt
08:56 _KaszpiR_ joined #salt
09:00 shoogz joined #salt
09:01 JAuz joined #salt
09:03 k1412 joined #salt
09:04 JawnAuz__ joined #salt
09:05 niluje joined #salt
09:08 jas02 joined #salt
09:14 zulutango joined #salt
09:23 _xor joined #salt
09:24 saltslackbridge <leo> https://gist.github.com/leogaggl/9198889ea9d78c03b9cbe976d08bec84
09:24 saltslackbridge <leo> File uploaded https://saltstackcommunity.slack.com/files/U8NKMEMA9/F8Z8HRW01/users.sls / undefined
09:29 saltslackbridge <leo> Corresponding pillar: https://gist.github.com/leogaggl/26c8c015012d9a68d36564c2a1316977
09:29 saltslackbridge <leo> File uploaded https://saltstackcommunity.slack.com/files/U8NKMEMA9/F8ZQP402E/users.sls / undefined
09:31 MTecknology I see nothing in here that defines a sudo group.
09:42 aldevar joined #salt
09:45 jas02 joined #salt
09:48 zerocoolback joined #salt
09:50 saltslackbridge <leo> groups:    - sudo   in the pillar file
10:00 pbandark joined #salt
10:05 MTecknology that's only for a requisite, not for a state
10:15 saltslackbridge <leo> Function: user.present       Result: False      Comment: The following requisites were not found:                                  require:                                      group: sudo      Changes:
10:15 saltslackbridge <leo> However the groups sudo is (as a default group on Ubuntu) present
10:15 xet7 joined #salt
10:15 saltslackbridge <leo> Which does not make any sense
10:16 MTecknology https://docs.saltstack.com/en/latest/ref/states/requisites.html
10:24 jas02 joined #salt
10:25 zerocoolback joined #salt
10:26 zerocoolback joined #salt
10:26 zerocoolback joined #salt
10:27 zerocoolback joined #salt
10:28 zerocoolback joined #salt
10:40 viq leo: requisites are for *states*. The fact that there's a function named the same as a category of object (group), and that object is already present on the system, does not mean you can refer the object directly.
10:43 saltslackbridge <leo> Thx for the help guys! Will check....
10:47 JAuz joined #salt
11:00 jas02 joined #salt
11:02 saltslackbridge <leo> Trying to implement this: http://russell.ballestrini.net/understanding-salt-stack-user-and-group-management/  I can't see what I got wrong. The requisite is being set in the state (with the data ie. sudo group) being passed from the pillar.   Been a long day. Might have to get some sleep....
11:02 el1356 joined #salt
11:03 saltslackbridge <leo> The error message I get when running the state:  The following requisites were not found:                                 require:                                     group: sudo
11:12 JawnAuz__ joined #salt
11:19 justanotheruser joined #salt
11:48 jas02 joined #salt
12:16 Trauma joined #salt
12:31 jas02 joined #salt
12:49 justan0theruser joined #salt
12:54 justanotheruser joined #salt
12:59 yidhra joined #salt
13:03 jas02_ joined #salt
13:06 yidhra joined #salt
13:08 sol7 joined #salt
13:24 oida joined #salt
13:32 XenophonF leo: in that require, "sudo" is a state ID and "group" is a state module
13:32 jas02 joined #salt
13:32 XenophonF so in your SLS file, if you don't have any group states with an ID of sudo, the require will fail with the message above
13:33 XenophonF that could be a `sudo: group.present: []` state or it could be a `sudo: group.absent: []` state or something else
13:34 XenophonF also, those saltstackcommunity.slack.com links don't work for those of us on IRC
13:37 gmoro_ joined #salt
14:19 jas02 joined #salt
14:32 zerocoolback joined #salt
14:33 c4rc4s joined #salt
14:38 tiwula joined #salt
14:49 mikecmpbll joined #salt
14:52 dendazen joined #salt
15:01 jas02 joined #salt
15:37 taylorbyte joined #salt
15:38 taylorbyte if i use   file.line   to add a line to the end of a file and i apply the state more than once will it add the line twice?
15:41 jas02 joined #salt
15:50 pbandark1 joined #salt
16:02 zerocoolback joined #salt
16:02 zerocoolback joined #salt
16:04 Aleks3Y joined #salt
16:24 jas02 joined #salt
16:24 Grauwolf joined #salt
16:28 Grauwolf hi! when setting roles in /etc/salt/minion via grains.roles[], the host can choose what roles it belongs to. this is not very desirable in some of my setups. any ideas?
16:42 MTecknology taylorbyte: usually file.managed is the better/safer option. file.line shouldn't re-add the same line, but will add new lines if you change what you're adding.  (It has no logic to replace the old added line)
16:46 taylorbyte MTecknology: ok thanks
16:46 MTecknology Grauwolf: 1) I usually find that using "roles" almost always leads to a messy/convoluted and difficult to debug setup. Partly evidenced by the problem you're running into now. You can resolve that one by making the "roles" a pillar value instead of a grain.
16:46 justan0theruser joined #salt
16:49 Grauwolf MTecknology: yes i thought as much. coming from puppet and ansible i'm used to the role model. its very hard to find salt resources for setups bigger than a few hosts
16:49 Grauwolf MTecknology: thanks
16:59 justanotheruser joined #salt
17:04 jas02 joined #salt
17:06 ipsecguy Hi, I am looking for a method for a connected salt-minion to check that the master ist there and responding. Similar to the test.ping from the salt-master to the minions but the active part on the minion side.
17:07 ipsecguy Trying to write a cron job to restart the minion in case the master is not responding. The minions run in unstable network environments.
17:08 dmaphy salt-call test.ping?`
17:11 ipsecguy salt-call test.ping circumvents the network part, i.e. it results in true, even if the salt-minion process is not running
17:16 dendazen joined #salt
17:37 jas02 joined #salt
17:53 * mirko is confused - do i now need to register on the webpage to review the package repositories?
18:21 jas02 joined #salt
18:47 Lionel_Debroux_ joined #salt
18:58 jas02 joined #salt
19:39 jas02 joined #salt
20:04 cswang joined #salt
20:09 stanchan joined #salt
20:13 jas02 joined #salt
20:16 stanchan joined #salt
20:23 Trauma joined #salt
20:33 jas02 joined #salt
20:39 ahrs joined #salt
20:39 jas02 joined #salt
20:51 viq ipsecguy: a dirty workaround that just came to my mind - salt minion fires event, master has reactor that touches file, cron restarts minion if file is older than X. Other than that, there are some 'ping' settings available in minion config
21:07 Hybrid joined #salt
21:08 stanchan joined #salt
21:21 cyteen_ joined #salt
21:42 whytewolf mirko, you shouldn't need to login to browse the repo. what link are you using?
21:47 tiwula joined #salt
21:51 RandyT joined #salt
21:51 RandyT joined #salt
21:54 aldevar left #salt
22:04 cswang joined #salt
22:08 jle joined #salt
22:25 stanchan joined #salt
22:29 MTecknology ipsecguy: test.ping can actually get you what you want. If you do 'salt-call test.ping' from the minion, and it can't authenticate to a master, it'll get an auth timeout and won't return True.
22:31 MTecknology stewgoin: Please, stop with the spammy nick changes.  ( http://sackheads.org/~bnaylor/spew/away_msgs.html )
22:46 viq MTecknology: though AFAIK salt-call effectively spawns a new minion, that won't help you figure out whether the one already running is communicating with master
22:49 MTecknology I'd imagine there's a pretty good chance that if the spawned minion can't connect, the other process probably isn't chatting either.
22:51 viq Not necessarily - firewalls that silently drop sessions that didn't send any packets for 5 minutes, for example. Both sides thing that session is open, but communications won't work. New session will work just fine.
22:51 viq s/thing/think/
22:51 jle master_keep_alive ftw
22:51 RandyT joined #salt
22:51 RandyT joined #salt
22:51 MTecknology pretty good chance vs. guaranteed
22:54 viq jle: https://docs.saltstack.com/en/latest/ref/configuration/minion.html doesn't list it
22:55 jle ops.. master_alive_interval sorry
22:55 viq I was told that's for multimaster
22:56 jle probably the reason why they implemented it, but it still works for single master
22:57 viq Ah, good to know that it does work, they made it sound like it didn't.
22:57 viq and with that I'm off, g'night
22:58 jle good night
22:59 cswang joined #salt
23:13 mirko whytewolf: i always end up on https://saltstack.com/saltstack-downloads/
23:16 saltslackbridge <whytewolf> Repo.saltstack.com
23:17 tiwula joined #salt
23:30 stewgoin MTecknology: Sorry about that... wonder why it's doing that...
23:32 aviau joined #salt
23:35 MTecknology stewgoin: could be a loaded plugin. Very much appreciate you fixing it, thanks! :)
23:35 stewgoin Yeah, must be something in znc that got goofed :/
23:38 MTecknology blame systemd! :D
23:38 tiwula joined #salt
23:43 stewgoin Now you are speaking my language
23:51 cswang joined #salt

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