pkidestroy doesn't remove the subsystem's connector from the security domain, so if we try to create the subsystem again pkispawn will fail saying that the connector already exists.
Traceback (innermost last): File "/usr/lib/python2.7/site-packages/pki/deployment/configuration.jy", line 135, in ? File "/usr/lib/python2.7/site-packages/pki/deployment/configuration.jy", line 132, in main File "/usr/lib/python2.7/site-packages/pki/deployment/pkijython.py", line 494, in configure_pki_data at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.netscape.certsrv.client.PKIErrorInterceptor.handle(PKIErrorInterceptor.java:52) at org.jboss.resteasy.client.core.extractors.ClientErrorHandler.clientErrorHandling(ClientErrorHandler.java:49) at org.jboss.resteasy.client.core.extractors.BodyEntityExtractor.extractEntity(BodyEntityExtractor.java:44) at org.jboss.resteasy.client.core.ClientInvoker.invoke(ClientInvoker.java:120) at org.jboss.resteasy.client.core.ClientProxy.invoke(ClientProxy.java:88) at $Proxy21.configure(Unknown Source) at com.netscape.certsrv.system.SystemConfigClient.configure(SystemConfigClient.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) com.netscape.certsrv.base.PKIException: com.netscape.certsrv.base.PKIException: Errors in pushing KRA connector information to the CA: java.io.IOException: DRM connector already exists.
commit:
1cceecafb8050ec362a9c9568d36d52d3fe4117e
Metadata Update from @edewata: - Issue assigned to vakwetu - Issue set to the milestone: 10.0.1
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/938
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.