Bug 1465718
| Summary: | Logging services are exist but "oadm diagnostics AggregatedLogging" reports the services are not found | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||||||
| Component: | oc | Assignee: | Luke Meyer <lmeyer> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Junqi Zhao <juzhao> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.6.0 | CC: | aos-bugs, jcantril, jokerman, lmeyer, mmccomas, pportant, pweil, rcarvalh, rmeggins | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-07-10 13:07: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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Junqi Zhao
2017-06-28 02:22:14 UTC
# oc version oc v3.6.122 kubernetes v1.6.1+5115d708d7 features: Basic-Auth GSSAPI Kerberos SPNEGO Jeff, is there a difference in the logging components for 3.6 that would require changes to `oadm diagnostics`? Luke, could you please have a look at this too? Probably should not check for the logging-deployer service account anymore, but the other ERRORs seem like things that should be there. If I add `-d` I can see why it's not finding the services. The services are no longer created with the expected label.
============
debug: Checking for services in project 'logging' with selector 'logging-infra=support'
ERROR: [AGL0217 from diagnostic AggregatedLogging@openshift/origin/pkg/diagnostics/cluster/aggregated_logging/diagnostic.go:96]
Expected to find 'logging-es' among the logging services for the project but did not.
===========
In fact the created services no longer have any labels whatsoever.
The services not being found should be addressed by https://github.com/openshift/openshift-ansible/pull/4649 I suggest we leave https://bugzilla.redhat.com/show_bug.cgi?id=1421623 for the remaining items as those will be origin changes. Thanks, Luke. IIUC there is no released version where the labels are missing and this was a regression in 3.6, correct? Assuming the PR makes it into 3.6.0, yes. https://github.com/openshift/openshift-ansible/pull/4649 was merged, this is ready for testing. Not certain it's been built yet but probably by the time QE gets to this. Tested, ops cluster was not enabled, but there were warn info showed it expected to find 'logging-es-ops', 'logging-es-ops-cluster', 'logging-kibana-ops' among the logging services for the project but did not. See the attached file, if we decide to ignore these warn info, then I think we can close this defect. Created attachment 1294019 [details]
logging diagnostics info
Created attachment 1294021 [details]
logging diagnostics info
From your output it looks like this particular bug has been addressed. I'm using the other bug 1421623 and PR to downgrade the ops warnings to info and get rid of the error about the deployer service account. It's reproduced, see the attached file # openshift version openshift v3.6.136 kubernetes v1.6.1+5115d708d7 etcd 3.2.1 Created attachment 1295231 [details]
issue reproduced
(In reply to Junqi Zhao from comment #15) > It's reproduced What was the version of openshift-ansible used to produce this? The issue was that the services were created without the right metadata that the diagnostic is looking for. The latest openshift-ansible 3.6 should be creating these correctly. Not a blocker so moving to 3.6.1. But I think it's likely fixed anyway unless the fix got reverted somehow. (In reply to Luke Meyer from comment #17) > (In reply to Junqi Zhao from comment #15) > > It's reproduced > > What was the version of openshift-ansible used to produce this? > > The issue was that the services were created without the right metadata that > the diagnostic is looking for. The latest openshift-ansible 3.6 should be > creating these correctly. Tested with the latest openshift-ansible version 3.6.139-1, this issue does not exist. # rpm -qa | grep openshift-ansible openshift-ansible-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-roles-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-docs-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-lookup-plugins-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-callback-plugins-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-playbooks-3.6.139-1.git.0.4ff49c6.el7.noarch openshift-ansible-filter-plugins-3.6.139-1.git.0.4ff49c6.el7.noarch |