#905 2 Step Configuration of CA instance using pkispawn fails
Closed: Fixed None Opened 10 years ago by mrniranjan.

When doing 2 Step process for configuring CA instance using pkispawn, pkispawn fails during Configuration.

Versions:

pki-ca-10.2.0-0.1.20140312T0344zgitd5fcab3.fc20.noarch (Build Date:Wed 12 Mar 2014 12:28:39 AM EDT)
pki-server-10.2.0-0.1.20140312T0344zgitd5fcab3.fc20.noarch(Build Date:Wed 12 Mar 2014 12:28:39 AM EDT)

Steps:

  1. Edit /etc/pki/default.cfg and change the parameters to do only Installation and skip configuration
pki_skip_configuration=True
pki_skip_installation=False
  1. Run pkispawn
[root@pkiserver1 ~]# pkispawn
Subsystem (CA/KRA/OCSP/TKS/TPS) [CA]:

Tomcat:
  Instance [pki-tomcat]:
  HTTP port [8080]:
  Secure HTTP port [8443]:
  AJP port [8009]:
  Management port [8005]:

Administrator:
  Username [caadmin]:
  Password:
  Verify password:
  Import certificate (Yes/No) [N]?
  Export certificate to [/root/.dogtag/pki-tomcat/ca_admin.cert]:

Directory Server:
  Hostname [pkiserver1.example.org]:
  Port [389]:
  Bind DN [cn=Directory Manager]:
  Password:
  Base DN [o=pki-tomcat-CA]:

Security Domain:
  Name [example.org Security Domain]:

Begin installation (Yes/No/Quit)?
Begin installation (Yes/No/Quit)? Yes

Installing CA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into
/etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg.


==========================================================================
                                INSTALLATION SUMMARY

==========================================================================

    Please start the configuration by accessing:

https://pkiserver1.example.org:8443/ca/admin/console/config/login?pin=96qHTCrVdRzYSxkehgF8

    After configuration, the server can be operated by the command:
    systemctl restart pki-tomcatd@pki-tomcat.service


==========================================================================
  1. Now modify default.cfg to skip installation and do configuration
pki_skip_configuration=False
pki_skip_installation=True
  1. Run pkispawn
[root@pkiserver1 ~]# pkispawn
Subsystem (CA/KRA/OCSP/TKS/TPS) [CA]:

Tomcat:
  Instance [pki-tomcat]:
  HTTP port [8080]:
  Secure HTTP port [8443]:
  AJP port [8009]:
  Management port [8005]:

Administrator:
  Username [caadmin]:
  Password:
  Verify password:
  Import certificate (Yes/No) [N]?
  Export certificate to [/root/.dogtag/pki-tomcat/ca_admin.cert]:

Directory Server:
  Hostname [pkiserver1.example.org]:
  Port [389]:
  Bind DN [cn=Directory Manager]:
  Password:
  Base DN [o=pki-tomcat-CA]:

Security Domain:
  Name [example.org Security Domain]:

Begin installation (Yes/No/Quit)? Yes

Installing CA into /var/lib/pki/pki-tomcat.
pkispawn    : ERROR    ....... KeyError:  'pki_uid'!

Installation failed

pki-spawn logs show below error:

2014-03-12 07:24:04 pkispawn    : INFO     BEGIN spawning subsystem 'CA' of instance 'pki-tomcat' . . .
2014-03-12 07:24:04 pkispawn    : INFO     ... skip initializing 'pki.server.deployment.scriptlets.initialization'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip populating
'pki.server.deployment.scriptlets.infrastructure_layout'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip populating 'pki.server.deployment.scriptlets.instance_layout'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip populating 'pki.server.deployment.scriptlets.subsystem_layout'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip populating 'pki.server.deployment.scriptlets.selinux_setup'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip deploying 'pki.server.deployment.scriptlets.webapp_deployment'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip assigning slots for 'pki.server.deployment.scriptlets.slot_substitution'
2014-03-12 07:24:04 pkispawn    : INFO     ... skip generating 'pki.server.deployment.scriptlets.security_databases'
2014-03-12 07:24:04 pkispawn    : INFO     ... configuring 'pki.server.deployment.scriptlets.configuration'
2014-03-12 07:24:04 pkispawn    : INFO     ....... mkdir -p /root/.dogtag/pki-tomcat/ca
2014-03-12 07:24:04 pkispawn    : DEBUG    ........... chmod 755 /root/.dogtag/pki-tomcat/ca
2014-03-12 07:24:04 pkispawn    : DEBUG    ........... chown 0:0 /root/.dogtag/pki-tomcat/ca
2014-03-12 07:24:04 pkispawn    : INFO     ....... generating '/root/.dogtag/pki-tomcat/ca/password.conf'
2014-03-12 07:24:04 pkispawn    : INFO     ....... modifying '/root/.dogtag/pki-tomcat/ca/password.conf'
2014-03-12 07:24:04 pkispawn    : DEBUG    ........... chmod 660 /root/.dogtag/pki-tomcat/ca/password.conf
2014-03-12 07:24:04 pkispawn    : DEBUG    ........... chown 0:0 /root/.dogtag/pki-tomcat/ca/password.conf
2014-03-12 07:24:04 pkispawn    : INFO     ....... generating '/root/.dogtag/pki-tomcat/ca/pkcs12_password.conf'
2014-03-12 07:24:04 pkispawn    : INFO     ....... modifying '/root/.dogtag/pki-tomcat/ca/pkcs12_password.conf'
2014-03-12 07:24:04 pkispawn    : DEBUG    ........... chmod 660 /root/.dogtag/pki-tomcat/ca/pkcs12_password.conf
2014-03-12 07:24:04 pkispawn    : ERROR    ....... KeyError:  'pki_uid'! 
2014-03-12 07:24:04 pkispawn    : DEBUG    ....... Error Type: KeyError
2014-03-12 07:24:04 pkispawn    : DEBUG    ....... Error Message: 'pki_uid'
2014-03-12 07:24:04 pkispawn    : DEBUG    .......   File "/usr/sbin/pkispawn", line 447, in main  rv = instance.spawn(deployer)
 File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 70, in spawn
deployer.file.modify(deployer.master_dict['pki_client_pkcs12_password_conf'])
 File "/usr/lib/python2.7/site-packages/pki/server/deployment/pkihelper.py", line 1455, in modify
 uid = self.identity.get_uid()
 File "/usr/lib/python2.7/site-packages/pki/server/deployment/pkihelper.py", line 257, in get_uid
    pki_uid = self.master_dict['pki_uid'

[06/04/2014] - Moving to Milestone 10.2 (July) to see if this is still a problem.

currently out for review

Check into 'master':

  • 3cbd3f4fd71bace3e1b5020defba07a3311d082a

Metadata Update from @mrniranjan:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.2 - 08/14 (August)

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/1472

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