Bug 1844634
| Summary: | [RFE] publish task spawned from sync task should be executed immediately, not put to the end of resource_manager queue | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> |
| Component: | Repositories | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED NOTABUG | QA Contact: | Cole Higgins <chiggins> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.7.0 | CC: | ahumbe, dalley, dkliban, dsynk, jhutar, jsherril, ktordeur, ltran, ttereshc |
| Target Milestone: | Unspecified | Keywords: | FutureFeature |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-08 12:55:28 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
2020-06-05 20:27:41 UTC
Hi Dennis, Would this still be applicable for pulp 3 or only pulp 2? Hi Pavel, The details might not be entirely relevant for Pulp 3 but currently it would have the same issue in terms of a sequence in which tasks are performed. Pulp 3 does not have auto publish functionality, it will have it soon though. Katello triggers publication creation after pulp sync is done, I believe. There is some tasking system redesign is going on at the moment + auto-publish is just being added. I'll keep this BZ open, to keep the workflow you described in mind. And we'll see if we could improve something in this are. Thanks! Pavel, the new auto-publish/distribute feature in Pulp 3 upstream makes it possible to perform Pulp's sync/publish inside one task. Currently, Katello doesn't use this feature, so as of now, Satellite will behave in a simialr way as before. We'll see if there are any objections/obstacles to start using this feature on the Katello side. (In reply to Tanya Tereshchenko from comment #4) > Pavel, the new auto-publish/distribute feature in Pulp 3 upstream makes it > possible to perform Pulp's sync/publish inside one task. > Currently, Katello doesn't use this feature, so as of now, Satellite will > behave in a simialr way as before. > We'll see if there are any objections/obstacles to start using this feature > on the Katello side. This sounds promising. Thanks for the review and feedback! The desired behaviour is available in the upstream releases of pulp_rpm 3.12+ when using auto-publish/distribute feature. In such case, Pulp sync and publish run inside one task. Moving to Katello/Repositories component to consider using the feature in the future. Auto-publish would also (probably) simplify Katello's codepaths, as for mirror repos you expect a publication to be created during the sync, but for non-mirror sync you do not, and have to trigger it yourselves. Letting non-mirrored repos be auto-published would mean that either way you can expect the publication to be there. But there's probably more that Pulp can do to make the workflows streamlined, so as you start looking into this definitely let us know if you have any pain points. Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. The task scheduling is improved in Pulp 3, so arguably this isn't much of an issue anymore regardless. |