All new release-groups added after the latest Musicbrainz update can not be added to Lidarr #4817
Open
2 tasks done
Labels
Area: Metadata API
Issue is related to metadata api
Status: Confirmed
Stops stale bot from asking if stale
Status: Investigating
We're looking in to it
Type: Bug
Issue is a bug
Is there an existing issue for this?
Current Behavior
New release-groups are not showing up in Lidarr. This is a major issue and crucial to the functioning of Lidarr.
I am aware of the following things:
My conclusion is: there is something wrong with the https://api.lidarr.audio/ server. I suspect it is because of the update the music brainz api did: https://blog.metabrainz.org/2024/05/13/musicbrainz-schema-change-release-2024-05-13-with-upgrade-instructions/
Please have a look at this again.
Expected Behavior
Be able to add new release-groups to Lidarr.
Steps To Reproduce
Environment
What branch are you running?
Develop
Trace Logs?
2024-05-21 13:52:07.3|Debug|SkyHookProxy|Getting Artist with LidarrAPI.MetadataID of 14465bd9-6cf0-4341-924e-b3e9388fb400
2024-05-21 13:52:07.3|Trace|ConfigService|Using default config value for 'metadatasource' defaultValue:''
2024-05-21 13:52:07.3|Trace|HttpClient|Req: [GET] https://api.lidarr.audio/api/v0.4/artist/14465bd9-6cf0-4341-924e-b3e9388fb400
2024-05-21 13:52:07.5|Trace|HttpClient|Res: HTTP/2.0 [GET] https://api.lidarr.audio/api/v0.4/artist/14465bd9-6cf0-4341-924e-b3e9388fb400: 404.NotFound (28 bytes)
{"error":"Artist not found"} (208 ms)
2024-05-21 13:52:07.5|Debug|SkyHookProxy|Getting Album with LidarrAPI.MetadataID of 14465bd9-6cf0-4341-924e-b3e9388fb400
2024-05-21 13:52:07.5|Trace|ConfigService|Using default config value for 'metadatasource' defaultValue:''
2024-05-21 13:52:07.5|Trace|HttpClient|Req: [GET] https://api.lidarr.audio/api/v0.4/album/14465bd9-6cf0-4341-924e-b3e9388fb400
2024-05-21 13:52:08.0|Trace|HttpClient|Res: HTTP/2.0 [GET] https://api.lidarr.audio/api/v0.4/album/14465bd9-6cf0-4341-924e-b3e9388fb400: 404.NotFound (27 bytes)
{"error":"Album not found"} (450 ms)
2024-05-21 13:52:08.0|Trace|ConfigService|Using default config value for 'metadatasource' defaultValue:''
2024-05-21 13:52:08.0|Trace|HttpClient|Req: [GET] https://api.lidarr.audio/api/v0.4/search?type=all&query=lidarr%3A14465bd9-6cf0-4341-924e-b3e9388fb400
2024-05-21 13:52:08.1|Trace|HttpClient|Res: HTTP/2.0 [GET] https://api.lidarr.audio/api/v0.4/search?type=all&query=lidarr%3A14465bd9-6cf0-4341-924e-b3e9388fb400: 200.OK (2 bytes) (133 ms)
2024-05-21 13:52:08.1|Trace|Http|Res: 58372 [GET] /api/v1/search?term=lidarr%3A14465bd9-6cf0-4341-924e-b3e9388fb400: 200.OK (867 ms)
2024-05-21 13:52:08.1|Debug|Api|[GET] /api/v1/search?term=lidarr%3A14465bd9-6cf0-4341-924e-b3e9388fb400: 200.OK (867 ms)
2024-05-21 13:52:12.5|Trace|Http|Req: 58373 [GET] /logfile/lidarr.txt (from ::1 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36)
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
trace
- that are relevant and show this issue.The text was updated successfully, but these errors were encountered: