vagrant-proxyconf: Cannot add PPA: user or team does not exist

Hi there,

I’m currently having problem adding apt repository

After I did vagrant ssh

I ran the following command:

Command: sudo apt-add-repository ppa:ansible/ansible

Output:

Cannot add PPA: ‘ppa:~ansible/ubuntu/ansible’. ERROR: ‘~ansible’ user or team does not exist.

I wonder if I missed anything during configuration?

Thanks a ton!!

Donny

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 2
  • Comments: 18 (1 by maintainers)

Most upvoted comments

I was able to get this to work (in bionic) by manually adding the repo to /etc/apt/sources.list - for xenial it would be: deb http://ppa.launchpad.net/ansible/ansible-2.6/ubuntu xenial main Then you should be able to manually add the key: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 93C4A3FD7BB9C367 However since I’m running WSL I had to use a workaround for the key: curl -sL “http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x93C4A3FD7BB9C367” | sudo apt-key add Hope this helps.

Short googling gives me this. Could you try passing the -E switch for sudo?

On my side, it was a proxy / firewall issue. I was able to add ppa after opening:

  • *.ubuntu.com
  • launchpad.net
  • *.launchpad.net

I was able to get this to work (in bionic) by manually adding the repo to /etc/apt/sources.list - for xenial it would be: deb http://ppa.launchpad.net/ansible/ansible-2.6/ubuntu xenial main Then you should be able to manually add the key: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 93C4A3FD7BB9C367 However since I’m running WSL I had to use a workaround for the key: curl -sL “http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x93C4A3FD7BB9C367” | sudo apt-key add Hope this helps.

Worked for me 👍

Lasts step I had to:

I had the same error and found out python was blocked in the firewall.

It’s solely and completely Ubuntu’s fault and they do have a bug report in regards: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1781917

That cryptic message can arise from various networking malfunction starting from DNS and you name it.