Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2017-01-24

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

All times shown according to UTC.

Time Nick Message
00:06 PatrolDoom joined #salt
00:12 antpa joined #salt
00:19 derrickm All, does anyone know of a directive in Salt Cloud that will make Cloud wait for SSH
00:20 derrickm I did some debugging and found out AWS does some Cloud-init stuff which breaks SSH for users who get in the first second or so
00:20 derrickm which Salt does
00:20 pipps joined #salt
00:20 xbglowx joined #salt
00:20 derrickm best would be to wait x # of seconds until AWS finishes provisioning and then attempting
00:22 derrickm surprised nobody has ran into this issue
00:23 derrickm not an issue with Salt, but how AWS handles Cloud-init on instances booting for the first time
00:30 pipps joined #salt
00:31 toastedpenguin joined #salt
00:32 xbglowx_ joined #salt
00:36 hardyfresh joined #salt
00:50 debian112 joined #salt
00:50 xbglowx joined #salt
00:55 pipps joined #salt
00:55 hardyfresh does anyone know of any good whitepapers or articles that cover environment usage?
00:56 hardyfresh I can't seem to wrap my head around it
00:57 hardyfresh do I have a single top.sls with the different environments specified there?
00:58 MTecknology fun story... I've mostly always used a local chroot environment for doing debian dev stuff. It works, until I try to build and then I start risking hosing my host. It's not uncommon for me to oopsie and as soon as I do I know I have a hard system crash coming within the next ten minutes.
00:59 MTecknology So.. I created a new salt master to manage endpoints, decided a build VM fits into that scope nicely, and built an LXC container to do that stuff with.
01:00 MTecknology Well, my friends, it turns out I can't do dev stuff inside of that because of security restrictions. I ended up rebuilding my dev box from scratch, again, from a downloaded iso into KVM.
01:00 MTecknology What's exciting... I'm right back to the *exact* point I was about half an hour ago with the re-deployed box and now breaking past the point I was at earlier.
01:07 N-Mi_ joined #salt
01:07 tercenya joined #salt
01:18 druonysus_ joined #salt
01:19 debian112 joined #salt
01:20 paant joined #salt
01:26 jas02 joined #salt
01:26 MTecknology :D  https://gist.github.com/MTecknology/09541e13cb5f9d31a98c3bbf1b5fea32
01:30 xbglowx joined #salt
01:40 debian112 joined #salt
01:47 Reverend joined #salt
01:51 antpa joined #salt
01:53 DEger joined #salt
02:05 edrocks joined #salt
02:12 debian112 joined #salt
02:13 hvn joined #salt
02:13 hvn joined #salt
02:15 gnomethrower joined #salt
02:16 gnomethrower Hey guys
02:17 gnomethrower I have an interesting question
02:17 gnomethrower I want to lock down a root account as much as possible. The idea is that users log in and use sudo to get root privs via their own users. However we would still like root to be accessible to a single important user
02:18 gnomethrower My question is how do you set the root password using Salt while not needing to know what it is? Can you store, say, a hash of the password instead?
02:20 gmacon joined #salt
02:23 gnomethrower I was looking at HashiCorp Vault and Salt's GPG renderer and not really sure if they will solve my issue
02:25 catpiggest joined #salt
02:26 jas02 joined #salt
02:34 ntropy gnomethrower: did you see the docs for user.present state function?
02:35 ntropy you can manage the user password, by specifying the password hash
02:36 hoolio joined #salt
02:37 gnomethrower ntropy: that may be what i'm looking for, thanks
02:37 gnomethrower :)
02:37 hoolio hey, getting "[WARNING ] Key 'file_ignore_glob' with value None has an invalid type of NoneType" with 2015.8.8 packaged for 16.04
02:39 hoolio short of stepping outside of the apt universe and upgrading salt, what can i do to make these disappear?
02:39 iggy ignore it
02:39 iggy or set file
02:40 antpa joined #salt
02:40 iggy or set file_ignore_glob to something else (perhaps an empty string '')
02:41 hoolio ok ta, that fixed it
02:46 cacasmacas joined #salt
02:47 ilbot3 joined #salt
02:47 Topic for #salt is now Welcome to #salt! <+> Latest Versions: 2016.3.4, 2016.11.1 <+> Support: https://www.saltstack.com/support/ <+> Logs: http://irclog.perlgeek.de/salt/ <+> Paste: https://gist.github.com/ (please don't multiline paste into channel) <+> See also: #salt-devel, #salt-offtopic <+> Ask with patience as we are volunteers and may not have immediate answers
03:05 druonysus_ joined #salt
03:12 hvn joined #salt
03:27 jas02 joined #salt
03:28 raspado joined #salt
03:33 Reverend_Fail joined #salt
03:45 DEger joined #salt
03:52 anotherzero joined #salt
03:54 antpa joined #salt
04:00 writtenoff joined #salt
04:00 dstensnes joined #salt
04:04 tobiasBora joined #salt
04:08 edrocks joined #salt
04:09 madboxs joined #salt
04:21 ruxu joined #salt
04:26 druonysus_ joined #salt
04:28 jas02 joined #salt
04:40 madboxs_ joined #salt
04:52 DEger joined #salt
04:59 druonysus_ joined #salt
04:59 ws2k3_ joined #salt
04:59 aharvey joined #salt
05:00 smcquay joined #salt
05:00 onlyanegg joined #salt
05:09 al joined #salt
05:16 tehsu joined #salt
05:29 samodid joined #salt
05:29 jas02 joined #salt
05:31 impi joined #salt
05:46 PatrolDoom joined #salt
05:47 madboxs joined #salt
05:51 evle joined #salt
05:59 DanyC joined #salt
06:08 euidzero joined #salt
06:10 euidzero_ joined #salt
06:12 netcho joined #salt
06:12 DanyC joined #salt
06:12 lasseknudsen joined #salt
06:20 ruxu joined #salt
06:25 euidzero joined #salt
06:30 jas02 joined #salt
06:33 DEger joined #salt
06:34 citaret Hi, I use salt-cloud to fire up vps on Vultr, however, it fails to install salt-minion with the message "[ERROR   ] Failed to start Salt on host", how can i find the problem?
06:35 teclator joined #salt
06:40 ronnix joined #salt
06:41 mpanetta joined #salt
06:44 netcho moin all
06:49 DanyC joined #salt
06:55 netcho does git.latest does git fetch --all by default? Trying to fetch a branch with only -rev and it used to work until someone force-pushed to another branch. Since that job is failing
06:57 netcho https://hastebin.com/onequmirim.sql
06:58 netcho after deleting branch1 runs fine
07:08 Klas joined #salt
07:10 edrocks joined #salt
07:12 iggy citaret: run with `-l debug` ... make sure you are running the latest bootstrap script (salt-cloud -u), are you passing any script args?
07:15 tom[] joined #salt
07:19 Rumbles joined #salt
07:21 funabashi joined #salt
07:29 citaret iggy: I followed the official documnet https://docs.saltstack.com/en/latest/ref/clouds/all/salt.cloud.clouds.vultrpy.html, and not passing any args.
07:30 citaret when run in debug mode, there are lots of message of 'Permission denied, please try again.', seems like the salt-master has no password to log into the minion.
07:31 Neighbour what does `salt-key --list-all` say?
07:31 Neighbour (on the master)
07:31 jas02 joined #salt
07:32 citaret it lists the new minion as accept key.
07:32 funabashi joined #salt
07:32 Neighbour then you have to accept the key with `salt-key --accept <new minion name>`
07:32 Neighbour (without the <>)
07:33 whytewolf if we are talking about salt-cloud then the key would already be accepted.
07:33 citaret it's already in Accepted Keys.
07:33 whytewolf [salt-cloud keys are generated on the master and shipped to the minion after creation]
07:34 infrmnt joined #salt
07:34 citaret i think the problem is the master has no password to login in the minion.
07:34 infrmnt left #salt
07:34 Trauma joined #salt
07:34 citaret but i do not know how to add password config in the cloud.provides
07:34 whytewolf I don't know enough about how vultr creates it's disks. but you should have to supply a ssh password or key
07:35 whytewolf citaret: https://docs.saltstack.com/en/latest/topics/cloud/misc.html
07:36 whytewolf typically for most clouds a ssh_password is the password
07:36 whytewolf and ssh_username is the user to login as
07:36 iggy citaret: salt-cloud doesn't use the password, it uses an ssh key
07:36 citaret i will hava a try, thanks.
07:36 whytewolf it can do both. but keys are perfered.
07:37 netcho how can i pass aws access key and id from pillar to state? i can't find an example in docs. All it says is profile: myprofile. I know how to set key separate but how cn i group them in 'myprofile'
07:37 netcho or am i missing smth here :)
07:38 iggy yeah, I should rephrase... the only way I ever got it to work was with ssh keys
07:38 iggy and I had to pass args (-P)
07:40 whytewolf it depends so much on which cloud that it almost isn't funny or easy to debug .. each one has so many different things internally that effect how ssh works
07:41 netcho https://hastebin.com/azomohozog.nginx
07:42 whytewolf netcho: did you read the bit at the top of boto_iam_role?
07:42 whytewolf it tells you wha tthe pillar looks like for a profile there
07:42 whytewolf actually tells you at the top of boto_secgroup as well
07:43 whytewolf netcho: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.boto_secgroup.html
07:44 netcho yes i did but i don't quite get it
07:45 iggy citaret: actually, I just remembered, I had to downgrade the bootstrap script... and then I ended up just writing my own
07:45 iggy vultr is such a pita
07:45 whytewolf you see the section that has myprofile: keyid: <with an id>, key: <key>
07:45 whytewolf thats the pillar profile
07:45 whytewolf you access that in the state with profile: myprofile
07:46 netcho i tried using use-instance-role-credentials with salt-cloud  for launching ec2 (salt master has fullAdmin for test) but for some reason had issues with deleting keys on termination
07:50 netcho whytewolf: how can i do that?
07:50 netcho sorry to bother but i am kinda confused here
07:50 whytewolf netcho: what do you mean how?
07:50 whytewolf you know how pillars work right?
07:51 whytewolf you assign them to a minion. and they get set
07:51 netcho ye i do and i managed to pull id and key
07:51 whytewolf in a profile?
07:51 netcho from a profile in state
07:51 whytewolf like it shows you how to build with the myprofile?
07:52 netcho no, with get.pillar
07:52 netcho i think i am missinterpreting 'profile' here :)
07:52 whytewolf no i mean the section that shows you what the pillar of myprofile looks like
07:53 whytewolf it shows a info block at the top of the page that has myprofile with three items below it
07:54 netcho i get that, and i have pillar file with that content
07:54 whytewolf okay, and you have that assigned to a minion that will be running the boto command correct?
07:55 netcho yes.. so i have to do {% set key = aws.get('key', {''}) -%} for example?
07:55 whytewolf no
07:55 whytewolf no jinja involoved
07:55 whytewolf - profile: <name of your profile in pillar>
07:56 netcho oh i see where the error is
07:56 whytewolf the state function will do the pull of the pillar. you just need to tell it what the name it
07:56 whytewolf is
07:57 citaret iggy: i added ssh key to the providers config, it still failed .
07:59 netcho whytewolf: sorry i was stupid, i had secretkey: xxx instead of key: xxx in pillar :/
08:00 whytewolf ... welp that would cause issue
08:00 netcho it even told me...  TypeError: cannot concatenate 'str' and 'NoneType' objects
08:01 netcho i still havent figured out why using instance role in cloud profile fails to delte key on termination
08:02 netcho it terminates the intance and leaves key accespted... for example minion-DEL234534534543
08:02 whytewolf i couldn't tell you, i don't use salt-cloud with aws. ... only thing i use on aws is route 53
08:02 netcho fair enough :)
08:02 whytewolf do you do something stupid like rename your minions?
08:02 netcho on termination yes
08:03 netcho and it works ok when i set keys in profile
08:03 antpa joined #salt
08:03 netcho but when i use master-iam role it does not
08:04 * whytewolf shrugs. not sure. maybe it isn''t returning the name that salt-cloud is thinking about so doesn't know which key to delete. but that is just random speculation.
08:08 lord2y joined #salt
08:09 lord2y hello folks
08:10 whytewolf good morning
08:10 lord2y newbie question: is there a way to check the presence of file(s) before apply the state?
08:11 whytewolf why?  if the file exists it will be over ridden if it doesn't it will be created. if the file that exists is already in the state you want it to be then nothing changes.
08:12 whytewolf if you want it to be backed up look at this https://docs.saltstack.com/en/latest/ref/states/backup_mode.html#file-state-backups
08:14 lord2y I have a batch job that run onece in a while, create a set of files. Some of these file will be over ridden but I need to delete the others
08:14 lord2y and I don't know the file name of these files
08:14 whytewolf sounds like you actually want a file.recurse with clean [depending on location
08:15 lord2y something like that but I need to match a regexp or exclude files I want to keep
08:16 whytewolf why not manage all the files? [but clean does have a exclude pattern
08:17 dariusjs joined #salt
08:18 lord2y whytewolf: what do you mean with 'manage all the files'?
08:20 whytewolf well. what is managing the files that you want to keep currently? an application? then why are you touching anything in the directory and why isn't that application managing it's files? if not the application why are you not managing the files through salt.
08:22 whytewolf basicly from what little you have given you are running into a dangerous area. it could be you are casting a net to wide for what you actually want to do
08:22 lord2y I'm managing the file through salt, but there are certain files that have unpredicatable names
08:22 whytewolf nothing about salts file names should be unpredictable
08:23 whytewolf they come from somewhere
08:23 samodid joined #salt
08:24 whytewolf most unpredictable filenames are done by applications because they are not meant to be touched
08:24 onlyanegg joined #salt
08:25 lord2y they are garbage trust me
08:25 lord2y I know what I'm doing
08:26 lord2y but ok, I'll take in mind to manage all the file through salt
08:27 o1e9 joined #salt
08:27 JohnnyRun joined #salt
08:28 Rumbles joined #salt
08:28 whytewolf well if they are managed by salt. you can have a file.recurse that requires the files that are file.managed. put a clean on that file.recurse [or file.directory] and anything not in those requires will be cleaned. and like i said there are exclude patterns for clean
08:29 whytewolf https://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html#salt.states.file.directory
08:29 whytewolf look at exclude_pat for more about the exclude pattern
08:29 ronnix joined #salt
08:32 lord2y clever suggestion, but I cannot use in this context.
08:32 toanju joined #salt
08:32 jas02 joined #salt
08:32 lord2y in the same directory there are files that I must *no* touch
08:33 whytewolf ... that sounds like a bad design in the software if there are files that you must clean up, must managed and can't touch
08:33 whytewolf all in one directory
08:33 fredvd joined #salt
08:34 lord2y yeah...and I'm the poor sysops that has to take care of that
08:35 sergeyt joined #salt
08:35 jas02 joined #salt
08:36 marcinkuzminski joined #salt
08:36 whytewolf i don't know if they count. but there is a file.exists state. I am unsure if they are required in a file.directory wil clean if they count as a file that shouldn't be touched.
08:36 candyman88 joined #salt
08:37 whytewolf however they deffintly will cause errors if the file DOESn't exist and is required.
08:40 whytewolf with a little jinja you might be able to craft states that even in unknown names might be able to find the files that are offlimits. but must stay.
08:42 whytewolf anything is possable. just some things take more work
08:43 lord2y true
08:43 krymzon joined #salt
08:44 lord2y actually I was thinking to arrange something with jinja
08:44 lord2y but I'm still not mastering it, so it's a little bit tricky
08:46 dariusjs_ joined #salt
08:53 dariusjs joined #salt
08:54 DanyC joined #salt
08:56 mikecmpbll joined #salt
08:57 antpa joined #salt
09:04 AndreasLutro lord2y: consider writing a custom state module if the logic is really complex. if it's not that complex you can use "creates" or "unless" or "onlyif" to only conditionally run your states
09:06 kbaikov joined #salt
09:08 scristian joined #salt
09:10 teclator joined #salt
09:12 edrocks joined #salt
09:15 toanju joined #salt
09:16 DanyC joined #salt
09:16 DanyC left #salt
09:19 dariusjs joined #salt
09:25 lord2y AndreasLutro: can you point me to 'onlyif' documentation?
09:27 AndreasLutro I'm sure you'll find it if you google "salt onlyif"
09:35 lord2y AndreasLutro: ok :-)
09:36 AndreasLutro that's how I find all my salt documentation anyway
09:36 impi joined #salt
09:38 rubenb Hi. Are there any known issues with the Windows minion using a lot of CPU?
09:38 lord2y well, I do the same. I just thought you had some tutorial. Salt's documentation is often confusing :-/
09:49 candyman88 joined #salt
09:50 antpa joined #salt
09:52 dariusjs joined #salt
09:54 netcho joined #salt
09:54 s_kunk joined #salt
09:54 kiorky joined #salt
10:09 DEger joined #salt
10:21 jhauser joined #salt
10:25 onlyanegg joined #salt
10:30 antpa joined #salt
10:37 jas02 joined #salt
10:43 sfxandy joined #salt
10:43 sfxandy morning all
10:44 sfxandy daxroc, how is your http.waitforsuccessfulquery patch coming on?
10:44 daxroc sfxandy:
10:44 daxroc testing it now, submitting today
10:45 manji does anyone know if the minion.d directory is being monitored for changes  when the salt-minion is running ?
10:45 manji I have a chicken and egg problem
10:45 sfxandy go on manji
10:45 manji when a minion is to become a mysql server
10:45 manji I need to create the minion.d/mysql.conf file
10:46 manji where I put
10:46 manji mysql.default_file: /etc/mysql/debian.cnf
10:46 sfxandy daxroc, thanks.... i  could do with that
10:46 manji so I can have salt create users, databases etc
10:46 manji in my highstate I place the file, and I restart the minion server
10:46 manji service*
10:46 manji which, of course, disrupts the highstate
10:47 manji I could have a runner to do that before I run highstate
10:47 manji but before I run highstate, the  /etc/mysql/debian.cnf does not exist
10:47 manji since I haven't installed mysql yet
10:48 N-Mi_ joined #salt
10:48 manji so I don;t know if the minion caches  /etc/mysql/debian.cnf  on start
10:48 netcho joined #salt
10:48 sfxandy any particular reason why you are adding a .conf file into minion.d?  seems quite disruptive.  could it not be added to Pillar?
10:49 sfxandy the mysql.default_file: /etc/mysql/debian.cnf i mean...
10:49 manji sfxandy,  /etc/mysql/debian.cnf  is different on each server
10:49 manji since it generates a mysql password
10:50 manji the debian package generates a password that is
10:50 antpa joined #salt
10:51 sfxandy so the mysql.default_file property .... what references that?
10:52 manji sfxandy, what do you mean by references?
10:52 manji I lost you there :/
10:52 antpa joined #salt
10:53 manji the mysql_* salt modules read it
10:53 manji to perform operations on mysql
10:53 manji mysql_grants,  mysql_user etc
10:53 sfxandy must confess, never used the mysql modules
10:54 manji hahaha
10:55 sfxandy ok i've just read the docs, understand now
10:55 manji sfxandy, I use debconf to pre-define the db root password
10:55 manji and then use the mysql module to create users, privileges and empty dbs
10:58 manji I does anyone know if instead of restarting the minion service
10:59 manji I reload it, if this will affect highstate's run ?
10:59 manji I found a discussion about it, but it kind of went nowhere
10:59 AndreasLutro manji: when a new minion boots up, you just have to make sure to run your salt minion states before any other states
11:00 AndreasLutro that way your salt config gets put in place, minion restarts, then all the other states happen
11:00 manji AndreasLutro, that is the thing
11:00 manji I can have the file  minion.d/mysql.conf  installed before I run highstate
11:01 manji eg using a reactor
11:01 manji but the file that is referenced in it, doesn't exist yet, since I havent installed mysql yet
11:02 manji unless
11:04 manji it reads the  mysql.default_file option when I actually call a mysql salt module
11:04 antpa joined #salt
11:04 manji I will have to test it I guess
11:08 manji thnx
11:19 amcorreia joined #salt
11:30 antpa joined #salt
11:38 jas02 joined #salt
11:41 coredumb Hello folks
11:41 ivanjaros joined #salt
11:42 Reverend sup coredumb
11:42 coredumb I run an orchestrator from a reactor, that runs a highstate for a specific group. The highstate run from the orchestrator for some reasons don't see my modifications from my gitfs whyle if I use the CLI to state.{apply,show_{low,high}state} it works fine
11:43 coredumb could it be some cache somewhere messing with me ?
11:43 coredumb while*
11:44 madboxs joined #salt
11:46 dariusjs joined #salt
11:48 amontalban joined #salt
11:48 amontalban joined #salt
11:55 gareth_ joined #salt
11:57 Guest95341 How do I force the host value when using salt-cloud? Using 3 NICs seems to randomly select which host to try and install salt to
12:04 lmctague joined #salt
12:09 franky joined #salt
12:09 abednarik joined #salt
12:12 coredumb mmmh for some reason orchestrator seems to force a saltenv ...
12:24 edrocks joined #salt
12:26 onlyanegg joined #salt
12:27 dariusjs joined #salt
12:28 coredumb ok so reactor actually calls orchestrator with saltenv: base
12:28 netcho joined #salt
12:29 amy_ joined #salt
12:30 cacasmacas joined #salt
12:32 AndreasLutro heh
12:32 AndreasLutro another reason to shy away from saltenvs
12:39 jas02 joined #salt
12:41 eThaD joined #salt
12:45 honestly is it a known issue that (custom?) grains aren't accessible inside file templates (i.e. the source of a file.managed state with jinja) with salt-ssh?
12:46 XenophonF joined #salt
12:47 madboxs joined #salt
12:48 antpa joined #salt
12:57 ronnix joined #salt
12:59 Firewalll joined #salt
13:00 ruxu joined #salt
13:01 DEger joined #salt
13:07 numkem joined #salt
13:10 binocvlar joined #salt
13:10 netcho joined #salt
13:12 Firewalll joined #salt
13:12 laax joined #salt
13:16 sergeyt joined #salt
13:18 aidin joined #salt
13:23 snc joined #salt
13:24 snc joined #salt
13:32 edrocks joined #salt
13:33 abednarik joined #salt
13:35 nicksloan joined #salt
13:35 rypeck joined #salt
13:36 nicksloan I'm getting an error about pip not being installed on 2016.11.1
13:36 rypeck left #salt
13:37 abednarik joined #salt
13:38 nicksloan I'm running a state to install the virtualenv package with pip when I get the error message. That state depends on a pkg.installed for python-pip
13:41 edrocks joined #salt
13:45 daxroc sfxandy: https://github.com/saltstack/salt/pull/38912
13:45 saltstackbot [#38912][OPEN] Enhanced wait_for_successful_query with request_interval | What does this PR do?...
13:47 dariusjs joined #salt
13:47 madboxs joined #salt
13:50 numkem joined #salt
13:50 antpa joined #salt
13:50 ssplatt joined #salt
13:52 raj_ joined #salt
13:52 sfxandy thanks daxroc
13:55 nickabbey joined #salt
13:58 abednarik joined #salt
14:01 _JZ_ joined #salt
14:01 nicksloan really stumped on this pip issue on Jessie.  Running  `cmd.run "python -c 'import pip; print pip'"` works fine
14:02 antpa joined #salt
14:12 nickabbey joined #salt
14:15 dariusjs joined #salt
14:20 nicksloan another development: it only fails for the pip.installed state, not `pip.install virtualenv`
14:24 ssplatt nickabbey: are you doing this as a one off command line thinger. or as a part of a state run
14:24 nickabbey ssplatt: wrong nick ;)
14:24 ssplatt woops. didn’t tab enough times
14:24 ssplatt sorry
14:25 nicksloan ssplatt: I did the former as a part of a full state run
14:25 nicksloan and the latter one-off
14:25 ssplatt i’ve seen the pip things fail during a state run because pip isn’t available at the start of the run
14:25 ssplatt so the salt env doesn’t know it’s there
14:25 ssplatt but 2nd run things like installing packages from pip will work
14:26 nicksloan Hmm. The funny thing is that this server is 6 months old, and these states have definitely run before
14:27 nicksloan pip has been installed this entire time
14:27 onlyanegg joined #salt
14:27 ssplatt you mentioned jessie. is it only failing on jessie? do you have other envs that it doesn’t? what versions of packages involved?
14:28 N-Mi_ joined #salt
14:30 nicksloan ssplatt: python, python-pip, python-pip-whl, python-requests, python-requests-whl are all current. Salt is 2016.11.1.
14:31 nicksloan and I don't sadly have any non-Jessie environments, but I do have a local Jessie environment where this problem is not occurring
14:31 brousch__ joined #salt
14:32 nicksloan the last thing that I recall doing on these instances was updating to 2016.11.1
14:34 ssplatt sorry i ran out of ideas
14:35 ssplatt sounds to me like there is a version conflict somewhere
14:36 riftman joined #salt
14:36 nicksloan yeah, agreed
14:36 nicksloan though of those packages that I mentioned, the versions are all identical on the server where it works vs the one where it doesn't.
14:38 amy joined #salt
14:40 dyasny joined #salt
14:41 jas02 joined #salt
14:41 daks hello
14:41 daks i have a very simple state to install pip/virtualenv and then in my virtualenv install a python package with pip
14:41 daks i think it's very simple
14:42 daks but when i specify the virtualenv to use (with bin_env) i always got an error
14:42 daks Could not find a `pip` binary
14:42 daks of course in the virtualenv i have pip
14:42 daks ls /opt/spotter/.venv/bin/pip                                                ~
14:42 daks /opt/spotter/.venv/bin/pip
14:43 daks my code is here ls /opt/spotter/.venv/bin/pip                                                ~
14:43 daks (sorry)
14:43 daks my code: https://friendpaste.com/7Bh0IM3kHZ5VbuYJHU2MdH
14:43 daks all seems fine, and I already used this and never got this error
14:43 daks does anyone knows what can be the problem
14:44 daks I am on Debian wheezy 64 with salt 2016.11
14:44 nicksloan hmmm
14:45 nicksloan I'm having pip trouble too
14:45 nicksloan but not the same kind
14:46 daks i saw on github issues this kind of problem but it seems solved since a few versions
14:46 nicksloan yep
14:47 dendazen joined #salt
14:48 daks what's really weird is that i have a custom graphite formula which does something really similar
14:48 daks and... it works!
14:48 daks :-/
14:48 madboxs joined #salt
14:49 nicksloan which salt version are you on?
14:49 daks 2016.11.1+ds-1
14:49 daks last one for wheezy on repo.saltstack.com
14:50 daks FYI: i'm running this state masterless on a vagrant VM
14:50 coredumb is there a way to tell a reactor to not force a saltenv when calling an orchestrator ?
14:50 daks but it should have no impact
15:03 aarontc joined #salt
15:05 coredumb is there no way to run a highstate through an orchestrator without any default saltenv so that it gives the same behavior than when running state.apply from the CLI ?
15:05 mikecmpbll joined #salt
15:06 mpanetta joined #salt
15:06 nicksloan the message I'm getting about unable to find an importable pip module occurs when HAS_PIP == True, that happens if an exception is raised for `import pip` or `import pip.req` and hasn't changed for more than three years
15:06 PatrolDoom joined #salt
15:08 abednarik joined #salt
15:09 daks nicksloan: I saw this issue https://github.com/saltstack/salt/issues/7659
15:09 saltstackbot [#7659][MERGED] pip.installed state has insufficient pip detection | I have a CentOS 6.3 VM running salt 0.17.0, which is python 2.6 by default. On this system, I use salt to install python2.7 along side of python2.6, create a python 2.7 virtualenv, and then use pip within that virtualenv to install python packages for my project....
15:09 coredumb or to word it differently ... how to use another saltenv than base in orchestrator when using gitfs and having a top file only in base
15:09 coredumb ...
15:09 daks and it only says that you need a systemwide pip
15:09 daks which i have
15:10 dyasny joined #salt
15:12 Brew joined #salt
15:15 netcho joined #salt
15:19 sarcasticadmin joined #salt
15:21 Tanta joined #salt
15:22 nayplum joined #salt
15:23 dyasny joined #salt
15:23 nayplum since upgrading to 2016.11 my states from two different environments are being executed in reverse order. i'm aware of the notes around merging but has something changed with the ordering?
15:23 nicksloan daks: yep. Same here
15:25 daks i opened https://github.com/saltstack/salt/issues/38915
15:25 saltstackbot [#38915][OPEN] Can't use pip.installed in a virtualenv: Could not find a `pip` binary | Description of Issue/Question...
15:25 Reverend oh god.
15:25 Reverend nayplum really?
15:25 Reverend oh wait, environments, cool. I don't use them.
15:25 * Reverend wipes sweat from forehead
15:26 tercenya joined #salt
15:26 nayplum before it was base then env1 but now it's env1 then base
15:27 nayplum output of state.show_top has them in correct order but looking at trace, the dict is ordered with env1 first
15:27 nayplum env_order does nothing to change it
15:29 nicksloan daks: your issue is definitely different
15:30 nicksloan I wouldn't rule out that they may be related, but my trouble is that pip.installed doesn't work without a bin_env
15:30 daks oh
15:30 daks in fact
15:32 nicksloan salt is using /usr/bin/python, and pip is in /usr/lib/python2.7/dist-packages/. I can definitely import pip and pip.req from /usr/bin/python with no error
15:33 nicksloan so the only conclusion I can draw is that Salt is doing some kind of path mangling somewhere that is fucking  things up
15:34 mikecmpb_ joined #salt
15:34 XenophonF nayplum: if you need an explicit ordering between two SLSes, then you probably ought to add a requisite
15:34 daks i too can import pip and pip.req
15:34 dyasny joined #salt
15:35 XenophonF nayplum: https://docs.saltstack.com/en/latest/ref/states/requisites.html#require-an-entire-sls-file
15:35 nayplum that won't work for top files tho right?
15:35 XenophonF the top file is irrelevant
15:35 drawsmcgraw joined #salt
15:36 Mattch joined #salt
15:36 XenophonF if you want states from one SLS to run before states in another, then you need to use requisites
15:36 nayplum that'd be a pain to add includes to every sls if all i want is one env to run before the second
15:37 nayplum and this worked before so not sure what changed
15:37 XenophonF agreed but i think cross environment dependencies are a bad idea
15:37 XenophonF i try to avoid cross-SLS dependencies, too
15:37 nicksloan daks: well, importing those is the check that, if fails, returns "An importable pip module is required but could not be found on your system. This usually means that the system's pip package is not installed properly."
15:37 nayplum it's more than base does initial baseline for all envs, env1 then sets up specifics
15:38 nicksloan which is the error I see, but not the one you see. So it may not be relevant for you
15:38 nayplum and i'm not sure you can actually do an include across envs
15:38 scoates joined #salt
15:38 daks you're right. i'll see if someone answers to my issue
15:38 daks (and in the venv, i can import too)
15:39 XenophonF nayplum: if you don't want to add requisites to your states in env1, then my recommendation is to rewrite your states so that they are self-contained and can run in any order
15:39 drawsmcgraw Has anyone here used (or made) something to generate Pillar files for them?
15:39 drawsmcgraw We have fairly complex deployments and have been stung by hand-editing Pillar configs a good number of times. Trying to get that process automated so it stops happening.
15:40 nayplum self-contained states would create massive duplications
15:40 nayplum and like i mentioned i'm not aware that you can actually use requisites across envs
15:40 scoates joined #salt
15:41 XenophonF the include isn't required
15:41 pcdummy joined #salt
15:41 XenophonF the state compiler should DTRT
15:41 XenophonF i could be wrong though
15:42 jas02 joined #salt
15:44 raspado joined #salt
15:47 lord2y joined #salt
15:47 debian112 joined #salt
15:48 XenophonF anyone else notice 100% CPU utilization by salt-minion on FreeBSD?
15:49 madboxs joined #salt
15:49 Miouge joined #salt
15:54 Inveracity joined #salt
15:57 nicksloan Here's my issue, in case anyone is interested in taking a look with more detail: https://github.com/saltstack/salt/issues/38916
15:57 saltstackbot [#38916][OPEN] Pip module exists but is not found | Description of Issue/Question...
15:58 nayplum joined #salt
15:59 AvengerMoJo is there a way in module to figure out the salt-master ip or hostname?
16:06 keldwud can I create multiple directories with one file.directory statement? or do I need a statement for each directory? they all live in the same folder
16:09 Inveracity keldwud, seems you can only create one at a time, however you could do a for loop in jinja
16:09 keldwud I found another creative solution
16:10 keldwud looks like if I make the source directory include empty and the source directory has subdirectories and I use file.recurse
16:10 keldwud it will copy the tree structure of the source directory
16:10 onlyanegg joined #salt
16:12 Inveracity nice
16:12 keldwud I asked in another channel and they answered at the same time you did.
16:13 jholtom hi keldwud I'm also here lol
16:13 bwellsnc Quick question guys, I am running a highstate on all my hosts with test=True, batching it for every 5, but it looks like it's using 100% of one core... is there a way to spread this load out.  thanks!
16:14 Inveracity bwellsnc, windows?
16:14 jholtom 100% of one core on the master or minion?
16:14 keldwud hah, yeah, credit goes to jholtom for the solution :)
16:14 kettlewell joined #salt
16:15 keldwud s/spread/balance
16:15 ivanjaros joined #salt
16:15 keldwud my juvenile mind can't parse spread in that sentence without chuckling
16:21 amy joined #salt
16:30 raspado joined #salt
16:31 NV joined #salt
16:32 mikecmpbll joined #salt
16:37 Renich joined #salt
16:37 whitenoise left #salt
16:38 Inveracity AvengerMoJo, possibly with network.netstat, then find an established connection to port 4505 and get the IP from there?
16:43 jas02 joined #salt
16:46 nixjdm joined #salt
16:50 samodid joined #salt
16:53 ronnix joined #salt
16:53 wryfi joined #salt
16:58 DanyC joined #salt
16:58 morissette joined #salt
17:01 impi joined #salt
17:06 iggy keldwud: you can also use `- names:` with file.directory
17:07 hackel joined #salt
17:07 bltmiller joined #salt
17:07 pipps joined #salt
17:08 iggy AvengerMoJo: __salt__['config.get']('master')
17:09 abednarik joined #salt
17:09 nicksloan joined #salt
17:10 amy joined #salt
17:10 nicksloan joined #salt
17:15 sh123124213 joined #salt
17:21 ruxu joined #salt
17:25 Edgan joined #salt
17:29 ruxu joined #salt
17:30 pipps joined #salt
17:31 DanyC joined #salt
17:33 keldwud iggy: oh interesting. where can I read more on names: ?
17:33 keldwud I didn't know about that feature
17:34 scoates joined #salt
17:37 seanz joined #salt
17:38 Inveracity I was unaware of this too, but apparently right here keldwud https://docs.saltstack.com/en/latest/ref/states/highstate.html#names-declaration
17:42 keldwud thanks for the link, Inveracity!
17:43 raspado joined #salt
17:45 Inveracity no bother
17:57 Praematura joined #salt
18:01 pepoluan joined #salt
18:01 pepoluan hello
18:01 pepoluan I am still confused as to where I should put my custom execution module.
18:03 pepoluan here is my settings for file_roots: http://pastebin.com/j8HJYhYC
18:04 pepoluan based on that settings, I should put my custom module in /srv/saltstack/states/base/_modules , amirite?
18:04 Inveracity that would be my assumption too, pepoluan
18:04 bltmiller joined #salt
18:06 whytewolf pepoluan: that is one of 4 possable places based on your settings there. there is also /srv/saltstack/formulas/_modules /srv/saltstack/states/dev and /srv/saltstack/states/prod [if you want different modules in different enviroments]
18:07 whytewolf custom modules are sinced from salt://_modules
18:07 DanyC joined #salt
18:09 whytewolf also o/ morning everyone, hopefully I am less of a __dunder__ today
18:09 s_kunk joined #salt
18:10 Trauma joined #salt
18:10 bdrung_work joined #salt
18:11 pepoluan hmmm... doing "salt-call mymod.function" doesn't work, though, when I put the mymod.py in /srv/saltstack/states/base/_modules
18:11 pepoluan strange
18:11 abonilla joined #salt
18:11 Inveracity and you've sync'd it to the minion?
18:11 whytewolf you do need to sync. using saltutil.sync_all or saltutil.sync_modules
18:12 abonilla Is there a way to have 2 salt masters (with different keys) and the minions listen to both?
18:12 pepoluan *GOOD GRIEF*
18:12 pepoluan I knew I forgot something --__--
18:12 pepoluan thanks Inveracity!
18:12 Inveracity :D
18:12 * pepoluan is getting old
18:13 pepoluan thanks also whytewolf :D
18:13 Inveracity abonilla, yes, I solved that by running two separate minion instances using the -c flag pointing to a different configuration directory
18:14 Inveracity salt-minion -c /my/other/minion
18:14 abonilla Inveracity: Ah! ;-)
18:14 whytewolf that just seems like bad juju. two masters controlling the same minion in different ways. can't imagine what will happen when the same file comes under preview of both
18:15 abonilla whytewolf: one is for Ops, other is for App.
18:15 whytewolf yeah because they never fight over files
18:15 whytewolf ;)
18:16 Miouge joined #salt
18:16 ryan8403 joined #salt
18:16 pipps joined #salt
18:17 DammitJim joined #salt
18:18 Inveracity gentleman agreements will solve such conflicts and departments always have excellent communication ...
18:18 brasticstack joined #salt
18:20 Tanta joined #salt
18:20 edrocks is there a way to tell why python is using the system installed python-requests? It is outdated(im on ubuntu 14.04) and docker-py needs the newer version installed with pip
18:20 abonilla Inveracity: it wants a directory rather than a folder
18:20 edrocks somehow I have this working on one server but not the other
18:21 Inveracity abonilla, directory rather than a file I assume you mean? and yes, it was a bad example I gave you, I meant a directory
18:22 davidka joined #salt
18:22 ronnix joined #salt
18:23 brasticstack Hi! I'm trying to rewrite a particularly complex state using the py renderer. Is there already a built-in way of importing a map that will parse jinja? I'm looking to replace a line like "{% from 'file.jinja' import foo with context %}"
18:24 abonilla Inveracity: I guess it just expects "minion" as the config file.
18:25 Inveracity abonilla, yeah it does :) also, you need to specify the new file_roots and so forth in that new minion config file
18:25 Inveracity pki dir, and a few more, hang on actually I may have a working example
18:27 davidka hi - how well is the aix support? do I need saltstack enterprise for a reasonible good aix support?
18:30 Inveracity abonilla, http://pastebin.com/1iWvLHPz I believe these to be the minimum requirements for a secondary minion config
18:30 Inveracity abonilla, I made one mistake, hang on
18:31 Inveracity abonilla, I forgot the pid file had to be explicit http://pastebin.com/MYZNy3yc
18:33 abonilla Inveracity: thanks, yeah, works for me now.
18:34 abonilla oh, let me see
18:36 DanyC joined #salt
18:37 SysadminM joined #salt
18:37 SysadminM Hello
18:43 whytewolf davidka: i doubt you will find much aix support. and i don't think enterprise has any better aix support.
18:47 iggy abonilla: I'm pretty sure the answer is no
18:47 iggy and I was apparently scrolled up
18:48 Miouge joined #salt
18:49 iggy brasticstack: many have tried, noone has succeeded afaik
18:52 brasticstack Thanks iggy!
18:52 Inveracity brasticstack, I wondering if you'd be able to import jinja2 and use that to parse it? I'm just thinking out loud
18:53 iggy Inveracity: the problem then becomes that you have to do the jinja setup of loading dunder dicts, etc
18:53 brasticstack I'm sure it's possible, I'd need to make sure it had the correct context.
18:53 brasticstack yeah
18:53 Inveracity right
18:53 madboxs joined #salt
18:54 scoates joined #salt
18:54 iggy if you have a very simple map.jinja (load defaults, merge some other yml files, etc) you are probably better off parsing those files directly and merging them using salt's merging
18:55 iggy i.e. do it all in the python rather than trying to pull in jinja
18:55 brasticstack iggy: I've moved on to the rest of my formula, I'll just keep it jinja rendered until I've got the time to dig into that.
18:56 davidka whytewolf: OK - they claim to have AIX support on their pages, but what this really means we do not know of course :) but since it´s basically based on the opensource version, I do not see why it should be any better
18:56 Inveracity apologies if this is entirely stupid, but could you do: from salt.utils import jinja
18:56 brasticstack the other question that kept bothering me is, py renderer needs to return a dict. How do I ensure that things run in the order I specified? Is it normal to use OrderedDict as the output of a pyrenderer?
18:56 davidka whytewolf: thanks. Have you tried it btw?
18:57 Trauma joined #salt
18:57 ruxu joined #salt
18:58 Inveracity brasticstack, you'll probably find #!pyobjects a better alternative
18:58 iggy brasticstack: I don't know about normal, but acceptable yes (and probably preferred for most cases)
18:59 iggy Inveracity: why do you say that?
18:59 whytewolf davidka: basicly saltstack is a python script and as such there is basic aix support. so they are not lieing about "supporting" aix. and no. i having tried it. there just isn't a lot of devops done on aix. because there are so few systems out there. however it does share some BSDisms and most of the BSDs are very supported. so who knows
19:00 Inveracity iggy, I realise it's a matter of taste, but I like calling the functions rather than forming a dict to return
19:00 davidka whytewolf: thanks
19:01 brasticstack pyobjects and pydsl both looked much nicer. Are they both being maintained and updated with salt? They kind of looked like 'contrib' code to me.
19:02 whytewolf pyobjects gets a lot of traction so would say it gets maintained. not heard about pydsl in awhile
19:02 Mattch joined #salt
19:03 brasticstack thanks, good to know! I definitely don't want to write a bunch of states only to find the renderer is obsolete.
19:05 whytewolf brasticstack: did find this ticket. https://github.com/saltstack/salt/issues/15909 which seems to imply that pyDSL really isn't touched anymore
19:05 saltstackbot [#15909][MERGED] Deprecate the PyDSL renderer | PyDSL should be deprecated now that the superior PyObjects renderer exists....
19:05 brasticstack Ah, good to know!
19:07 Heartsbane Oh noes brasticstack
19:07 prg3 joined #salt
19:07 brasticstack Oh noes Heartsbane!
19:11 dyasny joined #salt
19:17 aw110f joined #salt
19:23 bowhunter joined #salt
19:26 morissette joined #salt
19:29 druonysus_ joined #salt
19:31 amy_ joined #salt
19:31 jhauser joined #salt
19:31 jas02 joined #salt
19:32 oida joined #salt
19:41 patrek joined #salt
19:46 alxf joined #salt
19:53 teclator joined #salt
19:55 madboxs joined #salt
19:59 jgarr joined #salt
20:00 scoates joined #salt
20:01 Miouge joined #salt
20:02 jhauser joined #salt
20:10 cyborg-one joined #salt
20:10 pipps joined #salt
20:11 Heartsbane Your fault
20:14 cyteen joined #salt
20:16 mpanetta joined #salt
20:16 XmonkModeY joined #salt
20:16 oida joined #salt
20:17 XmonkModeY Hi all. If defining multiple pillar gitfs backends, I believed the order in which they were defined is the search order - can someone confirm?
20:20 beebeeep_ joined #salt
20:21 dfinn joined #salt
20:21 bltmiller joined #salt
20:23 sfxandy joined #salt
20:24 Tanta joined #salt
20:31 mritchie joined #salt
20:32 jas02 joined #salt
20:36 nmccollum joined #salt
20:37 ronnix_ joined #salt
20:40 pipps joined #salt
20:42 ronnix_ joined #salt
20:44 Tanta joined #salt
20:51 nickabbey joined #salt
20:54 pipps joined #salt
20:54 Deliant joined #salt
20:55 teclator joined #salt
20:58 tercenya joined #salt
20:58 dstensnes question: Using the salt-master from debian jessie-backports. Why does the salt-master try to execute dmidecode? Shouldn't salt-master just focus on coordinating the minions?
20:58 dstensnes it seems to be running /bin/ip and a lot of other commands as well
20:59 dstensnes seems to be populating grains
20:59 dstensnes is this intended behavior for the salt-master?
20:59 mritchie joined #salt
21:00 teclator joined #salt
21:02 abednarik joined #salt
21:04 Miouge joined #salt
21:05 teclator_ joined #salt
21:06 aarontc joined #salt
21:14 edrocks joined #salt
21:16 stooj joined #salt
21:17 amy_ joined #salt
21:17 DanyC joined #salt
21:18 mavhq joined #salt
21:20 lord2y joined #salt
21:20 Inveracity to my understanding, yes, this is very much intended behavior, if you care you can look through the code, you can see exactly what commands are being run https://github.com/saltstack/salt/tree/v2016.11.1/salt/grains
21:22 jhauser joined #salt
21:23 druonysus_ left #salt
21:25 cscf what's the command line option to totally hide Clean states when running? something with --filter?
21:26 dyasny joined #salt
21:28 teclator joined #salt
21:28 Inveracity cscf, possibly --state-output=terse ?
21:28 cscf Inveracity, that does one line per state
21:28 DanyC joined #salt
21:29 cscf I would like no output for Clean besides the summary number, and full output for Change and Failure
21:31 CimmX joined #salt
21:32 tercenya joined #salt
21:32 CimmX hello all.    Does anyone know if salt-cloud can be run while behind an outbound proxy?
21:32 Inveracity cscf, I'm unaware of output options that does that, sorry
21:32 cscf Yeah, me too...
21:34 _KaszpiR_ joined #salt
21:36 Inveracity however, I wonder if it would be difficult to write a custom one that does that though
21:38 jas02 joined #salt
21:39 hop joined #salt
21:40 cscf I was wondering that too, but I have enough on my plate atm.
21:43 seanz joined #salt
21:47 nickabbey joined #salt
21:47 stooj joined #salt
21:49 Derailed joined #salt
21:52 Inveracity has anyone here set up salt-cloud with GCE (google compute engine). I followed the docs, but when I try to create my first instance it gives me a url and asks me to login and get a code to enter in the prompt
21:52 Inveracity the docs make no mention of this and I'm stuck there
21:52 hasues joined #salt
21:53 hasues left #salt
21:54 Inveracity I set up a service account, downloaded the .json and the .p12 file, convert the .p12 to a .pem, set up the cloud.provider conf and cloud.profile conf, and there are no error messages in the master log
21:55 Inveracity oh and, opening the url in a browser it tells me I can't use a browser to get a code
21:59 alvinstarr1 joined #salt
22:04 pipps joined #salt
22:05 xbglowx joined #salt
22:05 madboxs joined #salt
22:06 pipps99 joined #salt
22:10 stooj joined #salt
22:10 DanyC joined #salt
22:13 tkharju joined #salt
22:20 sfxandy joined #salt
22:21 DanyC joined #salt
22:22 pipps99 joined #salt
22:32 sfxandy joined #salt
22:35 fhh joined #salt
22:38 DanyC joined #salt
22:47 dstensnes Inveracity: well, i'm trying to run salt-master as a non-root user, and it keeps complaining
22:48 dstensnes which is not so strange, because dmidecode does not have permission to read the DMI without root
22:53 DanyC joined #salt
22:54 stooj joined #salt
22:55 whytewolf dstensnes: from this ticket it looks like the dmidecode messages are not that big of issue. and were supposed to be downgraded to info ... https://github.com/saltstack/salt/issues/5249
22:55 saltstackbot [#5249][MERGED] salt-master should not run as root anymore | We're up to 0.15.1, and the PPA at least still ships a config that runs salt-master as root....
22:55 tercenya joined #salt
22:55 whytewolf very old ticket. so who knows if something migrated  since then
22:55 dstensnes whytewolf: but it seems to be trying to run it quite often
22:56 dstensnes shouldn't it just stop trying to run it?
22:56 dstensnes but what i'm curious about is why it tries to build grains in the master itself
22:56 whytewolf because the master has master grains
22:57 dstensnes okay
22:57 dstensnes i haven't played around with salt stack a lot
22:57 dstensnes i'm just trying to figure out why it's built like this
22:57 dstensnes hope I don't annoy you too much with these questions :)
22:58 dstensnes beer with me
22:58 whytewolf nope... thats why we are here...
22:58 dstensnes what are these master grains?
22:58 dstensnes i don't think i have encountered those yet
22:58 whytewolf personally never used them so have no idea
22:58 whytewolf but i believe they are mostly used for things in runners
23:03 stooj joined #salt
23:06 madboxs joined #salt
23:10 riftman joined #salt
23:11 chutzpah joined #salt
23:18 t_o joined #salt
23:20 xbglowx joined #salt
23:20 mosen joined #salt
23:21 t_o Hi, I seem to be missing something in the docs, trying to do optional pip install ala 'pip install thing[optional]' and coming up with nada. Anyone know what I'm missing?
23:23 whytewolf what nada means?
23:24 whytewolf please gist up what you are currently trying
23:25 t_o nada means nothing :)
23:26 whytewolf i know what nada means. which is precisly the amount of info you gave to figure out what is going wrong ;)
23:27 t_o nice.
23:27 t_o https://gist.github.com/towens/e9c8ce60e0406503dab626b00603d6f8
23:27 t_o it's pretty simple.
23:28 whytewolf getting errors with that? [most likely something about hive not being a valid function. or something like that]
23:29 whytewolf iirc pip.install doesn't like [] in the name
23:30 xbglowx joined #salt
23:30 ponyofdeath joined #salt
23:30 petong joined #salt
23:30 t_o If i pip install airflow[hive] in a shell, it works 100% of the time. It's generally how you get option packages specified in setuptools.
23:31 whytewolf well yes. i didn't say that it was a problem with pip.
23:31 t_o I just haven't seen that syntax used in Salt, or an alternate syntax in the docs.
23:32 whytewolf but you might also have to put it in ''
23:32 t_o ah, you're saying the salt module doesn't like pip install []. Got it.
23:32 whytewolf as [text] actually means something in yaml
23:32 dendazen joined #salt
23:32 t_o Yeah that's a good point.
23:35 t_o I'll try the single quotes, see where that leads.
23:35 whytewolf I'm trying to see if there is a bug report for pip extra packages
23:37 bocaneri joined #salt
23:39 pipps joined #salt
23:40 jas02 joined #salt
23:41 t_o Yeah I didn't see any obvious ones searching GitHub.
23:41 whytewolf humm just testing and running salt-call pip.install 'airflow[hive]' worked on the cli.
23:44 t_o That's cool. I never ran it via salt-call, just through the sls. I guess finding the translation is where I'm heading.
23:48 whytewolf humm. there is a minor thing that it might not be able to detect when airflow[hive] is installed since salt will look for airflow[hive] in pip and it won't exist even if installed correctly
23:51 t_o That would be a problem. I'll bang on it a bit more, I have coworker giving me the "10 mins till the coffee shop closes" look. Thanks for weighing in on it :)
23:52 jgarr anyone ever have trouble syncing salt yum repos? I'm using reposync and just get '[Errno 256] No more mirrors to try.' on every package
23:55 raspado joined #salt
23:59 jgarr also, trying to move my salt master to a new system without re-keying all the minions. I tried rsyncing /etc/salt but on a couple test nodes it still shows the master pub key has changed. Something else I need to do?

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