freeipa

#6879 ipa-replica-install's --ip-address option should allow addresses that are not bound to the host
Closed: wontfix by rcritten. Opened by tkent.

Closed: wontfix
Reopen Issue

The --ip-address option used with ipa-replica-install requires the address used to be bound to the host. While this seems to make perfect sense, a problem comes up when using FreeIPA in docker containers.

A containerized FreeIPA installation will only see it's docker network IP address, not any addresses bound to the docker host. If you are setting up a replica using a containerized FreeIPA installation, then you'll want to have all DNS references to the installation point to some mapped address on the docker host, not the docker network.

See this GitHub issue some history about how this problem comes up.

Metadata Update from @pvoborni:
- Issue priority set to: critical
- Issue set to the milestone: FreeIPA 4.7

Metadata Update from @rcritten:
- Issue set to the milestone: FreeIPA 4.7.1 (was: FreeIPA 4.7)

FreeIPA 4.7 has been released, moving to FreeIPA 4.7.1 milestone

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)

'tis fine by me! We've long since changed our architecture to avoid running into the issue. As long as somebody can find this issue by looking online, I assume everyone will happily just use the work-around described.
Metadata
None
None
None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.