On BDA V4.11 and Higher Node 1 Recommission Fails Due to a Puppet Corruption After Node 1 Migration
(Doc ID 2530415.1)
Last updated on MARCH 12, 2021
Applies to:Big Data Appliance Integrated Software - Version 4.11.0 and later
On BDA V4.11 and higher a Node 1 recommission may fail due to a puppet corruption on Node 1 after Node 1 has been migrated to another host. Node 1 recommission may follow Node 1 migration if the node is being migrated to take advantage of newer hardware for example.
After Node 1 is successfully migrated to another host, running Node 1 recommission fails with:
Following, Troubleshooting Mammoth Errors: "ERROR: Puppet agent on node bdanode0x is not reachable" (Doc ID 2164227.1), identifies that puppet is corrupted on Node 1.
1. Running "puppet agent -t' reports:
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet://<HOSTNAME1>-master.<DOMAIN>/plugins: getaddrinfo: Name or service not known
getaddrinfo: Name or service not known
Error: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: getaddrinfo: Name or service not known
2. Running "puppet kick --ping --host <HOSTNAME1>.<DOMAIN> raises:
<HOSTNAME1>.<DOMAIN> finished with exit code 2
3. The puppet master is still running on Node 1 and it is also running on the node where Node 1 was migrated to.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document