importing gpg key fails about ansible_role_gitea HOT 7 CLOSED

Did you try the Vagrantscript I was using?

Don't know if there is something specific with the used vm or how vagrant runs ansible here...

I import the key now manually and it works:

Vagrant.configure("2") do |config|

  config.vm.box = "debian/buster64"
  config.vm.provision "shell", inline: <<-SHELL
    apt -y install python-apt   
  SHELL

  config.vm.provision "shell", privileged:false, inline: <<-SHELL
    gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2
  SHELL

  config.vm.provision "ansible" do |ansible|
    ansible.playbook = "playbook.yml"
  end
   config.vm.network "forwarded_port", guest: 3000, host: 8083
end

from ansible_role_gitea.

I hope this will resolve it!

from ansible_role_gitea.

yes, worked

from ansible_role_gitea.

I don't have any experience with vagrant and need some help to reproduce the issue.

I run this ansible role (v2.1.2) at a blank debian buster. (see asciinema recording.)

I used the following package versions:

ansible-playbook --version
ansible-playbook 2.10.8
  config file = None
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible-playbook
  python version = 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]


hostnamectl 
   Static hostname: grmpg
         Icon name: computer-vm
           Chassis: vm
        Machine ID: d72735cff36a41f0a5326f0bb7eb1778
           Boot ID: 4501f9e2bdab4875b1ee09d804278652
    Virtualization: kvm
  Operating System: Debian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.0-13-cloud-amd64
      Architecture: x86-64

but it went through without a problem and spawned a gitea on port 3000. The GPG key import did not cause any problems.

I would like to recreate the poblem and then solve it, but I need more tips to reproduce it. as I said, so far no contact with vagrant.

from ansible_role_gitea.

I am very sorry. I haven't really found the time to get to grips with Vagrantscript and so haven't tried deploying it myself.

You have found a workaround. I think that is good. Theoretically the ansible should do exactly the same.

Do you have any idea why ansible behaves differently than the shell command in the vagrantscript?

from ansible_role_gitea.

Maybe the issue is, that the gpg key is added as root but checked as another user?
ansible is run in vagrant from the vagrant user and I had to import the key as vagrant user.

from ansible_role_gitea.

good idea.

This was not a problem under a native Debian. But who knows if public keys imported as root are also available as non-root...

from ansible_role_gitea.