Project

General

Profile

Actions

Bug #21988

open

After signing certificate of new agent, host created name is real fqdn instead of certname

Added by Christian P over 6 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

After signing certificate of new agent, new host is created with name = <real fqdn> instead of certname.

ubuntu 16.04 client and server
Foreman 1.16

In node:

root@srv-03:~# hostname -f
srv-03.c.gcloud-sig.internal
nano /etc/puppetlabs/puppet/puppet.conf
[agent]
certname = srv-03.mydomain.com
server = <mi server>

In "Smart Proxy > Certificates" I see new certificate with "Certificate Name = srv-03.mydomain.com"
This is rigth so I sign it.

But the in "Hosts -> All Host", new host appears with "Name = srv-03.c.gcloud-sig.internal"

The problem is that in client when I run test I get the following error:

root@srv-03:~# /opt/puppetlabs/bin/puppet agent --test
Info: Caching certificate for srv-03.mydomain.com
Info: Caching certificate_revocation_list for ca
Info: Caching certificate for srv-03.mydomain.com
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 500 on SERVER: Server Error: Failed to find srv-03.mydomain.com via exec: Execution of '/etc/puppetlabs/puppet/node.rb srv-03.mydomain.com' returned 1: 
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for srv-03.mydomain.com
Info: Applying configuration version '1513342336'

To fix this I need to manually change hostname in registered host to srv-03.mydomain.com.
After that averithings works fine.

Actions #1

Updated by Anonymous over 6 years ago

  • translation missing: en.field_release deleted (332)
Actions

Also available in: Atom PDF