Bug 1572493
Summary: | openshift_logging_namespace default value should be openshift-logging in openshift_health_checker/openshift_checks/logging/logging.py | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.10.0 | CC: | aos-bugs, jcantril, rmeggins, wsun |
Target Milestone: | --- | ||
Target Release: | 3.10.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-04-09 23:40:43 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
Junqi Zhao
2018-04-27 07:10:19 UTC
Luke - is this your team? Commits pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/150cbfb7c4c11c857a0e9f72a76786e47dfa963e bug 1572493. Update default logging NS in openshift_health_checker https://github.com/openshift/openshift-ansible/commit/ea56d015ae5dea66451dbce749a3719a5c380814 Merge pull request #8764 from jcantrill/1572493_default_ns_for_health_check bug 1572493. Update default logging NS in openshift_health_checker default value for openshift_logging_namespace is openshift-logging now # rpm -qa | grep openshift-ansible openshift-ansible-3.10.126-1.git.0.d49a24a.el7.noarch openshift-ansible-docs-3.10.126-1.git.0.d49a24a.el7.noarch openshift-ansible-roles-3.10.126-1.git.0.d49a24a.el7.noarch openshift-ansible-playbooks-3.10.126-1.git.0.d49a24a.el7.noarch 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-2019:0620 |