Jira (PUP-10626) puppet node deactivate and external CA - cert revocation can't be disabled

[Steve Traylen (Jira)]

Title: Message Title

Steve Traylen created an issue   Puppet / PUP-10626 puppet node deactivate and external CA - cert revocation can't be disabled Issue Type: Bug Affects Versions: PUP 6.15.0 Assignee: Unassigned Created: 2020/08/19 2:08 AM Priority: Normal Reporter: Steve Traylen Puppet Version: 6.15.0 Puppet Server Version: 6.11.1 OS Name/Version: CentOS 7 When using an external certificate authority it's assumed that a working puppet-ca endpoint is not required. However `puppet node deactivate` always attempts a revocation and fails as a result.   Desired Behavior: puppet node deactivate foo.example.org should delete node from PDB as is the case with puppetdb 5 Actual Behavior: With puppet 6 puppet node deactivate b7g19n0014.cern.ch Error: Request to https://puppet:8140/puppet-ca/v1 failed after 0.004 seconds: Failed to open TCP connection to puppet:8140 (getaddrinfo: Name or service not known) Wrapped exception:   we have no configuration for ca_server so default puppet is chosen. For info we are running pupetserver with: cat /etc/puppetlabs/puppetserver/services.d/ca.cfg puppetlabs.services.ca.certificate-authority-disabled-service/certificate-authority-disabled-service Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369661.1597828121000.18793.1597828140259%40Atlassian.JIRA.