Bug #37817
closed
Custom certificates will override server CA with default CA on foreman-proxy-content scenario
Added by Eric Helms 7 months ago.
Updated 6 months ago.
- Status changed from New to Ready For Testing
- Assignee set to Eric Helms
- Pull request https://github.com/theforeman/puppet-certs/pull/463 added
- Category set to Foreman modules
- Triaged changed from No to Yes
- Found in Releases 3.11.0 added
This was introduced in commit:433dadc5ec41c2477fc6a04e056ca061fd818980 which landed in puppet-certs 18.0.0. That was first shipped in foreman-installer 3.11.0.
- Fixed in Releases 3.13.0 added
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman-installer/pull/975 added
- Target version set to 3.11.3
- Fixed in Releases 3.12.0 added
- Fixed in Releases deleted (
3.13.0)
- Target version changed from 3.11.3 to 3.11.4
- Pull request https://github.com/theforeman/puppet-certs/pull/466 added
- Pull request https://github.com/theforeman/foreman-installer/pull/987 added
- Priority changed from Normal to Immediate
- Fixed in Releases 3.11.4 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Added by Eric Helms 7 months ago
Fixes #37817: Only copy server CA in build root if generate is true
Fixes: 433dadc5ec41 ("Copy the server CA certificate with file resource")