#1720 Runtime dependency on python-nss is missing
Closed: Duplicate None Opened 8 years ago by mharmsen.

Runtime dependency on python-nss is missing

Steps to Reproduce:

1. pkispawn CA
2.[root@cisco-b22m3-01 ~]# pki-server subsystem-cert-find ca
Traceback (most recent call last):
  File "/usr/sbin/pki-server", line 28, in <module>
    import pki.server.cli.subsystem
  File "/usr/lib/python2.7/site-packages/pki/server/cli/subsystem.py", line 26,
in <module>
    import nss.nss as nss
ImportError: No module named nss.nss

Actual results:

yum install python-nss

[root@cisco-b22m3-01 ~]# pki-server
Usage: pki-server [OPTIONS]

  -v, --verbose                Run in verbose mode.
      --debug                  Show debug messages.
      --help                   Show help message.

Commands:
 ca                            CA management commands
 instance                      Instance management commands
 subsystem                     Subsystem management commands
 migrate                       Migrate system
 nuxwdog                       Nuxwdog related commands

Expected results:

pki-server command should be executable after CA packages are installed and
pkispawn of CA

Per discussions in the Dogtag 10.3 Triage meeting of 01/06/2016: priority high

The issue is addressed in ticket #1623 and has been fixed in 063944827690c47f1f1422e178b5b8729738ac3d (DOGTAG_10_2_6_BRANCH) and 29801060fa86b6f196ef694c6672d909ea5336e4 (master). I don't think there is anything left to do for 10.3.

This bug is a duplicate of PKI TRAC Ticket #1623 - Runtime dependency on python-nss is missing

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.3.0

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2278

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata