Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2018-04-12

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

All times shown according to UTC.

Time Nick Message
00:00 onslack joined #salt
00:16 dendazen joined #salt
00:20 gforgx joined #salt
00:30 Hybrid joined #salt
00:49 hemebond joined #salt
01:01 noobiedubie joined #salt
01:02 bltmiller joined #salt
01:10 evle2 joined #salt
01:16 Whissi joined #salt
01:30 mechleg1 joined #salt
01:30 mechleg1 left #salt
01:31 Bryson joined #salt
01:56 ilbot3 joined #salt
01:56 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2017.7.5, 2018.3.0 <+> 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
01:58 Whissi joined #salt
02:08 zerocoolback joined #salt
02:16 tiwula joined #salt
02:24 zerocool_ joined #salt
02:36 shiranaihito joined #salt
02:42 eekrano joined #salt
04:06 Miuku_ left #salt
04:07 Miuku joined #salt
04:42 evle1 joined #salt
05:08 JacobsLadd3r joined #salt
05:10 sauvin joined #salt
05:20 lompik joined #salt
05:29 DanyC joined #salt
05:43 DanyC joined #salt
06:00 greatgatsby joined #salt
06:02 jkaberg joined #salt
06:02 jkaberg has anyone solved "templating the template" with pillar? eg defining something somewhere (in pillar), and then accessing it an other place in pillar?
06:04 hemebond jkaberg: I just use Jinja.
06:04 jkaberg hemebond: please explain, if you have an example please share
06:05 zer0def i think the implication is recursive pillar templating
06:05 hemebond You're talking about shared or "global' pillar data, yeah?
06:05 hemebond using pillar data in another pillar file isn't really possible so I just use a globals.jinja file that contains shared information.
06:06 hemebond And other pillar files import it.
06:12 jkaberg hemebond: you're refering to https://docs.saltstack.com/en/latest/topics/pillar/#including-other-pillars ?
06:13 jkaberg or a general jinja feature?
06:14 ProT-0-TypE joined #salt
06:14 jkaberg but yeah, we'd call it "common" as it stuff we want to reuse in several pillar (proxy server's, ldap servers etc)
06:14 jkaberg but global works to :-D
06:15 hemebond It's just jinja.
06:16 hemebond {%- from "globals.jinja" import g %}
06:18 jkaberg right hemebond, thanks
06:18 jkaberg I'll give that a shot
06:18 jkaberg is that relative to the root of pillar?
06:18 jkaberg the path to globals.jinja
06:19 jkaberg relative path*
06:20 hemebond Relative to the root.
06:21 _xor joined #salt
06:37 aldevar joined #salt
06:43 haam3r_ joined #salt
06:45 jrj joined #salt
06:47 Waples_ joined #salt
06:48 Waples_ Morning
06:58 xet7 joined #salt
07:10 darioleidi joined #salt
07:13 BarBQ joined #salt
07:13 Ricardo1000 joined #salt
07:16 _xor joined #salt
07:16 jhauser joined #salt
07:18 briner joined #salt
07:31 orichards joined #salt
07:32 orichards joined #salt
07:35 Pjusur joined #salt
07:36 Hybrid joined #salt
07:44 tyx joined #salt
07:55 Elsmorian joined #salt
08:01 mikecmpbll joined #salt
08:01 briner joined #salt
08:06 tys101010 joined #salt
08:08 briner joined #salt
08:29 exarkun joined #salt
08:32 tys101010 joined #salt
08:45 Hybrid joined #salt
08:51 Mattch joined #salt
08:59 Hybrid joined #salt
09:22 JacobsLadd3r joined #salt
09:31 jrj joined #salt
09:32 gforgx joined #salt
09:41 colegatron joined #salt
09:42 joshin joined #salt
09:42 joshin joined #salt
09:55 DanyC joined #salt
10:03 colegatron left #salt
10:22 joshin joined #salt
10:22 joshin joined #salt
10:31 pf_moore joined #salt
10:36 Hybrid joined #salt
10:36 zerocool_ joined #salt
10:38 CrummyGummy joined #salt
10:43 Mogget joined #salt
10:54 darioleidi joined #salt
11:02 tys101010 joined #salt
11:05 pewpew joined #salt
11:19 ddg joined #salt
11:21 jrenner left #salt
11:23 jrenner joined #salt
11:24 zulutango joined #salt
11:29 golodhrim|work joined #salt
11:45 tys101010 joined #salt
11:48 aT_ joined #salt
11:51 ddg joined #salt
11:52 dendazen joined #salt
12:03 jkaberg left #salt
12:07 scooby2 joined #salt
12:13 Nahual joined #salt
12:14 briner joined #salt
12:18 golodhrim|work joined #salt
12:23 briner_ joined #salt
12:24 thelocehiliosan joined #salt
12:27 golodhrim|work joined #salt
12:34 Tyrant joined #salt
12:34 Tyrant joined #salt
12:38 Elsmorian joined #salt
12:40 briner joined #salt
12:43 briner_ joined #salt
12:45 Tyrant joined #salt
12:58 edrocks joined #salt
13:07 brokensyntax joined #salt
13:18 racooper joined #salt
13:28 thelocehiliosan joined #salt
13:34 Elsmorian joined #salt
13:37 onslack <gtmanfred> Morning
13:38 cgiroua joined #salt
13:38 gtmanfred dimeshake: i will poke cro about it today.
13:40 gtmanfred dimeshake: we made some hardware changes, and it was brought down during that, so hopefully it will be back up soon
13:48 gh34 joined #salt
13:49 zerocoolback joined #salt
13:51 wavded joined #salt
14:02 mikecmpb_ joined #salt
14:03 stack joined #salt
14:03 stack hello, when using salt-ssh and multiple environments I get errors like The conflicting ID is 'base_files' and is found in SLS 'base:base_files' and SLS 'prod:base_files'
14:04 stack is it common? is there any solution to this problem ?
14:08 viq https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.puppet.html -> https://github.com/saltstack/salt/blob/v2018.3.0/salt/modules/puppet.py#L32 -> https://github.com/saltstack/salt/blob/v2018.3.0/salt/utils/path.py#L189 which uses system's PATH. How do I add /opt/puppetlabs/bin/ to salt-minion's path without modifying systemd unit?
14:08 stack this is the relevant config section http://paste.debian.net/1019910/ , I should add that with other hosts where I can use salt and not salt-ssh this errors is not presented
14:12 schemanic joined #salt
14:15 zerocoolback joined #salt
14:15 viq So a temporary solution is https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.environ.html#salt.modules.environ.setenv but is there something more permanent?
14:18 zerocoolback joined #salt
14:25 tiwula joined #salt
14:26 GMsoft_ left #salt
14:32 theloceh1liosan joined #salt
14:33 briner joined #salt
14:38 gtmanfred viq: set it in the systemd unit with Environment
14:39 gtmanfred just drop a file at /etc/systemd/system/salt-minion.service.d/path.conf
14:39 gtmanfred with
14:39 gtmanfred [Service]
14:39 gtmanfred Environment=PATH=/opt/puppetlabs/bin:whateverelse
14:39 viq huh, I wasn't aware of that mechanism, thank you
14:40 gtmanfred :+1:
14:40 gtmanfred drop in files are great
14:40 Cadmus '.d' directories are so useful
14:40 Cadmus I'm actually using them a lot with things like limits.d with salt itself, rather than trying to manage limits.conf dorectly (for example)
14:40 gtmanfred stack: if you are applying the same states from both environments to the same machine in top.sls, and you have the same state_ids in both, you will have conflicts
14:41 gtmanfred either add {{env}} top the end of the state_id, or only apply states from one environment to a machine
14:42 gtmanfred or specify which saltenv to apply when you do a highstate, salt \* state.highstate saltenv=base or saltenv=prod
14:45 om2 joined #salt
14:50 edrocks joined #salt
14:50 racooper joined #salt
14:52 keltim joined #salt
14:55 Waples_ exit
14:57 briner joined #salt
15:10 stack gtmanfred: I'll try with saltenv=prod, probably I missed it with salt-ssh and I already have it for `salt`
15:11 stack gtmanfred: calling salt-ssh with state.apply saltenv=prod pillarenv=prod , I get the same errors
15:18 babilen I'm seeing "stderr: 'error: could not lock config file /var/cache/salt/master/pillar_gitfs/$SOME_SHA/.git/config: File exists" on 2017.7 and can't find information as to what might be the cause of that
15:18 babilen Does that look familiar to someone?
15:24 nkuttler joined #salt
15:24 DammitJim joined #salt
15:25 dezertol joined #salt
15:31 nixjdm joined #salt
15:36 froztbyt1 left #salt
15:37 froztbyte joined #salt
15:39 stankmac1 left #salt
15:39 stankmack joined #salt
15:48 lordcirth_work babilen, never seen that but looks like there is already a lock file
15:58 babilen lordcirth_work: Yeah .. It doesn't appear after I switched that master to the "new" way of configuring git_pillars
16:02 VR-Jack2-H joined #salt
16:09 babilen Still *shrug*
16:10 babilen I guess it was due to multiple processes trying to get a lock, while the "old" git_pillar code doesn't properly manage the lockfiles
16:10 frots joined #salt
16:16 DanyC joined #salt
16:23 DanyC joined #salt
16:25 DanyC_ joined #salt
16:25 brokensyntax joined #salt
16:46 aldevar left #salt
16:46 dimeshake gtmanfred: cool, thanks for lookin' at it!
16:59 schemanic joined #salt
17:00 briner joined #salt
17:00 schemanic Hello. Is there a way to make salt display what states should be being applied to a given minion? I have something not being run during highstate that seems to be assigned in my topfile
17:02 StarHeart left #salt
17:02 Edgan joined #salt
17:10 dimeshake schemanic: state.show_highstate
17:10 dimeshake it's pretty verbose but does what it says
17:28 cewood joined #salt
17:40 mechleg joined #salt
17:45 dezertol joined #salt
17:48 edrocks joined #salt
17:51 Edgan schemanic: show_top
18:04 schemanic Hello. There is a problem with archive.extracted in 2018.3. Running archive.extracted across multiple minions fails, while the same state works properly against only a single minion
18:04 sjorge joined #salt
18:06 dezertol joined #salt
18:17 jeffspeff joined #salt
18:21 briner joined #salt
18:22 briner joined #salt
18:28 mikecmpbll joined #salt
18:32 MTecknology I tend to prefer show_top unless I'm debugging execution ordering
18:33 dimeshake i usually just do a highstate with test=True
18:37 schemanic Are there any reports of states not properly applying when called against multiple minions?
18:38 JacobsLadd3r joined #salt
18:38 MTecknology that seems like an odd question
18:38 schemanic but applying properly when called against a single minion?
18:38 MTecknology Does it apply to all without problem if applied one at a time?
18:38 briner joined #salt
18:39 cliluw joined #salt
18:40 schemanic MTecknology, yes that's correct
18:41 MTecknology what's the error?
18:41 MTecknology got a log?
18:42 schemanic I can individually call the state against each minion individually yes
18:43 schemanic I can pull a log shortly. I'm fixing an issue currently
18:48 * whytewolf wonders how it is possable for a function to fail across multiple servers but work on single servers at a time. when the multple processes are unrelated to each other. either download is stripping the master of resorces so other minions are unable to download the file. or the files are being extracted to an NFS mount that multiple servers have access to
18:48 schemanic whytewolf, the archive that is being downloaded does indeed live on s3 as part of the salt file server
18:49 schemanic This problem was not happening prior to my compulsory upgrade to 2018.3
18:49 quique joined #salt
18:49 hammer065 joined #salt
18:50 Elsmorian joined #salt
18:51 quique is there a way to run a state file without targeting a minion?
18:51 MTecknology compulsory, eh?
18:53 schemanic yes MTecknology, by circumstance. salt-bootstrap's behavior on Amazon Linux is broken for specifying specific minion version. I can't commission new nodes in this way without upgrading to the latest version, as I cannot specify the minion version properly
18:53 schemanic ergo my new minions are always at the latest released salt version until the fix has been applied. I have an issue in on the project's Github page
18:54 MTecknology well.. I told you what I think about the bootstrap
18:54 schemanic sure.
18:58 crux-capacitor joined #salt
19:03 aldevar joined #salt
19:05 evle2 joined #salt
19:06 DanyC joined #salt
19:11 thelocehiliosan joined #salt
19:17 DanyC_ joined #salt
19:20 evle2 joined #salt
19:22 DanyC joined #salt
19:26 rivyn joined #salt
19:28 rivyn Is there a way to make file.managed replace the target file when the source file has changed?  I thought that would be default behavior but it's not touching the contents of the target file if it's already there, just returning clean.
19:31 brokensyntax joined #salt
19:31 rivyn http://dpaste.com/27J6D9E  <-- simple test state
19:34 das_deniz joined #salt
19:37 MTecknology If the source file changes, the destination should be modified.
19:58 orichards joined #salt
19:58 crux-capacitor joined #salt
20:01 DanyC_ joined #salt
20:07 lordcirth_work joined #salt
20:08 lordcirth_work Anyone configuring networking in 18.04?  If so, which way?
20:08 thelocehiliosan joined #salt
20:09 zer0def i think ubuntu 18.04 has some overlay crap on systemd-networkd
20:10 zer0def /etc/netplan/*.yaml
20:11 keldwud joined #salt
20:12 keldwud joined #salt
20:14 aldevar left #salt
20:15 crux-capacitor hi all, during a state run, is it possible to read the output of one of the commands, and run another command based on that output?
20:16 Bonjourm8 joined #salt
20:18 howdybud54 joined #salt
20:19 Bonjourm8 joined #salt
20:20 MTecknology lordcirth_work: Hah! I /just/ wrote states for that this week.
20:20 lordcirth_work MTecknology, can you share it please?
20:21 MTecknology not all, but some- ya
20:21 MTecknology http://dpaste.com/379PAPF
20:23 MTecknology If you wanna help me fix that thing....
20:23 MTecknology At one point gtmanfred was going to teach me to write test cases for salt, but we never got around to it.
20:30 lordcirth_work MTecknology, In 16.04 network.managed just writes to /etc/network/interfaces.  What does it do in 18.04?
20:37 thelocehiliosan joined #salt
20:40 MTecknology same thing
20:40 MTecknology lordcirth_work: is there something special you're expecting from 18.04?
20:42 joseph_ joined #salt
20:47 evle2 joined #salt
20:48 Edgan schemanic: My opinion is you should always bake the salt-minion into your ami. It is also a good idea, because they will delete old AMIs over time, but your's will last as long as you want them to.
20:59 schemanic mmm. Edgan - I see what you're saying. Set one up with salt-cloud then save the AMI with the right version of salt-minion
20:59 Hybrid joined #salt
21:02 dendazen joined #salt
21:02 theloceh1liosan joined #salt
21:03 MTecknology Edgan: there's a strong chance they're not even building their own images
21:04 schemanic MTecknology, thats correct. My understanding is that I'm meant to provision a new machine on the fly
21:04 MTecknology FSV of "on the fly"
21:04 schemanic FSV: unknown ackronym
21:04 schemanic please elaborate?
21:05 MTecknology for some value
21:05 schemanic hmm. I'm not sure I follow. I'm a bit curious how this pans out when it comes to using salt-cloud to stand up the system
21:06 MTecknology I could explain some options, but you've listened to nearly nothing I've ever said, so I'll leave that for Edgan...
21:16 Hybrid joined #salt
21:20 keldwud joined #salt
21:20 keldwud joined #salt
21:21 ymasson joined #salt
21:28 Hybrid joined #salt
21:33 thelocehiliosan joined #salt
21:47 Hybrid joined #salt
21:50 exarkun joined #salt
21:53 zulutango joined #salt
22:16 orichards joined #salt
22:34 jsmith0012 joined #salt
22:34 jsmith0012 can you do a state for the contents of a entire folder?
22:37 hemebond jsmith0012: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.recurse ?
22:38 jsmith0012 (face palm) missed that.  thx
22:43 dendazen joined #salt
22:44 armin joined #salt
23:09 zerocoolback joined #salt
23:14 mircea joined #salt
23:17 mircea left #salt
23:20 mircea joined #salt
23:27 zerocoolback joined #salt
23:30 exarkun joined #salt
23:36 zerocoolback joined #salt
23:39 zerocoolback joined #salt
23:53 Edgan The yaml parsing in 2018.3.0 got stricter.
23:53 hemebond It did?
23:56 Edgan hemebond: https://pastebin.com/J5qziUQM worked without error in 2017.7.4, but I had to dedup the acme to make it work in 2018.3.0
23:56 hemebond I'm very surprised that worked.
23:56 hemebond I don'
23:57 hemebond I don't remember ever being able to have dupes like that.
23:57 Edgan hemebond: I wouldn't have expected it to either, but I only got an error after upgrading
23:58 hemebond Maybe it's the load_yaml filter that has become stricter.
23:59 Edgan maybe

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