Grafana latest/edge fails to install
#690
Comments
This was referenced Sep 2, 2023
i-chvets
pushed a commit
to canonical/notebook-operators
that referenced
this issue
Sep 13, 2023
canonical/bundle-kubeflow#688 canonical/bundle-kubeflow#690 Summary of changes: - Pinned revisions of prometheus and grafana to avoid failure of integration tests. Refer to above issues for more details.
|
Just a quick comment. We have exactly same issue before 1.7 release. Prometheus/Grafana updates break us from time to time. Possible approach is to pin everything that we depend on to revisions when we cut a track branch. This is a proper way to "freeze" branch in time to avoid extra work in the future. There is no point having edge in track branches. |
i-chvets
added a commit
to canonical/notebook-operators
that referenced
this issue
Sep 14, 2023
* fix: pin prometheus and grafana canonical/bundle-kubeflow#688 canonical/bundle-kubeflow#690 Summary of changes: - Pinned revisions of prometheus and grafana to avoid failure of integration tests. Refer to above issues for more details.
4 tasks
DnPlas
added a commit
to canonical/dex-auth-operator
that referenced
this issue
Sep 26, 2023
|
Closing this since we use Juju>=3.1 now. |
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5367.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
Grafana from
latest/edgefails to install on Juju 2.9.44, with an error stating that the Grafana unit is not assigned to a machine. This is the case following revision 90 of the charm, which among other things introduces the use ofopen_portinstead of the K8s service patch. Pinning to a previous revision fixes the problem.Although this does not directly affect our charms, it does break our CI across repos that deploy Grafana as part of their integration tests (e.g. here)
To Reproduce
To reproduce, you can try deploying Grafana from latest/edge (revision >= 90) on Juju 2.9.44.
Environment
Juju Agent: 2.9.44
MicroK8s: 1.24/stable
Grafana: latest/edge (rev: 90)
Relevant log output
Additional context
Grafana is tested on (and most probably developed for) Juju 3.1. Given that we will be switching to Juju 3.1 very soon and that this issue blocks a number of time-critical PRs, we could pin Grafana to revision 89 for now and revert as soon as the migration has been completed.
The text was updated successfully, but these errors were encountered: