Skip to content
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

Alert rule group failed to be applied - context deadline exceeded #1465

Closed
ErikRosic opened this issue Mar 19, 2024 · 2 comments
Closed

Alert rule group failed to be applied - context deadline exceeded #1465

ErikRosic opened this issue Mar 19, 2024 · 2 comments
Assignees
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ErikRosic
Copy link

ErikRosic commented Mar 19, 2024

Describe the bug

After deploying grafana-operator-grafana-deployment with CR alertrulegroup i'm getting following error:

Alert Rule Group failed to be applied for 1 out of 1 instances. Errors: │
│ - grafana-operator/grafana-operator-grafana: fetching folder: Get "http://grafana-operator-grafana-service.grafana-operator:3000/api/folders/670f1565-8f76-49f6-b78a-51469d413791": context deadline exceeded

Version

Helm chart version 3.12.2

To Reproduce

Deploy following CRs:

apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaFolder
metadata:
  name: erik-folder
spec:
  instanceSelector:
    matchLabels:
      app: grafana-operator-grafana
  permissions: |
    {
      "items": [
        {
          "role": "Admin",
          "permission": 4
        }
      ]
    }
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaAlertRuleGroup
metadata:
  name: zookeeper-elastic
spec:
  folderRef: erik-folder
  instanceSelector:
    matchLabels:
      app: grafana-operator-grafana
  interval: 1m
  rules:
    - uid: a55303dc-81ba-4d92-8d71-82de4dd6541f
      title: zookeeper-elastic
      condition: A
      data:
        - refId: A
          relativeTimeRange:
            from: 600
            to: 0
          datasourceUid: 51226607-32f3-4822-b9e4-d81ce739e094
          model:
            alias: ""
            bucketAggs:
              - field: '@timestamp'
                id: "2"
                settings:
                  interval: auto
                type: date_histogram
            datasource:
              type: elasticsearch
              uid: 51226607-32f3-4822-b9e4-d81ce739e094
            hide: false
            intervalMs: 1000
            maxDataPoints: 43200
            metrics:
              - id: "1"
                type: count
            query: 'kubernetes.labels.app_kubernetes_io/name: zookeeper'
            refId: A
            timeField: '@timestamp'
      noDataState: NoData
      execErrState: Error
      for: 1m
      annotations: { }
      labels: { }
      isPaused: false`

Expected behavior
Deployed alert in grafana-operator-grafana-deployment

Suspect component/Location where the bug might be occurring
Status in CR grafanaalertrulegroup

Runtime (please complete the following information):

k8s version v1.26.10+rke2r2

@ErikRosic ErikRosic added bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 19, 2024
@theSuess theSuess added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 26, 2024
@theSuess
Copy link
Member

We just merged #1475 which fixes an issue with timeouts in the new client.

To verify if this was your issue - do you have a custom timeout set in your Grafana instance?

@theSuess theSuess self-assigned this Mar 26, 2024
@theSuess
Copy link
Member

theSuess commented Apr 5, 2024

This is now fixed in 5.8.1! Feel free to reopen the issue if this still occurs in the newest version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants