Bug 1965942
| Summary: | pulp3: invalid depsolving warnings when publishing a CV with filters | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> |
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Griffin Sullivan <gsulliva> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.10.0 | CC: | dalley, ggainey, ltran, myarboro, osousa, rchan, ryandeussing, ttereshc, zhunting |
| Target Milestone: | 6.10.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-pulp-rpm-3.14.3 | Doc Type: | Known Issue |
| Doc Text: |
Problem: The invalid warnings are not ignored automatically.
Solution: The "can't be installed" warnings, and warnings regarding multi-arch RPMs not found, can safely be ignored.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 14:11:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pavel Moravec
2021-05-31 08:12:50 UTC
Daniel, Grant, one more item to investigate for the dep solving area. Thank you! I can reproduce the warnings in upstream-pulp3 by: * syncing RHEL7 * finding all RPMs not associated with an Advisory (ie, only (allegedly) RPMs released at RHEL7.0GA) * copying just that list to a new repo, depsolving=true We absolutely have had RPMs released into repos without advisories. This is a never-happen case...yet here we are. It will take some time to decide if that's what we're seeing here. In the meanwhile - following this recipe on a loaner-Sat-Latest, I get the the many-warnings - but more importantly, the initial copytask fails with this error message: === pulpcore-worker-4[1160]: python3: ../src/rules.c:261: solver_addrule: Assertion `!p2 && d > 0' failed. pulpcore-worker-4[1160]: pulp [None]: pulpcore.tasking.pulpcore_worker:INFO: Cleaning up and canceling Task b4d6e7ec-bcff-4663-9ef5-599bd3bce24b === and the task is marked **CANCELED**, with the remaining 3 copy-tasks waiting-forever. I haven't been able to make that happen in pulp-upstream. Investigation notes can be found here : https://hackmd.io/@ggainey/depsolving-issues Some useful debugging scripting can be found starting at https://hackmd.io/@ggainey/depsolving-issues#Pulling-useful-info-from-journalctl Investigation continues. Quick note on investigation: The reproducer given is actually copying **the entire repo**, explicitly listing everything, and depsolving the whole thing one entity at a time; it's the worst-possible-case for copy. (Note that it **should** work, and there are def things to fix here - it's just A Lot...) The advisory-filter is "including" advisories from before-a-date. The rpm-filter is "including base-rpms", with no other qualifiers. This results in **all** rpms, and **all** advisories (no-filters copies everything, and both of these filters don't **limit** anything). To limit content to "everything from before a given date", you prob want just an **exclude** advisory-filter, that excludes everything **after** the date-of-interest. The modularity-filter doesn't do anything - RHEL7 doesn't have modules. At any rate - there is definitely at least one problem exposed here, where depsolving isn't handling multiarch correctly. It does not, however, explain the same-arch "not found" entries. Investigation continues. The Pulp upstream bug status is at POST. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. Verified in 6.10 snap 21 Content View successfully publishes with dependency solving after syncing RHEL7 repo. Steps to Reproduce: 1. Sync RHEL7 repo from CDN 2. Create and publish a CV like described above, or with hammer commands in detail: hammer content-view create --name CV_RHEL7_yes_include_2021-05-01 --organization-id=1 --repository-ids=1 --solve-dependencies=yes hammer content-view filter create --organization-id=1 --content-view=CV_RHEL7_yes_include_2021-05-01 --name=include_base --inclusion=true --original-packages=true --type=rpm hammer content-view filter create --organization-id=1 --content-view=CV_RHEL7_yes_include_2021-05-01 --name=include_errata --inclusion=true --type=erratum hammer content-view filter rule create --organization-id=1 --content-view=CV_RHEL7_yes_include_2021-05-01 --content-view-filter=include_errata --date-type='updated' --end-date='2021-05-01' hammer content-view filter create --organization-id=1 --content-view=CV_RHEL7_yes_include_2021-05-01 --name=include_modules --inclusion=true --original-module-streams=true --type=modulemd hammer content-view publish --name CV_RHEL7_yes_include_2021-05-01 --organization-id=1 --async 3. Wait for publish then check /var/log/messages Expected Results: Content View publish shows no warnings or errors. Actual Results: Content View publish shows no warnings or errors. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702 |