#4467 ipa-server-install --uninstall doesn't restore certmonger and kadmin correctly
Closed: wontfix 5 years ago Opened 9 years ago by mkosek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1126021

Description of problem:
ipa-server-install --uninstall doesn't restore runlevels correctly for
certmonger and kadmin

clean machine, before ipa-server-install:
[root@pes-guest-79 sanity-ipa-install]# chkconfig --list certmonger
certmonger      0:off   1:off   2:off   3:on    4:on    5:on    6:off

[root@pes-guest-79 sanity-ipa-install]# chkconfig --list kadmin
kadmin          0:off   1:off   2:off   3:off   4:off   5:off   6:off

after ipa-server-install
[root@pes-guest-79 sanity-ipa-install]# chkconfig --list certmonger
certmonger      0:off   1:off   2:off   3:on    4:on    5:on    6:off

[root@pes-guest-79 sanity-ipa-install]# chkconfig --list kadmin
kadmin          0:off   1:off   2:off   3:off   4:off   5:off   6:off

after ipa-server-install --uinstall
[root@pes-guest-79 sanity-ipa-install]# chkconfig --list certmonger
certmonger      0:off   1:off   2:off   3:off   4:off   5:off   6:off

[root@pes-guest-79 sanity-ipa-install]# chkconfig --list kadmin
service kadmin supports chkconfig, but is not referenced in any runlevel (run
'chkconfig --add kadmin')


ipa server probably wrongly assumes that certmonger isn't enabled by default.
I don't know what it do with kadmin service, but it damages kadmin's runlevels.


Version-Release number of selected component (if applicable):
ipa-server-3.0.0-37.el6

How reproducible:


Steps to Reproduce:
1.ipa-server-install
2.ipa-server-install --uninstall
3.

Actual results:


Expected results:


Additional info:

Metadata Update from @mkosek:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

7 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata