| Summary: | use_dnsmasq defaults should be false for 3.1 installs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> | ||||
| Component: | Installer | Assignee: | Scott Dodson <sdodson> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ma xiaoqiang <xiama> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.1.0 | CC: | aos-bugs, bleanhar, jokerman, mmccomas, xtian | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: Containerized installations of OSE 3.1 were incorrectly receiving configuration defaults intended only to be used with OSE 3.2 installations. This meant that dnsmasq was configured for 3.1 installs when it shouldn't have been.
Fix: We have fixed containerized version detection so that the correct default configurations are applied to 3.1 installations. This means dnsmasq will no longer be included by default on 3.1 containerized installations. This bug only affected containerized installations.
Result:
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-06-07 10:55:30 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: | |||||
| Attachments: |
|
||||||
The dnsmasq wasn't installed ,so Verified and pass. 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-2016:1208 |
Created attachment 1151288 [details] dnsmasq was installed by default. Description of problem: The dnsmasq was installed by default for atomic and containerized 3.1 installs. It seems the root cause is that the version_gte_3_2_or_1_2 was set to true by mistake. hosts.ose.example # Configure dnsmasq for cluster dns, switch the host's local resolver to use dnsmasq # and configure node's dnsIP to point at the node's local dnsmasq instance. Defaults # to True for Origin 1.2 and OSE 3.2. False for 1.1 / 3.1 installs, this cannot # be used with 1.0 and 3.0. # openshift_use_dnsmasq=False install.logs ok: [atomic1node2.example.com] => {"ansible_facts": {"openshift": {"common": <---snip---> false, "use_dnsmasq": true, "use_flannel": false, "use_manageiq": true, "use_nuage": false, "use_openshift_sdn": true, "version_gte_3_1_1_or_1_1_1": true, "version_gte_3_1_or_1_1": true, "version_gte_3_2_or_1_2": true}, "current_config": {"roles": ["node", "docker"]}, "docker": {"additional_registries": ["registry.access.redhat.com"], "api_version": 1.2, "disable_push_dockerhub": false, "version": "1.8.2-el7"}, "etcd": {"etcd_data_dir": "/var/lib/etcd/default.etcd"}, "hosted": {"router": {"selector": "region=infra"}}, "node": {"annotations": <---snip---> Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.82 How reproducible: always Steps to Reproduce: 1.Don't specify openshift_use_dnsmasq in inventory file and then install containerized OSE 3.1 2.ansible-playbook -i config/hostnative /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml -vvv|tee install.logs 3. check the install logs Actual results: refer to the attached logs Expected results: Additional info: It result in install failure due to I am using a non-recurring nameserver(dnsmasq don't support non-recursio nameserver).