(and then you'll need to restart the server) On Tuesday, September 20, 2022 at 7:38:45 AM UTC-7 Ben Ford wrote:
> On the Puppet server, you will need either both of these parameters > set (when using Satellite for classification), or both of them unset (when > not using Satellite for classification). > > > *external_nodes = /etc/puppetlabs/code/node.rbnode_terminus = exec* > > > > > On Thursday, September 15, 2022 at 9:15:51 AM UTC-7 acia...@icloud.com > wrote: > >> Hello all, >> >> my apologies if this topic is already discussed. I try to research it but >> I didn't find any solution. >> >> I have the following infrastructure: >> >> One RHEL Satellite 6 with several capsule server around our datacentres. >> I implement puppet and ansible correctly, sync the puppet environment >> with rsync (the RHEL Sync doesn't work). >> >> I moved to RHEL satellite 6.11 (where they remove the puppet support, but >> still in the code). I install again puppet on all server. >> On the principal satellite server works perfectly, but on capsule servers >> not. >> >> [root@am-sv-satcap02 opt]# puppet agent -t >> Info: Using environment 'production' >> Info: Retrieving pluginfacts >> Info: Retrieving plugin >> Error: Could not retrieve catalog from remote server: Error 500 on >> SERVER: Server Error: Failed when searching for node >> am-sv-satcap02.linux.netops.local: You must set the 'external_nodes' >> parameter to use the external node terminus >> Warning: Not using cache on failed catalog >> Error: Could not retrieve catalog; skipping run >> [root@am-sv-satcap02 opt]# >> >> Some, can help me to sort out of this problem? >> >> All the best >> >> Alex >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/dce05a05-a9f1-48a1-9d1b-00a146d75e60n%40googlegroups.com.
