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

Assertion error in pool.hpp #2007

Open
kilinitt opened this issue Jan 14, 2025 · 4 comments
Open

Assertion error in pool.hpp #2007

kilinitt opened this issue Jan 14, 2025 · 4 comments

Comments

@kilinitt
Copy link

kilinitt commented Jan 14, 2025

Hello,

I get the following assertion failure:

[root@a4030d980752 /]# dnf install ./rsync-3.3.0-3.fc41.aarch64.rpm
Updating and loading repositories:
Repositories loaded.
terminate called after throwing an instance of 'libdnf5::AssertionError'
what(): libdnf5/./solv/pool.hpp:246: void libdnf5::solv::Pool::swap_considered_map(libdnf5::solv::SolvMap&): Assertion 'other_considered_map.allocated_size() == 0 || other_considered_map.allocated_size() >= get_nsolvables()' failed: The considered map is smaller than the number of solvables in the pool
Aborted (core dumped)

It happens after a specific and somewhat set of packages installed and uninstaleld as the image is built.

Once in this state, it happens with any .rpm file that i've tried installing via dnf. What information can I provide for you to be able to diagnose the problem?

libdnf5 version is: libdnf5-5.2.8.1-2.fc41

@m-blaha
Copy link
Member

m-blaha commented Jan 14, 2025

Hi,
It seems you’re able to reproduce the issue. If possible, could you share step-by-step instructions on how to reach this unfortunate state? That would be really helpful. Also getting a backtrace from the core dump might shed some light on the problem.

@kilinitt
Copy link
Author

Hi @m-blaha, yes I have a reproducible setup, but it's actually quite difficult to detail the steps that get us to this point. I saw the problem on an intel machine as I was building an image a few days ago, and it went away as I worked on the image, so I brushed it off to docker build issues. Then it surfaced on a different image on my ARM machine, which is the reproducible case that I have. Happy to share that image with you if it can be done privately. Please let me know. I will also try to get a trace from the core dump for you later today.

@m-blaha
Copy link
Member

m-blaha commented Jan 15, 2025

Thank you. In case you are willing to share the image, you can contact me on e-mail [email protected]

@kilinitt
Copy link
Author

I can certainly do that. Apologies it's been a hectic week. Plan to get it to you by Monday @m-blaha. Thank you.

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

2 participants