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

[Bug] Grafana Operator deploys version 7.5.16 by default, needs to be updated to 7.5.17 #847

Closed
xphyr opened this issue Nov 17, 2022 · 3 comments
Labels
bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@xphyr
Copy link
Contributor

xphyr commented Nov 17, 2022

Describe the bug
Current release of Grafana Operator deploys version 7.5.16 of Grafana. The latest release of the Chrome browser (and browsers based on Chrome such as Microsoft Edge) trigger a bug in the QueryFields/Input Fields of Grafana see QueryFields/Input fields are broken in the recent Chrome browser

This also shows up in the Grafana UI as ""1:1: parse error: unexpected character: '\ufeff".

A fix for this issue is in Grafana 7.5.17 see [v7.5.x] Chore: Update slate and related packages

Version
v4.7.1

To Reproduce
Steps to reproduce the behavior:

  1. Deploy Grafana from Grafana Operator
  2. Follow steps to reproduce Grafana bug from QueryFields/Input fields are broken in the recent Chrome browser

Expected behavior
Operator should deploy version 7.5.17 as a minimum version to address this issue.

Suspect component/Location where the bug might be occuring
The value of the default GrafanaVersion needs to be updated in controllers/constants.go

Screenshots
NA

Runtime (please complete the following information):

  • OS: Any
  • Grafana Operator Version: v4.7.1
  • Environment: all
  • Deployment type: Operator from OperatorHub in OpenShift
  • Other: NA

Additional context
Link to Slack Discussion: https://kubernetes.slack.com/archives/C019A1KTYKC/p1668698161070489

@xphyr xphyr added bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 17, 2022
@xphyr
Copy link
Contributor Author

xphyr commented Nov 17, 2022

I am working on the PR update to this and will submit once I have tested it.

@xphyr
Copy link
Contributor Author

xphyr commented Nov 17, 2022

This can be addressed in the 4.7.1 release of the grafana operator by updating your current Grafana CR with: spec.baseImage: docker.io/grafana/grafana:7.5.17 as shown below:

apiVersion: integreatly.org/v1alpha1
kind: Grafana
metadata:
  name: example
  namespace: my-grafana
spec:
  baseImage: 'docker.io/grafana/grafana:7.5.17'
  config: {}

xphyr added a commit to xphyr/grafana-operator that referenced this issue Nov 17, 2022
xphyr added a commit to xphyr/grafana-operator that referenced this issue Nov 17, 2022
NissesSenap pushed a commit that referenced this issue Nov 17, 2022
…#847 (#848)

Signed-off-by: xphyr <xphyr@users.noreply.github.com>
@pb82
Copy link
Collaborator

pb82 commented Nov 22, 2022

Closing this, fix has been merged

@pb82 pb82 closed this as completed Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants