This also happened when running an external role (from Ansible Galaxy) I had to uncomment line 7 of https://github.com/bcoca/oracle7java/blob/54d5fd3a56d6b2d4186c5c8fabb24b6f42a1f731/tasks/main.yml to ensure the apt-key was also installed, as the previous apt-repository command didn't do so.
This would appear to be a regression in 1.5.3 at this stage ? Ben On Monday, 17 March 2014 11:41:54 UTC+11, Ben Turner wrote: > > Addenda: > > It seems I had to ALSO add in the key manually, as the apt_repository > command had not done that for me - this isn't what I'd expected from a PPA ? > > - name: Add brightbox repository key > > > apt_key: url=" > http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0xF5DA5F09C3173AA6 > " > > This was required, along with the apt update_cache command. Still puzzled > why. > > Regards, > Ben > > On Monday, 17 March 2014 11:06:48 UTC+11, Ben Turner wrote: >> >> I'm running Ansible 1.5.3 on Ubuntu 12.04 LTS >> >> I've got the following two lines in one of my roles: >> >> - name: Add brightbox repository >> >> >> apt_repository: repo=ppa:brightbox/ruby-ng >> >> >> >> - name: Install brightbox ruby >> >> >> apt: pkg=ruby1.9.3 state=latest >> >> >> >> This outputs the following (Note: abbreviated. Full error log shown >> below): >> >> failed: [ec2-54-253-255-54.ap-southeast-2.compute.amazonaws.com] => >> (item=ruby1.9.3) => {"failed": true, "item": "ruby1.9.3"} >> stderr: E: There are problems and -y was used without --force-yes >> ... >> WARNING: The following packages cannot be authenticated! >> libruby1.9.1 ruby1.9.1 ri1.9.1 ruby1.9.1-dev ruby1.9.1-examples >> libruby1.9.1-dbg ruby1.9.1-full ruby1.9.3 >> >> This, I believe, is usually a sign that "apt-get update" has not been run >> - indeed going onto the box, manually running apt-get update, and then >> rerunning my playbook causes it to install successfully. >> >> Thinking it might be a bug in the apt_repository code or documentation, I >> bought up a new copy of the server and changed the apt_respository to >> include the (default) value of true for the update_cache attribute: >> >> - name: Add brightbox repository >> >> >> apt_repository: repo=ppa:brightbox/ruby-ng update_cache=yes >> >> This made no difference. But when I added update_cache to the apt command >> instead, it now worked: >> >> - name: Install brightbox ruby >> >> >> apt: pkg=ruby1.9.3 state=latest update_cache=yes >> >> >> >> So I'm a little puzzled as to why the apt_repository command doesn't >> update the apt index in time to fix the following install task, but the apt >> take does manage to update the index in time ? >> Obviously, I'd rather not update my apt index before every run on the apt >> module, and logically the only reason I am updating it is for the new >> repository I've added, so would prefer the apt_repository task to own that >> responsibility. >> >> Regards, >> Ben >> >> FULL ERROR TRACE >> ================== >> >> failed: [ec2-54-253-255-54.ap-southeast-2.compute.amazonaws.com] => >> (item=ruby1.9.3) => {"failed": true, "item": "ruby1.9.3"} >> stderr: E: There are problems and -y was used without --force-yes >> >> stdout: Reading package lists... >> Building dependency tree... >> Reading state information... >> The following packages were automatically installed and are no longer >> required: >> libgudev-1.0-0 linux-headers-3.2.0-54 gir1.2-gudev-1.0 openjdk-7-jre-lib >> linux-headers-3.2.0-54-virtual >> Use 'apt-get autoremove' to remove them. >> The following extra packages will be installed: >> libgoogle-perftools-dev libgoogle-perftools0 libreadline5 libruby1.9.1 >> libruby1.9.1-dbg libtcmalloc-minimal0 libunwind7 ri1.9.1 ruby1.9.1 >> ruby1.9.1-dev ruby1.9.1-examples ruby1.9.1-full >> Suggested packages: >> graphviz ruby-switch >> The following NEW packages will be installed: >> libgoogle-perftools-dev libgoogle-perftools0 libreadline5 libruby1.9.1 >> libruby1.9.1-dbg libtcmalloc-minimal0 libunwind7 ri1.9.1 ruby1.9.1 >> ruby1.9.1-dev ruby1.9.1-examples ruby1.9.1-full ruby1.9.3 >> 0 to upgrade, 13 to newly install, 0 to remove and 0 not to upgrade. >> Need to get 14.1 MB of archives. >> After this operation, 48.3 MB of additional disk space will be used. >> WARNING: The following packages cannot be authenticated! >> libruby1.9.1 ruby1.9.1 ri1.9.1 ruby1.9.1-dev ruby1.9.1-examples >> libruby1.9.1-dbg ruby1.9.1-full ruby1.9.3 >> >> msg: 'apt-get install 'ruby1.9.3' ' failed: E: There are problems and -y >> was used without --force-yes >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/882b827f-c0d1-414b-a59c-9f6898d7e080%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
