Bug 1417750 - oadm diagnostics AggregatedLogging does not find logging route
Summary: oadm diagnostics AggregatedLogging does not find logging route
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-30 21:28 UTC by Jeff Cantrill
Modified: 2017-02-01 21:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 21:44:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jeff Cantrill 2017-01-30 21:28:55 UTC
Trying to diagnose a 3.4 cluster that has both an ops and non-ops route, diagnostic fails because it evaluates against the 'ops' route.

# oc get routes
NAME                 HOST/PORT                    PATH      SERVICES             PORT      TERMINATION
logging-kibana       logs.opstest.openshift.com             logging-kibana       <all>     reencrypt
logging-kibana-ops   kibana-ops.example.com                 logging-kibana-ops   <all>     reencrypt
[root@ip-172-31-56-133 ~]# 
[root@ip-172-31-56-133 ~]# 
[root@ip-172-31-56-133 ~]# 
[root@ip-172-31-56-133 ~]# 
[root@ip-172-31-56-133 ~]# oadm diagnostics AggregatedLogging --master-config=/etc/origin/master/master-config.yaml -l 0
[Note] Determining if client configuration exists for client/cluster diagnostics
debug: Reading client config at /root/.kube/config
Info:  Successfully read a client config file at '/root/.kube/config'

```
debug: Checking if context is cluster-admin: 'logging/internal-api-opstest-openshift-com:443/system:admin'
Info:  Using context for cluster-admin access: 'logging/internal-api-opstest-openshift-com:443/system:admin'

[Note] Running diagnostic: AggregatedLogging
       Description: Check aggregated logging integration for proper configuration
       
debug: Looking for master config file at '/etc/origin/master/master-config.yaml'
debug: Found a master config file: /etc/origin/master/master-config.yaml
debug: masterConfig.AssetConfig.LoggingPublicURL: 'https://logs.opstest.openshift.com'
debug: Comparing URL to route.Spec.Host: kibana-ops.example.com

ERROR: [AGL0014 from diagnostic
AggregatedLogging@openshift/origin/pkg/diagnostics/cluster/aggregated_logging/diagnostic.go:194]
       Unable to find a route matching the loggingPublicURL defined in the master config
'https://logs.opstest.openshift.com'. Check that the URL is correct and aggregated logging is deployed.
       
[Note] Summary of diagnostics execution (version v3.4.0.39):
[Note] Errors seen: 1
```

Comment 1 Jeff Cantrill 2017-02-01 21:44:00 UTC
I'm closing as upon investigation locally, I think the route is not configured correctly.  Unfortunately the environment from which this originated is no longer available.


Note You need to log in before you can comment on or make changes to this bug.