Feature #21730: Add check to verify if any empty CA request files exist on satellite - Foreman Maintain - Foreman

Actions

Copy link

Feature #21730

closed

Add check to verify if any empty CA request files exist on satellite

Added by Kavita Gaikwad over 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Kavita Gaikwad

Category:

Target version:

1.15.6

Difficulty:

Triaged:

Bugzilla link:

1437580

Pull request:

https://github.com/theforeman/foreman_maintain/pull/130

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Description of problem:

Puppet Master Issue / CA issue:

When Satellite have one empty CA file, customer will receive the message according below
---
Failure: ERF50-5345 [Foreman::WrappedException]: Unable to connect ([ProxyAPI::ProxyException]: ERF12-5356 [ProxyAPI::ProxyException]: Unable to get PuppetCA certificates ([RestClient...)
---

Version-Release number of selected component (if applicable):
6.2.8

How reproducible:
100%

Steps to Reproduce:
1. Create one empty file inside "/var/lib/puppet/ssl/ca/requests/test.pem"
2. Execute the command "/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --list --all"

Actual results:
Error
---
[root@satellite6 log]# /usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --list --all
Error: header too long
[root@satellite6 log]#
---

Expected results:
See all certificates

Additional info:

Also, provide a step to delete those empty files.