Continually get WARNING: The following packages cannot be authenticated!

[gwagner]

No matter what i do, i will get WARNING: The following packages cannot be authenticated! for both graylog2-server and graylog2-web

[grafjo]

@gwagner maybe you want to provide more information?

[gwagner]

When i follow the instructions listed this page:

https://www.graylog2.org/resources/documentation/setup/puppet

the very last example:

# Graylog2
  class { 'graylog2::repo':
    version => '0.92'
  } ->
  class { 'graylog2::server':
    password_secret            => '16BKgz0Qelg6eFeJYh8lc4hWU1jJJmAgHlPEx6qkB',
    root_password_sha2         => '8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918',
    elasticsearch_cluster_name => 'graylog2',
    require                    => [
      Class['graylog2::repo'],
    ],
  } ->
  class { 'graylog2::web':
    application_secret => '16BKgz0Qelg6eFeJYh8lc4hWU1jJJmAgHlPEx6qkBa2cQQTUG',
    require            => Class['graylog2::server'],
  }

The repo is consistently throwing a WARNING: The following packages cannot be authenticated! error which is making it impossible to install anything.

I get a 50% success rate installing graylog2-server and a 0% success rate installing graylog2-web

[grafjo]

@gwagner rpm or deb based?

[gwagner]

sorry, deb based on ubuntu 14.04

[grafjo]

I'm not sure what you're doing ... with mod 'graylog2/graylog2', '0.9.1' and the manifest there was an The password_secret parameter is too short. error ... after fixing this issue it was working for me.

See https://github.com/grafjo/vagrant-puppetdev/tree/graylog2_13

[joschi]

WARNING: The following packages cannot be authenticated!

@gwagner This looks like the GnuPG key used for signing our packages hasn't been imported into your keyring. Usually this is added by our setup packages (e. g. https://packages.graylog2.org/repo/packages/graylog2-0.92-repository-ubuntu14.04_latest.deb).

Please check that there's a key for packages@torch.sh available in your keyring.

[grafjo]

@joschi I guess manifests/repo/debian.pp is handling this!

[gwagner]

I think this can be closed. I believe the image i was using had a stale apt package cache which was causing a dependency to not be found oddly causing this package to error out on install. Once i did an apt-get clean && apt-get clean then everything started to work again.