Bug 1364139
Summary: | When master's IP address does not resolve to its name, ipa-replica-install fails | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Pazdziora <jpazdziora> | ||||
Component: | ipa | Assignee: | Florence Blanc-Renaud <frenaud> | ||||
Status: | CLOSED MIGRATED | QA Contact: | Kaleem <ksiddiqu> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 8.0 | CC: | cobrown, frenaud, jpazdziora, pasik, rcritten, tscherf, twoerner | ||||
Target Milestone: | rc | Keywords: | MigratedToJIRA, Reopened, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1751951 (view as bug list) | Environment: | |||||
Last Closed: | 2023-09-18 17:48:09 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1751951 | ||||||
Attachments: |
|
Description
Jan Pazdziora
2016-08-04 14:21:33 UTC
The installutils.verify_fqdn(config.master_host_name, options.no_host_dns) calls in /usr/lib/python2.7/site-packages/ipaserver/install/server/replicainstall.py should likely include local_hostname=False. (In reply to Jan Pazdziora from comment #1) > The > > installutils.verify_fqdn(config.master_host_name, options.no_host_dns) > > calls in > > > /usr/lib/python2.7/site-packages/ipaserver/install/server/replicainstall.py > > should likely include local_hostname=False. With this change, ipa-replica install complains but proceeds setting up the replica: /etc/ssh/sshd_config not found, skipping configuration Configuring example.test as NIS domain. Client configuration complete. ipa : ERROR The host name ipa.example.test does not match the value freeipa-server-container.freeipa-network obtained by reverse lookup on IP address 172.18.0.2 Configuring NTP daemon (ntpd) [1/4]: stopping ntpd [2/4]: writing configuration [3/4]: configuring ntpd to start on boot [4/4]: starting ntpd Done configuring NTP daemon (ntpd). Configuring directory server (dirsrv). Estimated time: 1 minute [1/44]: creating directory server user [2/44]: creating directory server instance That ERROR output should likely also be purged. Upstream ticket: https://fedorahosted.org/freeipa/ticket/6210 Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. Fixed upstream master: https://pagure.io/freeipa/c/f1e20b45c5deeb25989c87a2d717bda5a31bb084 Missclicked status MIDIFIED setting to POST; Fixed upstream ipa-4-8: https://pagure.io/freeipa/c/0b2ed9c415370de79f8ecaa1be153a1d80cf6ea1 Fixed upstream ipa-4-7: https://pagure.io/freeipa/c/82351f1e09e9d592e3b0bef521c2c94b0d222cce Fixed upstream ipa-4-6: https://pagure.io/freeipa/c/a016ed75ecbe7e2698530036043ef19df1bd718f The pull requests add that local_hostname=False in containers. I don't think this is the proper fix. This is about the master's IP address not resolving directly to its hostname, so the same situation likely happens in AWS, and the same situation happens when the master is in container (or in general, in reverse-DNS-challenging environment) and replica is on a host, outside of containers. When verifying this bugzilla, please use a setup when the IP address of master as seen by the replica does not resolve to master's hostname, outside of containers. Created attachment 1663784 [details] verification steps with console output Verified based on same steps done for 7.8 bugs mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=1751951#c10 I still don't see how this verifies the change. We need a reproducer of the failing setup with the older version of IdM, and then fixed reproducer with newer package versions. Similar to my comments in bug 1751951, unless you show that the behaviour has changed (improved), the bugzilla cannot be considered verified. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |