Bug 1330920
| Summary: | [Behind Proxy] The variable of "openshift_generate_no_proxy_hosts" should be in key=value form in example inventory files | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gan Huang <ghuang> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | Ma xiaoqiang <xiama> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.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: The example inventories used the incorrect syntax for openshift_generate_no_proxy_hosts.
Consequence: If you had copied and pasted the example syntax it would not have taken affect.
Fix: The example inventories have been updated with the correct syntax for setting openshift_generate_no_proxy_hosts.
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-07 10:55:23 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: | |||
|
Description
Gan Huang
2016-04-27 10:28:09 UTC
Verified with openshift-ansible-docs-3.0.90 [root@xxx ~]# grep -nir "openshift_generate_no_proxy" /usr/share/doc/openshift-ansible-docs-3.0.90/docs/ /usr/share/doc/openshift-ansible-docs-3.0.90/docs/example-inventories/hosts.aep.example:394:#openshift_generate_no_proxy_hosts=True /usr/share/doc/openshift-ansible-docs-3.0.90/docs/example-inventories/hosts.origin.example:399:#openshift_generate_no_proxy_hosts=True /usr/share/doc/openshift-ansible-docs-3.0.90/docs/example-inventories/hosts.ose.example:395:#openshift_generate_no_proxy_hosts=True 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 |