Stable branch

[VermiumSifell]

What would you like to see!

Hi, I would like to see a stable branch / tag. There are so many releases I have gone thru which has broken anything related to managing in Grafana.

I would like a branch containing stable releases and listing actual breaking changes (LTS branch or something).

I want to be able to rely on the OSS version and not be nervous about having to debug for hours(if not days) after each update.

Product Area

Helm/Kubernetes/Docker, Mobile App, Other

Anything else to add?

Everything mentioned here has been pushed to releases.

Looking at you 👀

• PluginAppClientSecret not set in config #5202
• Grafana Oncall Plugin not connected #5100
• jsonData.stackid v1.9.1 Issues #4843
• Disable e2e tests for grafana latest #5207
• Oncall can't connect to external grafana #4829
• RBAC: AccessControlOnCall general availability grafana#93383 (review)
• chore: patch recent migration files that drop db columns #5277
• Migrations failing when upgrading to 1.12.1 #5244 (Migrations failing when upgrading to 1.12.1 #5244 (comment))
• chore: remove deprecated slack_channel and heartbeat integration types #5270 (Stable branch #5232 (comment))

[github-actions]

The current version of Grafana OnCall, at the time this issue was opened, is v1.12.0. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!

[WoodyWoodsta]

I'm in the same boat. I've spent many hours now trying to get oncall connected back to Grafana following the broken migrations in 1.12.1, with no acknowledgment from the team.

Difficult to help out if there is no communication!

[VermiumSifell]

I'm in the same boat. I've spent many hours now trying to get oncall connected back to Grafana following the broken migrations in 1.12.1, with no acknowledgment from the team.

Difficult to help out if there is no communication!

Hi I would like to clarify that they provided a solution in https://github.com/grafana/oncall/releases/tag/v1.13.1 (check release notes). But yeah, having a stable branch would be so amazing.

[WoodyWoodsta]

Except the actual solution is #5244 (comment), not simply running --fake across all the migrations as the release note suggests.

[VermiumSifell]

Can we get some sort of Stable branch? Upgraded to v1.13.10 today and got this:
oncall_engine | django.db.utils.IntegrityError: NOT NULL constraint failed: heartbeat_integrationheartbeat.actual_check_up_task_id

Not sure if it was caused by v1.13.10 but still. OnCall software should be stable and not hacky.

UPDATE:

By manually rerunning the following migrations I got it working, so most likely --fake causing the issue.

254 | slack | 0012_remove_slackmessage_organization_state | 2024-12-07 02:44:47.418837
253 | slack | 0011_remove_slackmessage__channel_id_state | 2024-12-07 02:44:47.314318
252 | slack | 0010_remove_slackmessage_active_update_task_id_db | 2024-12-07 02:44:47.230221
251 | slack | 0009_drop_orphaned_messages_and_fill_in_missing_team_identity_values | 2024-12-07 02:44:47.146062
250 | slack | 0008_remove_slackmessage_active_update_task_id_state | 2024-12-07 02:44:46.797070
249 | slack | 0007_migrate_slackmessage_channel_id | 2024-12-07 02:44:46.705395
248 | slack | 0006_rename_channel_id_slackmessage__channel_id_and_more | 2024-12-07 02:44:46.627356
247 | labels | 0006_remove_alertreceivechannelassociatedlabel_inheritable_state | 2024-12-07 02:44:46.166525
246 | alerts | 0071_migrate_labels | 2024-12-07 02:44:45.208357
245 | user_management | 0029_remove_organization_general_log_channel_id_db | 2024-11-22 06:35:22.497590
244 | user_management | 0028_remove_organization_general_log_channel_id_state | 2024-11-22 06:35:22.493546
243 | schedules | 0021_remove_oncallschedule_channel_db | 2024-11-22 06:35:22.489402
242 | schedules | 0020_remove_oncallschedule_channel_state | 2024-11-22 06:35:22.485387
241 | heartbeat | 0003_remove_integrationheartbeat_actual_check_up_task_id_and_more | 2024-11-22 06:35:22.481753
240 | auth_token | 0007_serviceaccounttoken | 2024-11-22 06:35:22.477856
239 | alerts | 0070_remove_resolutionnoteslackmessage__slack_channel_id_db | 2024-11-22 06:35:22.473265
238 | alerts | 0069_remove_channelfilter__slack_channel_id_db | 2024-11-22 06:32:52.702302
237 | alerts | 0068_remove_resolutionnoteslackmessage__slack_channel_id_state | 2024-11-22 06:32:52.612590
236 | alerts | 0067_remove_channelfilter__slack_channel_id_state | 2024-11-22 06:32:52.548780
235 | alerts | 0066_remove_channelfilter__slack_channel_id_and_more | 2024-11-22 06:32:52.503476
234 | alerts | 0065_alertreceivechannel_service_account | 2024-11-22 06:32:52.496121
233 | user_management | 0027_serviceaccount | 2024-11-22 06:32:52.262754