Bug 1597809
Summary: | unable to connect to IPA server during setup in appliance_console | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Felix Dewaleyne <fdewaley> |
Component: | Appliance | Assignee: | Joe Vlcek <jvlcek> |
Status: | CLOSED NOTABUG | QA Contact: | Mike Shriver <mshriver> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5.9.0 | CC: | abellott, fdewaley, jvlcek, mpusater, obarenbo |
Target Milestone: | GA | ||
Target Release: | cfme-future | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | auth:externalauth:freeipa | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-08-09 13:48:32 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: | 1595269 |
Description
Felix Dewaleyne
2018-07-03 16:16:47 UTC
the customer was able to setup the IPA server swapping the /etc/hosts mid setup because the IPA server is behind a serie of networks that do not allow ping. the official documentation for IPA do not specify that a ping is required : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/installing-ipa#prereq-ports-list this could be a design issue with the ipa implementation in cloudforms... I've opened a feature request but in retroaspect this may actually be more of a bug. see bz https://bugzilla.redhat.com/show_bug.cgi?id=1613921 for the RFE. at this point I'm not sure if that was entirely the right move to make anymore and would appreciate feedback. (In reply to Felix Dewaleyne from comment #5) > the customer was able to setup the IPA server swapping the /etc/hosts mid > setup because the IPA server is behind a serie of networks that do not allow > ping. > > the official documentation for IPA do not specify that a ping is required : > > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ > html/linux_domain_identity_authentication_and_policy_guide/installing- > ipa#prereq-ports-list > > this could be a design issue with the ipa implementation in cloudforms... > I've opened a feature request but in retroaspect this may actually be more > of a bug. > > see bz https://bugzilla.redhat.com/show_bug.cgi?id=1613921 for the RFE. > > at this point I'm not sure if that was entirely the right move to make > anymore and would appreciate feedback. IPA client configuration can do server discovery, which is why the IPA documentation does not require the ping is required. Cloudforms engineering made the decision to ensure the IPA server be secified and reachable. This was done by design for Cloudforms configuration. We want to ensure the IPA server selected is not left up to IPA, which could result in configurations using an IPA server that was not intended. If we change it to allow IPA server auto discovery we'd be changing the currently accepted behavior and could confuse or even upset existing customers who have come to expect and rely on the current behavior. Having a network configuration where the desired IPA server is not ping-able is not a common configuration and should not be done. Having the IPA server behind a series of networks that do not allow ping is not a good network configuration and an edge case that I am not sure Cloudforms should need to support. Because the customer was able to setup the IPA server I am going to close this bug and ask that, if you feel this odd network configuration is something Cloudforms should support that you open a separate RFE and we can have PM evaluate the need. If you feel this BZ should remain open please just reopen it and provide your perspective and justification. Thank you. JoeV |