Project

General

Profile

Bug #18313

Upgrading to puppet4 fails as apache conf still refers to /var/lib/puppet/ssl

Added by Lukas Pramuk over 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Upgrading to puppet4 fails as httpd cannot start since /etc/httpd/conf.d/25-puppet.conf still refers to /var/lib/puppet/ssl

# foreman-installer -S katello --upgrade-puppet
...

Upgrade Step: restart_services...
...
Redirecting to /bin/systemctl start  httpd.service
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.

Redirecting to /bin/systemctl start  foreman-tasks.service

Some services failed to start: httpd

Upgrade step restart_services failed. Check logs for more information.

# journalctl -u httpd
Jan 30 16:43:59 <FQDN> systemd[1]: Stopped The Apache HTTP Server.
Jan 30 16:48:23 <FQDN> systemd[1]: Starting The Apache HTTP Server...
Jan 30 16:48:23 <FQDN> httpd[3781]: AH00526: Syntax error on line 34 of /etc/httpd/conf.d/25-puppet.conf:
Jan 30 16:48:23 <FQDN> httpd[3781]: SSLCertificateFile: file '/var/lib/puppet/ssl/certs/<FQDN>.pem' does not exist or is empty

# grep /var/lib/puppet/ssl /etc/httpd/conf.d/25-puppet.conf
  SSLCertificateFile      "/var/lib/puppet/ssl/certs/<FQDN>.pem" 
  SSLCertificateKeyFile   "/var/lib/puppet/ssl/private_keys/<FQDN>.pem" 
  SSLCertificateChainFile "/var/lib/puppet/ssl/ca/ca_crt.pem" 
  SSLCACertificateFile    "/var/lib/puppet/ssl/ca/ca_crt.pem" 
  SSLCARevocationFile     "/var/lib/puppet/ssl/ca/ca_crl.pem" 

But the ssl files were moved to /etc/puppetlabs/puppet/ssl

History

#1 Updated by Justin Sherrill over 5 years ago

  • Legacy Backlogs Release (now unused) set to 222

#2 Updated by Justin Sherrill almost 5 years ago

  • Legacy Backlogs Release (now unused) deleted (222)

#3 Updated by Eric Helms almost 5 years ago

  • Status changed from New to Resolved
  • Legacy Backlogs Release (now unused) set to 166

This has been resolved in latest releases please upgrade and re-open if you hit the issue again.

Also available in: Atom PDF