Bug 1664350 - Failed to start puppetserver while cloning 6.4 database
Summary: Failed to start puppetserver while cloning 6.4 database
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Lucie Vrtelova
URL:
Whiteboard:
Depends On:
Blocks: 1644152
TreeView+ depends on / blocked
 
Reported: 2019-01-08 14:38 UTC by Nikhil Kathole
Modified: 2020-05-01 13:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-01 13:22:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nikhil Kathole 2019-01-08 14:38:43 UTC
Description of problem:
Cloning satellite 6.4 server failed at

TASK [satellite-clone : Run Satellite installer] *******************************
Service[puppetserver]                             : 471/537, 87%, 0.3/s, elapsed: 00:13:33, ETA: 00:03:53
 Systemd start for puppetserver failed!
journalctl log for puppetserver:
-- Logs begin at Sun 2019-01-06 05:38:50 EST, end at Sun 2019-01-06 06:49:07 EST. --
Jan 06 06:48:11 satellite.example.com systemd[1]: Starting puppetserver Service...
Jan 06 06:48:11 satellite.example.com puppetserver[4178]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: Exception in thread "main" java.lang.IllegalArgumentException: Unable to open 'ssl-cert-chain' file: /var/lib/puppet/ssl/ca/ca_crt.pem
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at clojure.lang.Reflector.invokeConstructor(Reflector.java:180)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at puppetlabs.trapperkeeper.services.webserver.jetty9_config$eval33867$get_x509s_from_ssl_cert_chain_pem__33872$fn__33873.invoke(jetty9_config.clj:238)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at puppetlabs.trapperkeeper.services.webserver.jetty9_config$eval33867$get_x509s_from_ssl_cert_chain_pem__33872.invoke(jetty9_config.clj:231)
Jan 06 06:49:07 satellite.example.com puppetserver[4178]: at 


Version-Release number of selected component (if applicable):
satellite-clone 1.3.0 


How reproducible: always


Steps to Reproduce:
1. backup 6.4 satellite using foreman-maintain
2. run satellite-clone to restore backup

Actual results:

Failed to restore satellite db backup.

Expected results:
Successful restore.

Additional info:

Comment 4 John Mitsch 2019-01-08 15:35:03 UTC
Was puppet upgraded from puppet 3 to puppet 4 while on satellite 6.3? Puppet 3 isn't supported on 6.4. The file locations in the error message looks like puppet wasn't upgraded.

I was told the following
"note that you must do (puppet) 3 → 4 in 6.3, in 6.4 it can't upgrade from version 3"

Comment 9 John Mitsch 2019-01-09 16:34:43 UTC
It looks like the puppet server ssl chain filepath is not set correctly, on the reproducer, running "foreman-installer --reset-puppet-server-ssl-chain-filepath" appears to fix the issue.

A fix is required in the installer, but I did open up a PR to satellite-clone to add that option to the installer for 6.4 https://github.com/RedHatSatellite/satellite-clone/pull/350

Nikhil - is there any way you can test out the sat-clone fix with the same workflow?

Comment 10 Nikhil Kathole 2019-01-09 16:55:26 UTC
Sure, I will test out and will let you know on pull request. Thanks John.

Comment 19 John Mitsch 2019-03-21 13:03:20 UTC
Hey Lucie,

Unless there is something I am missing, this bug is for 6.4 and should be tested on a 6.4 backup.

Comment 22 Bryan Kearney 2020-05-01 13:22:42 UTC
This was delivered in Satellite 6.6.


Note You need to log in before you can comment on or make changes to this bug.