-
Notifications
You must be signed in to change notification settings - Fork 297
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
Pagerduty Migration failed in migrate mode #2917
Comments
👋 @pramodh-b could you please try setting |
Hi @vadimkerr its still same issue. |
I'm not able to reproduce the issue when passing |
As you suggested changes SMTP values to true and provided the details. Now there is another error with migrate mode in the Migrating schedule step. below is the error. ▶ Migrating schedules... |
The issue should be fixed in this PR by setting @pramodh-b regarding the |
What went wrong?
What happened:
File "/app/migrator/oncall_api_client.py", line 46, in api_call
raise requests.exceptions.HTTPError(
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://URL/api/v1/personal_notification_rules, response payload JSON: {'type': 'Invalid type'}
What did you expect to happen:
I was expecting a successful migration in migrate mode.
How do we reproduce it?
By running Pager duty migrator in migrate mode we can reproduce this error
Grafana OnCall Version
1.3.27
Product Area
Other
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
Are you using OSS or Grafana Cloud?
Ans: OSS
What’s the version of OnCall on your instance?
Ans: Onall plugin version: 1.3.27, Grafana version: 9.5.3
Which types of user notification rules are used on your PD instance? (e.g. email, SMS, etc.)
Ans: Email, Call, SMS, App notification
Used helm package manager to install oncall and configure.
helm install my-oncall grafana/oncall --version 1.3.27
The text was updated successfully, but these errors were encountered: