Project

General

Profile

Actions

Bug #9185

closed

Deleting a network interface breaks all puppet agent syncing

Added by Mark Chaney over 9 years ago. Updated over 9 years ago.

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

Description

Ive tried this in 1.7.1 and 1.7.2, but if I delete a network interface in foreman, I can no longer sync any of my dedicated servers with the puppet agent. the odd thing though is that my lxc guests can sync just fine. This is the error i get:

############################

root@stor1:~# puppet agent -t --verbose
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 400 on SERVER: Failed to find stor1.cloud.foo.com via exec: Execution of '/etc/puppet/node.rb stor1.cloud.foo.com' returned 1: --- false
...
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node stor1.cloud.foo.com: Failed to find stor1.cloud.myiacon.com via exec: Execution of '/etc/puppet/node.rb stor1.cloud.foo.com' returned 1: --- false
...
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

#############################

I have restored my system from backup multiple times with different scenarios and this is always the common thing that triggers it.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #9231: Exception message missing when ENC fails to renderClosedDavid Davis02/05/2015Actions
Actions

Also available in: Atom PDF