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

Authentication issue when attempting to install sensu package #444

Closed
jlk opened this issue Nov 13, 2015 · 0 comments
Closed

Authentication issue when attempting to install sensu package #444

jlk opened this issue Nov 13, 2015 · 0 comments

Comments

@jlk
Copy link
Contributor

jlk commented Nov 13, 2015

Howdy! When attempting to install sensu on Ubuntu via the sensu-puppet module, it's failing as the repository data hasn't been updated between the apt key being added and the attempt to install the sensu package:

==> default:
==> default: Error: /Stage[main]/Sensu::Package/Package[sensu]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install sensu' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following NEW packages will be installed:
==> default:   sensu
==> default: 0 upgraded, 1 newly installed, 0 to remove and 125 not upgraded.
==> default: Need to get 21.2 MB of archives.
==> default: After this operation, 60.8 MB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default:   sensu
==> default: E: There are problems and -y was used without --force-yes

Relevant part of my manifest looks like this:

class { 'sensu':
  rabbitmq_password  => 'sensu',
  server             => true,
  install_repo       => true,
  repo_source        => 'http://repositories.sensuapp.org/apt',
  repo_key_source    => 'http://repositories.sensuapp.org/apt/pubkey.gpg',
  repo_key_id        => '',
  api                => true,
  require            => Package['ruby-dev'];
}

Looks like adding a few lines in manifests/repo/apt.pp would straighten this out. Will tinker with that idea and submit a pull request if I get it working...

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

1 participant