I'm manually adding yum-utils in my RedHat installs as I am performing a minimal install. I figured that this was my fault for trying to install as little as possible. It might make some sense to document that dependency in the yum module page though.
Adam On Wednesday, February 19, 2014 5:03:18 AM UTC-8, Michael DeHaan wrote: > > +1 > > Also, what (remote) OS is this? > > We'd have this discussion before, where yum-utils we were pretty sure was > only excluded in @core installs. That might not b e true though -- need > to check. > > I have no problem making the yum module self-add yum-utils if not already > there if it resolves problems in those environments as it should be there > anyway. > > > > > On Wed, Feb 19, 2014 at 6:17 AM, Walid <walid....@gmail.com > <javascript:>>wrote: > >> I am away from my Ansible machine and test, however in my playbook the >> first thing i do is update yum, and yum-utils to the latest update as i >> had similar issues with older releases. >> >> >> On 19 February 2014 11:59, Marc Trudel <mtr...@wizcorp.jp >> <javascript:>>wrote: >> >>> Quick note. My playbooks break if I do not have repoquery... the code >>> seems to suggest this is optional, but I just found a case, for instance, >>> where checking for an already installed package gave me a recursion error, >>> while another fresh install failed on "failed to parse: >>> SUDO-SUCCESS-whatever" >>> >>> >>> On Wednesday, February 19, 2014 5:22:07 PM UTC+9, Marc Trudel wrote: >>>> >>>> I think I found the issue - seems to be related to repoquery >>>> >>>> Following tests were done as suggested with the test-module on the host >>>> >>>> With repoquery: >>>> real 0m21.014s >>>> user 0m4.094s >>>> sys 0m1.337s >>>> >>>> Without repoquery: >>>> real 0m8.130s >>>> user 0m1.914s >>>> sys 0m0.449s >>>> >>>> I guess it is then no longer an ansible issue (never really were), but >>>> has anyone experienced this in the past? >>>> >>>> On Wednesday, February 19, 2014 10:22:54 AM UTC+9, Michael DeHaan wrote: >>>>> >>>>> ./hacking/test-module in the checkout is pretty useful for things like >>>>> this. >>>>> >>>>> Do a checkout on a machine with yum and even inserting some basic >>>>> print statements or logging could be a useful start to find out what >>>>> functions or commands are taking the most time. >>>>> >>>>> >>>>> On Tue, Feb 18, 2014 at 7:47 PM, Marc Trudel <mtr...@wizcorp.jp>wrote: >>>>> >>>>>> I'll remove fastest-mirror, it indeed looks like it made things >>>>>> slower (this is in fact what I was adding to my stack as an experiment >>>>>> to >>>>>> make YUM faster - at first I thought it was purely YUM-related issue). >>>>>> >>>>>> I will try to find some information as to how to benchmark, but would >>>>>> you have any recommendation as to how I should proceed? >>>>>> >>>>>> >>>>>> On Tuesday, February 18, 2014 9:20:58 PM UTC+9, Michael DeHaan wrote: >>>>>> >>>>>>> I see from the above that you said 50 seconds above and I misread. >>>>>>> In your case this is definitely slower than the actual command by a >>>>>>> very >>>>>>> decent margin. I'm still not seeing this. >>>>>>> >>>>>>> If you can benchmark where it is spending it's time that would be >>>>>>> appreciated. >>>>>>> >>>>>>> I noticed you were installing fastest-mirror though, which you >>>>>>> probably don't want to do :) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 18, 2014 at 7:06 AM, Michael DeHaan >>>>>>> <mic...@ansible.com>wrote: >>>>>>> >>>>>>>> It runs some extra ops to ensure it doesn't need to run >>>>>>>> change-inducing commands up front. >>>>>>>> >>>>>>>> However I would disagree that 20% is "much slower". >>>>>>>> >>>>>>>> Do make sure you have "fastest mirror" disabled, BTW, the module >>>>>>>> usually isn't faster. >>>>>>>> >>>>>>>> Local mirroring is also always a fantastic idea! Check out "yum >>>>>>>> reposync". >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Feb 18, 2014 at 6:33 AM, Marc Trudel <mtr...@wizcorp.jp>wrote: >>>>>>>> >>>>>>>>> I notice that --enablerepos should be --enablerepo - no worries, >>>>>>>>> I tested with the right flags. >>>>>>>>> >>>>>>>>> Also, just to make sure its not ssh related, I also tried: >>>>>>>>> >>>>>>>>> time ssh 123.1322.0.453 "sudo yum install yum-presto >>>>>>>>> yum-fastestmirror yum-fast-downloader --enablerepo=personalrepo, >>>>>>>>> rpmforge" >>>>>>>>> >>>>>>>>> Which gave me comparable times as with running it straight on the >>>>>>>>> server. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tuesday, February 18, 2014 8:28:23 PM UTC+9, Marc Trudel wrote: >>>>>>>>>> >>>>>>>>>> The yum module looks heaps slower than the actual yum command. >>>>>>>>>> >>>>>>>>>> For instance, when I check if a set of three packages are >>>>>>>>>> installed in ansible (timestamps are mine) >>>>>>>>>> >>>>>>>>>> [19:44:05] TASK: [common | Install presto, fastdownloader and >>>>>>>>>>> yum-fast-downloader] ******* >>>>>>>>>>> [19:44:56] ok: [someserver] => (item=yum-presto,yum-fastestmi >>>>>>>>>>> rror,yum-fast-downloader) >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> But if I run: >>>>>>>>>> >>>>>>>>>> time yum install yum-presto yum-fastestmirror yum-fast-downloader >>>>>>>>>>> --enablerepos=personalrepo,rpmforge >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It runs in: >>>>>>>>>> >>>>>>>>>> First time: >>>>>>>>>>> real 0m7.956s >>>>>>>>>>> user 0m0.829s >>>>>>>>>>> sys 0m0.190s >>>>>>>>>>> >>>>>>>>>>> Second time: >>>>>>>>>>> real 0m5.031s >>>>>>>>>>> user 0m1.136s >>>>>>>>>>> sys 0m0.269s >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> If I run the previous command from ansible: >>>>>>>>>> >>>>>>>>>> [20:27:21] TASK: [common | Install presto, fastdownloader and >>>>>>>>>>> yum-fast-downloader] ******* >>>>>>>>>>> [20:27:28] changed: [someserver] >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Any reasons why ansible's yum module run are that much slower? I >>>>>>>>>> have tested on 1.4.5. >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Ansible Project" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to ansible-proje...@googlegroups.com. >>>>>>>>> To post to this group, send email to ansible...@googlegroups.com. >>>>>>>>> >>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Ansible Project" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to ansible-proje...@googlegroups.com. >>>>>> To post to this group, send email to ansible...@googlegroups.com. >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>> >>>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Ansible Project" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to ansible-proje...@googlegroups.com <javascript:>. >>> To post to this group, send email to >>> ansible...@googlegroups.com<javascript:> >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ansible-proje...@googlegroups.com <javascript:>. >> To post to this group, send email to ansible...@googlegroups.com<javascript:> >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
