O Puppet não consegue encontrar o arquivo do módulo

2

Eu criei um servidor de fantoches (5.0.0) usando o docker-compose exemplo e trouxe com sucesso seis clientes (usando o agente fantoche fornecido pela debian).

Embora eu possa fornecer arquivos com conteúdo bruto, por exemplo,

file { '/etc/systemd/timesyncd.conf':
  ensure => present,
  content => "[Time]\nNTP=time.xxx.net\n",
  notify => Service["systemd-timesyncd.service"]
}

fornecer os arquivos pela fonte não funciona:

file { "/etc/default/grub":
  ensure => present,
  source => "puppet:///modules/debian-noquiet-grub/etc-default-grub",
}

O erro dos clientes com

Error: /Stage[main]/Loudgrub/File[/etc/default/grub]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/debian-noquiet-grub/etc-default-grub

e o servidor com

2017-08-24 13:40:21,582 INFO  [puppetserver] Puppet Not Found: Could not find file_metadata modules/debian-noquiet-grub/etc-default-grub
10.161.xxx.zzz - - - 24/Aug/2017:13:40:21 +0000 "GET /puppet/v3/file_metadata/modules/debian-noquiet-grub/etc-default-grub?environment=production&links=manage&checksum_type=md5&source_permissions=ignore HTTP/1.1" 404 132 10.161.xxx.zzz 10.161.xxx.zzz 8140 6

As localizações dos arquivos são (dentro do contêiner Docker):

/etc/puppetlabs/code/environments/production/manifests/site.pp (site.pp)
/etc/puppetlabs/code/environments/production/modules/debian-noquiet-grub/files/etc-default-grub (the text file)
/etc/puppetlabs/code/environments/production/modules (first element of puppet config print modulepath --section master --environment production)

O que causa esse erro e como corrigi-lo?

    
por Marco Schuster 24.08.2017 / 15:57

1 resposta

2

De acordo com os documentos (e os comentários):

Module names should only contain lowercase letters, numbers, and underscores, and should begin with a lowercase letter. [...]

    
por 24.08.2017 / 16:51