-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: obs.nerc Grafana Dashboards showing x509: certificate has expired #800
Comments
Also the ACM Observability metrics endpoint on the infra cluster has a different certificate error, where the valid dates are ok: |
Starting with the second issue first: The certificate presented by https://observatorium-api-open-cluster-management-observability.apps.nerc-ocp-infra.rc.fas.harvard.edu/api/metrics/v1/default is signed by the
That CA isn't going to be trusted by anybody, hence the "certificate issuer is unknown" error. The correct fix is probably to change the corresponding route from |
Regarding the first problem, which certificate is resulting in the "certificate is expired or not yet valid" error? |
The second problem sounds like ACM Observability suddenly broke with it's passthrough Route TLS handling. kind: Route
apiVersion: route.openshift.io/v1
metadata:
name: observatorium-api
namespace: open-cluster-management-observability
uid: a7f4bf8b-eba5-456b-b9b8-71e2e1dc4802
resourceVersion: '1261594129'
creationTimestamp: '2023-11-02T13:48:51Z'
annotations:
openshift.io/host.generated: 'true'
ownerReferences:
- apiVersion: observability.open-cluster-management.io/v1beta2
kind: MultiClusterObservability
name: observability
uid: bcc31c98-3269-4ffc-bcfd-76257a9600d0
controller: true
blockOwnerDeletion: true
|
Another possible solution would be to configure grafana to trust the observability ca certificate. |
The first one relates to dex and the Oauth configuration for Grafana in vault
|
The expired certificate in the
Note the |
@larsks @schwesig I updated the certs and keys described in this issue (observability-grafana-certs, observability-server-ca-certs) in oc --as system:admin -n open-cluster-management-observability get secret/observability-grafana-certs -o jsonpath='{.data.tls\.crt}' | base64 -d
oc --as system:admin -n open-cluster-management-observability get secret/observability-grafana-certs -o jsonpath='{.data.tls\.key}' | base64 -d
oc --as system:admin -n open-cluster-management-observability get secret/observability-server-ca-certs -o jsonpath='{.data.ca\.crt}' | base64 -d It's still a temporary solution until:
|
@computate @schwesig A neat command for dealing with files embedded in secrets (and configmaps) is the
Saves you from the whole |
FYI: |
can we call this issue closed now? |
You can close this issue @schwesig . |
follow up:
Motivation
When opening a dashboard in Grafana on obs.nerc
e.g. https://grafana.apps.obs.nerc.mghpcc.org/d/20241028a/ai4dd-v5?orgId=1
there is an error:
Completion Criteria
Opening the dashboards in Grafana obs, seeing the data and getting no cert error.
Description
Completion dates
Desired - 2024-11-06
Required - 2024-11-08
/CC @schwesig @computate @RH-csaggin @jtriley @larsks
The text was updated successfully, but these errors were encountered: