Skip to content

fail to deploy prometheus #204

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

Closed
xp2014 opened this issue Nov 2, 2022 · 5 comments · Fixed by #206
Closed

fail to deploy prometheus #204

xp2014 opened this issue Nov 2, 2022 · 5 comments · Fixed by #206

Comments

@xp2014
Copy link

xp2014 commented Nov 2, 2022

Describe the bug
Fail to deploy prometheus with ./bin/start.sh.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a stack with ./bin/start.sh
  2. View logs on terminal
  3. See error

error: Program failed with an unhandled exception:

Your environment

  • Version of the repo -v1.1.1
  • Version of infrastructure tooling (Pulumi)
  • Version of executing environment (Python)
  • OS and distribution: ubuntu 20
  • Details about containerization or virtualization environment: Microk8s

Additional context
fail to deploy prometheus.log

@qdzlug
Copy link
Contributor

qdzlug commented Nov 10, 2022

Hi @xp2014 ,

Can you let me know what version of microk8s you are running? we have known issues with 1.24 #182

Jay

@xp2014
Copy link
Author

xp2014 commented Nov 13, 2022

@qdzlug

1.23/stable: v1.23.9

Thanks,
XP

@qdzlug
Copy link
Contributor

qdzlug commented Nov 14, 2022

@xp2014 - thanks, confirmed that I'm able to reproduce this locally. Looking into it now.

@qdzlug
Copy link
Contributor

qdzlug commented Nov 14, 2022

Found the issue; when we refactored to use the python based startup script and the secrets namespace we missed ensuring that the admin password for Grafana was added to the config. This wasn't impacting the automated testing since that builds the config automatically.

Working on a patch for the repo, but short term, you can get around this by adding the value manually

pulumi config set prometheus:adminpass "${MARA_PASSWORD}" --secret -C pulumi/python/kubernetes/secrets -s "${STACKNAME}"

where you substitute your values for the two variables.

@xp2014
Copy link
Author

xp2014 commented Nov 18, 2022

Found the issue; when we refactored to use the python based startup script and the secrets namespace we missed ensuring that the admin password for Grafana was added to the config. This wasn't impacting the automated testing since that builds the config automatically.

Working on a patch for the repo, but short term, you can get around this by adding the value manually

pulumi config set prometheus:adminpass "${MARA_PASSWORD}" --secret -C pulumi/python/kubernetes/secrets -s "${STACKNAME}"

where you substitute your values for the two variables.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants