-
Notifications
You must be signed in to change notification settings - Fork 35
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
Traceback when fetching errata info #227
Comments
This is probably related to breaking change in |
I think the breaking change was rolled back in ET
…On Wed, Apr 13, 2022 at 2:47 AM Lukas Holecek ***@***.***> wrote:
This is probably related to breaking change in /advisory/{id}.json in the
just released Errata Tool.
—
Reply to this email directly, view it on GitHub
<#227 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADX2FDFTLIGCUBVQ2FILSLVEZUXFANCNFSM5TJSBDKQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Correct, it works now, thank you :) |
I think this was resolved in RHELWF-6417. Longer-term: in RHELWF-5989 Jon Orris asked us to try to move away from the legacy |
If I recall correctly the user information is one of the difficult parts that wasn't in api/v1 but there may be other parts that are pulled from there as well |
After recent errata_tool update, errata_tool.Erratum._fetch method throws an error:
The text was updated successfully, but these errors were encountered: