-
Notifications
You must be signed in to change notification settings - Fork 88
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
Loki role fails in check mode #252
Closed
winsmith opened this issue
Aug 2, 2024
· 5 comments
· Fixed by #262 · May be fixed by winsmith/grafana-ansible-collection#1
Closed
Loki role fails in check mode #252
winsmith opened this issue
Aug 2, 2024
· 5 comments
· Fixed by #262 · May be fixed by winsmith/grafana-ansible-collection#1
Comments
Agreed, it should run in check mode. Could you please raise a PR? |
@winsmith any progress on this ? |
winsmith
added a commit
to winsmith/grafana-ansible-collection
that referenced
this issue
Sep 2, 2024
This was referenced Sep 2, 2024
@voidquark whoops! Here you go: #262 |
It is still failing but this time with
|
Added a fix for it in #266. Feel free to takeover from there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running in check mode, the grafana.grafana.loki role fails to execute because a variable is not set. Here is the error message:
I believe the first task in the role, Scrape Github API endpoint to obtain latest Loki version, should always be run, even in check mode. This should fix the issue.
If requested, I'll gladly make a PR that adds
check_mode: false
to the task.The text was updated successfully, but these errors were encountered: