Skip to content
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

Open
dhodovsk opened this issue Apr 13, 2022 · 5 comments
Open

Traceback when fetching errata info #227

dhodovsk opened this issue Apr 13, 2022 · 5 comments

Comments

@dhodovsk
Copy link

After recent errata_tool update, errata_tool.Erratum._fetch method throws an error:

>>> from errata_tool import Erratum
>>> e = Erratum(errata_id=93249)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.10/site-packages/errata_tool/erratum.py", line 130, in __init__
    self._fetch(kwargs['errata_id'])
  File "/usr/local/lib/python3.10/site-packages/errata_tool/erratum.py", line 271, in _fetch
    self._product = advisory
@hluk
Copy link

hluk commented Apr 13, 2022

This is probably related to breaking change in /advisory/{id}.json in the just released Errata Tool.

@yazug
Copy link
Collaborator

yazug commented Apr 13, 2022 via email

@dhodovsk
Copy link
Author

Correct, it works now, thank you :)

@ktdreyer
Copy link
Contributor

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 /advisory/<id>.json endpoint and do everything via /api/v1/erratum/<id>

@yazug
Copy link
Collaborator

yazug commented Apr 18, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants