Bug 1543638 - httpd pod cannot forward requests to cloudforms pod when httpd-auth-configs is updated with AD auth settings
Summary: httpd pod cannot forward requests to cloudforms pod when httpd-auth-configs i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: cfme-httpd-configmap-generator
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.3
Assignee: Joe Vlcek
QA Contact: Ievgen Zapolskyi
Steve Bream
URL:
Whiteboard: auth:externalauth:ad
Depends On: 1590301
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-08 21:40 UTC by Ievgen Zapolskyi
Modified: 2018-07-12 14:51 UTC (History)
7 users (show)

Fixed In Version: 5.9.3.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-12 14:51:39 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
izapolsk: automate_bug+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2183 0 None None None 2018-07-12 14:51:56 UTC

Description Ievgen Zapolskyi 2018-02-08 21:40:41 UTC
Description of problem:
httpd generator pod generates config map with new resolv.conf file.
initialize-httpd-auth service of httpd pod replaces default resolve.conf with openshift's dns ip by new resolv.conf from httpd-auth-configs config map.
As a result httpd pod cannot resolve cloudforms name and cannot forward requests to it. 

Version-Release number of selected component (if applicable):
5.9.0.18/upstream
I have to use upstream httpd-config-generator because of blocker 1540641.
But httpd pod and the rest is 5.9.0.18

How reproducible:
100%

Steps to Reproduce:
1. generate AD auth configuration using httpd generator pod
2. replace default httpd-auth-configs config map
3. redeploy httpd pod
4. oc rsh to httpd pod and check initialize-httpd-auth service state
if it is failed, then start service manually (this is necessary because of another bug)
5. try to connect to CloudForms in browser


Actual results:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: DNS lookup failure for: cloudforms

Expected results:
resolv.conf should be correctly updated

Comment 2 Joe Vlcek 2018-05-08 14:21:49 UTC
Ievgen,

Can post a PM in the BZ with the credentials for the environment where you are encountering this?

Thank you. JoeV

Comment 4 Joe Vlcek 2018-05-21 20:48:30 UTC
This issue will be addressed by PR: https://github.com/ManageIQ/httpd_configmap_generator/pull/32

Comment 5 Joe Vlcek 2018-05-21 20:53:22 UTC
Ievgen,

I have posted a PR that does remove the /etc/resolv.conf from the Active Directory
config map, as you have pointed out should not be.

I have also changed "--ad-server" name to be a required parameter.

I have tested the fix on the QE OpenShift test bed but I used my Active Directory
server/Realm. The Active Directory realm must be DNS resolvable and it is not
in the QE Active Directory set up.

So although this PR will allow for successful generation of active directory
config maps doing so will not be possible until the active directory realm is
DNS resolvable for the QE AD test setup.

Comment 6 Ievgen Zapolskyi 2018-05-22 09:51:52 UTC
Joe, 

nice, thank you!

as for QE AD test setup we know about that and we add some workaround to make AD DNS resolvable.

Comment 7 Joe Vlcek 2018-05-22 14:36:31 UTC
https://github.com/ManageIQ/httpd_configmap_generator/pull/32
has been merged. Moving to "POST"

Comment 10 Ievgen Zapolskyi 2018-06-20 13:19:16 UTC
Verified in 5.9.3.2

Comment 12 errata-xmlrpc 2018-07-12 14:51:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2183


Note You need to log in before you can comment on or make changes to this bug.