Monitoring stack fails on installation with stackablectl

Open
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes, prometheus

Research direction

Reproduce the failure with the stack install using the manifests in demos/stacks/monitoring/grafana-dashboards.yaml, demos/stacks/_templates/prometheus.yaml, and demos/stacks/_templates/prometheus-service-monitor.yaml. Compare the first installation with a second run and manual kubectl application to investigate the reported ordering issue. Done means the monitoring stack installs successfully on its first run.

Written by the indexing model from the issue text.

Description

Installing the monitoring stack with stackable fails when it reaches prometheus-service-monitor.yaml. Running the stack install a second time succeeds as does applying prometheus-service-monitor.yaml manually with kubectl.

    manifests:
      - plainYaml: demos/stacks/monitoring/grafana-dashboards.yaml
      - helmChart: demos/stacks/_templates/prometheus.yaml
      - plainYaml: demos/stacks/_templates/prometheus-service-monitor.yaml

This could be a race condition between the installation of the Prometheus helm chart and the creation of the ServiceMonitors.

Dominant language
Jupyter Notebook
Stars
3
Forks
13
Avg merge
2d 20h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/demos

All issues in stackabletech/demos

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.