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

Unable to use custom grafana port #187

Closed
rjd1 opened this issue Sep 4, 2023 · 1 comment
Closed

Unable to use custom grafana port #187

rjd1 opened this issue Sep 4, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@rjd1
Copy link
Contributor

rjd1 commented Sep 4, 2023

Describe the Bug

When grafana management is enabled and the port is not using the default value, the service gets stuck in a restart loop.

Expected Behavior

The grafana service should run normally and stay up with a custom port.

Steps to Reproduce

Configure the grafana server to use a different http port and set the value in the dashboards profile class. E.g., include the main puppet_operational_dashboards class and add to hiera:

grafana::cfg:
  server:
    http_port: 8080
puppet_operational_dashboards::profile::dashboards::grafana_port: 8080

Environment

  • Module Version: 2.0.0
  • Puppet Version: 7.13.1
  • Platform: Amazon Linux 2 (RHEL7)

Additional Context

The problem is the default port is hard-coded in templates/grafana_wait.epp. So it isn't seen as listening and systemd just keeps restarting the service.

@rjd1 rjd1 added the bug Something isn't working label Sep 4, 2023
rjd1 added a commit to rjd1/puppet_operational_dashboards that referenced this issue Sep 4, 2023
m0dular added a commit that referenced this issue Sep 18, 2023
(GH-187) Update grafana_wait.epp template to use grafana_port value
@m0dular
Copy link
Collaborator

m0dular commented Sep 29, 2023

Fixed in #188

@m0dular m0dular closed this as completed Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants