Bug 1466680
Summary: | [trello nEOGoTet] Elasticsearch is always deployed to -n logging, regardless of ${openshift_logging_namespace} in inventory | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xia Zhao <xiazhao> | ||||
Component: | Installer | Assignee: | Jeff Cantrill <jcantril> | ||||
Status: | CLOSED ERRATA | QA Contact: | Xia Zhao <xiazhao> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.6.0 | CC: | aos-bugs, jokerman, mmccomas, rmeggins | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-08-10 05:29:50 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: | |||||||
Attachments: |
|
Description
Xia Zhao
2017-06-30 08:50:32 UTC
Created attachment 1293153 [details]
inventory file used for logging deployment to let this bz repro
Setting to 3.6.1 as I dont see this really as a blocker It's fixed, verified with openshift-ansible-playbooks-3.6.135-1.git.0.5533fe3.el7.noarch all logging stacks can be deployed to namespace other than "logging": # oc project xiazhao Now using project "xiazhao" on server "https://host-8-175-189.host.centralci.eng.rdu2.redhat.com:8443". # oc get po NAME READY STATUS RESTARTS AGE logging-curator-1-lv9q0 1/1 Running 0 2m logging-es-data-master-0q37jjq2-1-ct6s4 1/1 Running 0 2m logging-fluentd-gxdn9 1/1 Running 0 2m logging-fluentd-zq421 1/1 Running 0 2m logging-kibana-1-fsb04 2/2 Running 0 2m 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/RHEA-2017:1716 |