#4831 ipa-client-install should check if fedora-domainname.service is available before calling it
Closed: Fixed None Opened 9 years ago by adelton.

In an unprivileged container, nisdomainname fails with

# nisdomainname jezek.test
nisdomainname: you must be root to change the domain name

and it's expected: https://bugzilla.redhat.com/show_bug.cgi?id=1148794. In fact, in default images like fedora:21, initscripts (and thus fedora-domainname.service) is not even installed.

While it's possible to disable the functionality with --no-nisdomain, perhaps ipa-client-install should check if the service it's trying to enable and start is even available.

This is for robustness, ipa-client-install should update it's defaults (NIS domain name setting, SUDO setting) cleanly before installing.

Processing leftovers from 4.2 backlog - this ticket was found as suitable for consideration in next big feature release - 4.4.

The RPM depedency was missing which was a mistake. The depedency will be added to the SPEC file.


  • 771dea5 client: RPM require initscripts to get *-domainname.service

Metadata Update from @adelton:
- Issue assigned to pspacek
- Issue set to the milestone: FreeIPA 4.4.1

7 years ago

Login to comment on this ticket.