#5898 CAInstance presented as always running
Closed: Fixed None Opened 7 years ago by stlaz.

Problem:
CA will always be shown as RUNNNING even after manually stopping the pki-tomcat service.

Steps to reproduce:
1. service pki-tomcatd@pki-tomcat stop
2. ipactl status

Actual result:

Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
ipa_memcached Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: RUNNING
pki-tomcatd Service: RUNNING
ipa-otpd Service: RUNNING

Expected result:

Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
ipa_memcached Service: RUNNING
httpd Service: RUNNING
ipa-custodia Service: RUNNING
pki-tomcatd Service: STOPPED
ipa-otpd Service: RUNNING

Sorry, can't get used to the ticket formatting:

Actual result:[[BR]]
Directory Service: RUNNING[[BR]]
krb5kdc Service: RUNNING[[BR]]
kadmin Service: RUNNING[[BR]]
ipa_memcached Service: RUNNING[[BR]]
httpd Service: RUNNING[[BR]]
pki-tomcatd Service: RUNNING[[BR]]
ipa-otpd Service: RUNNING[[BR]]
ipa: INFO: The ipactl command was successful

Expected result:

Directory Service: RUNNING[[BR]]
krb5kdc Service: RUNNING[[BR]]
kadmin Service: RUNNING[[BR]]
ipa_memcached Service: RUNNING[[BR]]
httpd Service: RUNNING[[BR]]
pki-tomcatd Service: STOPPED[[BR]]
ipa-otpd Service: RUNNING[[BR]]
ipa: INFO: The ipactl command was successful

decreasing priority, it is not blocker

master:

  • fb4e197 Fixes CA always being presented as running

Metadata Update from @stlaz:
- Issue assigned to stlaz
- Issue set to the milestone: FreeIPA 4.4

7 years ago

Login to comment on this ticket.

Metadata