Cloud VM instances (in OpenStack or EC2) often have a concept of private IP address assigned to it's network interfaces and a public IP address that can be assigned to a VM. The public IP is just routed to the VM and thus not present in the interfaces.
ipa-server-install --ip-address=PUBLIC_IP fails in that case and the IP address of the server needs to be reassigned after the installation:
ipa-server-install --ip-address=PUBLIC_IP
# ipa-server-install --setup-dns --ip-address 1.2.3.4 Usage: ipa-server-install [options] ipa-server-install: error: option --ip-address: invalid IP address 1.2.3.4: No network interface matches the provided IP address and netmask
It would be better to turn the error just in a warning and let Administrator use the value when sure it is the right address.
Moving to OpenStack integration bucket. As discussed on the triage, it would be preferred if a --force option is added, instead of just a warning.
--force
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1377973 (Red Hat Enterprise Linux 7)
Metadata Update from @mkosek: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA OpenStack Integration
Metadata Update from @mbasti: - Issue close_status updated to: None - Issue set to the milestone: FreeIPA 4.5.2 (was: FreeIPA OpenStack Integration)
master:
ipa-4-5:
Metadata Update from @mbasti: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Reopening, fix for this causes additional issues
Metadata Update from @mbasti: - Issue status updated to: Open (was: Closed)
Metadata Update from @tkrizek: - Issue set to the milestone: FreeIPA 4.5.3 (was: FreeIPA 4.5.2)
Metadata Update from @dkupka: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.