Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import of new gpg key from Repo fails with 401 Unauthorized #151

Open
martinseener opened this issue Jan 23, 2019 · 7 comments
Open

Import of new gpg key from Repo fails with 401 Unauthorized #151

martinseener opened this issue Jan 23, 2019 · 7 comments

Comments

@martinseener
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.5.2
  • Ruby: ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]
  • Distribution: Debian Jessie
  • Module version: 313ffb6

How to reproduce (e.g Puppet code you use)

We use the module to install Grafana and manage it. Today we updated the module to the latest master which includes the DEB Repo URL fix and we see 401 Unauthorized while adding the new gpg key from the URL.

What are you seeing

Error: 401 Unauthorized for https://packages.grafana.com/gpg.key Error: /Stage[main]/Grafana::Install/Apt::Source[grafana]/Apt::Key[Add key: 4E40DDF6D76E284A4A6780E48C8C34C524098CB6 from Apt::Source grafana]/Apt_key[Add key: 4E40DDF6D76E284A4A6780E48C8C34C524098CB6 from Apt::Source grafana]/ensure: change from absent to present failed: 401 Unauthorized for https://packages.grafana.com/gpg.key

What behaviour did you expect instead

I can download this gpg key file and import it manually on the machine. Then the puppet run works without any problems also on consecutive runs.

@bastelfreak
Copy link
Member

mhm strange. The link works for me as well. Do you require a proxy or something similar, and puppet isn't aware of it?

@thaiphv
Copy link

thaiphv commented Jan 28, 2019

I had the same problem.

@martinseener
Copy link
Author

Hi @bastelfreak,
we had apt-cache until last year but this has already gone and there is no other proxy in between. I'm still not sure why this happened, especially because the manual adding of the key worked. I'll try to remove the key from apt again and let puppet run and see if it happens again. Nevertheless, give me one or two days to figure it out. I'll report back.

@martinseener
Copy link
Author

@thaiphv while you also had it, the problem might be within the apt puppet module. maybe packagecloud does not allow the user-agent or something like this....i'll try to replicate the issue

@thaiphv
Copy link

thaiphv commented Jan 30, 2019

I think it's related to the apt module that I'm using. It's pretty outdated. I'll try to reproduce it after upgrading the module to the latest version.

@dhoppe
Copy link
Member

dhoppe commented Mar 26, 2019

@thaiphv Is there any news on this issue? Which version of the apt module did you use?

@promasu
Copy link

promasu commented Mar 17, 2023

I think this issue can be closed as the URLs have been reworked by Grafana Labs and it's stale for almost four years now

promasu added a commit to promasu/puppet-grafana that referenced this issue Mar 17, 2023
promasu added a commit to promasu/puppet-grafana that referenced this issue Mar 17, 2023
promasu added a commit to promasu/puppet-grafana that referenced this issue Mar 17, 2023
fixes voxpupuli#278
refs voxpupuli#151

Signed-off-by: Adrian Nöthlich <adrian.noethlich@hadiko.de>
promasu added a commit to promasu/puppet-grafana that referenced this issue Mar 17, 2023
fixes voxpupuli#278
refs voxpupuli#151

Signed-off-by: Adrian Nöthlich <adrian.noethlich@hadiko.de>
promasu added a commit to promasu/puppet-grafana that referenced this issue Mar 19, 2023
fixes voxpupuli#278
refs voxpupuli#151

Signed-off-by: Adrian Nöthlich <adrian.noethlich@hadiko.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants