Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nightly test failure in rawhide during CA installation: NoClassDefFoundError: javax/xml/bind/JAXBContext #3327

Closed
pki-bot opened this issue Oct 3, 2020 · 2 comments

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #3210. Originally filed by frenaud (@flo-renaud) on 2020-09-14 05:04:44:

  • Closed at 2020-09-17 12:08:30 as fixed
  • Assigned to nobody

The FreeIPA nightly PR [testing_master_rawhide] has multiple tests with similar failures in the server or replica installation, during the pkispawn step.

See the full description in https://pagure.io/freeipa/issue/8495

The logs can appear either in the journal or in the ipa-server|replica-install.log:

Sep 13 18:57:12 master.ipa.test systemd[1]: Starting PKI Tomcat Server pki-tomcat...
Sep 13 18:57:15 master.ipa.test pki-server[26964]: NoClassDefFoundError: javax/xml/bind/JAXBContext
Sep 13 18:57:15 master.ipa.test pki-server[26940]: ERROR: Command: pki -d /etc/pki/pki-tomcat/alias -C /tmp/tmp2zs37p5s/password.txt nss-cert-export --with-chain --format PEM Server-Cert cert-pki-ca /etc/pki/pki-tomcat/alias/ca.crt
Sep 13 18:57:15 master.ipa.test systemd[1]: pki-tomcatd@pki-tomcat.service: Control process exited, code=exited, status=255/EXCEPTION
Sep 13 18:57:15 master.ipa.test systemd[1]: pki-tomcatd@pki-tomcat.service: Failed with result 'exit-code'.
Sep 13 18:57:15 master.ipa.test systemd[1]: Failed to start PKI Tomcat Server pki-tomcat.

or

Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -C /etc/pki/pki-tomcat/pfile pkcs12-cert-find --pkcs12 /tmp/ca.p12 --password-file /tmp/tmpe9j93mxj/password.txt

Please check pkispawn logs in /var/log/pki/pki-ca-spawn.20200913175939.log

2020-09-13T17:59:44Z DEBUG stderr=NoClassDefFoundError: javax/xml/bind/JAXBContext
ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-C', '/etc/pki/pki-tomcat/pfile', 'pkcs12-cert-find', '--pkcs12', '/tmp/ca.p12', '--password-file', '/tmp/tmpe9j93mxj/password.txt']' returned non-zero exit status 255.
  File "/usr/lib/python3.9/site-packages/pki/server/pkispawn.py", line 575, in main
    scriptlet.spawn(deployer)
  File "/usr/lib/python3.9/site-packages/pki/server/deployment/scriptlets/security_databases.py", line 171, in spawn
    pkcs12.show_certs()
  File "/usr/lib/python3.9/site-packages/pki/pkcs12.py", line 73, in show_certs
    subprocess.check_call(cmd)
  File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)

The issue does not always happen as other tests with CA installation completed successfully in the same PR.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cipherboy (@cipherboy) at 2020-09-17 12:08:32

Addressed in #555

@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cipherboy (@cipherboy) at 2020-09-17 12:08:33

Metadata Update from @cipherboy:

  • Custom field component adjusted to None
  • Custom field feature adjusted to None
  • Custom field origin adjusted to None
  • Custom field proposedmilestone adjusted to None
  • Custom field proposedpriority adjusted to None
  • Custom field reviewer adjusted to None
  • Custom field type adjusted to None
  • Custom field version adjusted to None
  • Issue close_status updated to: fixed
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant