Actions
Story #2434
closedAdd timing output to sync task steps
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
There are times with Pulp syncs take a long time with no clear understanding of which step(s) took abnormally long to complete. An example progress report can be seen below.
This is a request to add start and finish times to the individual steps (e.g. comps, purge_duplicates, errata) so that tasks can be analyzed for errant behavior. This is useful for debugging a singular sync that has gone awry as well as to bulk analyze systematic issues across a number of Pulp syncs. This could help identify issues with the underlying host and resources, Pulp itself or potential performance issues with the code for a given step.
progress_report:
yum_importer:
content:
items_total: 0
state: FINISHED
error_details: []
details:
rpm_total: 0
rpm_done: 0
drpm_total: 0
drpm_done: 0
size_total: 0
size_left: 0
items_left: 0
comps:
state: FINISHED
purge_duplicates:
state: FINISHED
distribution:
items_total: 0
state: FINISHED
error_details: []
items_left: 0
errata:
state: FINISHED
metadata:
state: FINISHED
Actions
Changes how pulp-selinux RPM decides when to run restorecon statements
RHEL 7.3 was experiencing a bug that was preventing the pulp-selinux RPM from using semodule -l to figure out the installed version of pulp-selinux policies during upgrades. This patch switched to using rpm -qa for determining the version of previously installed SELinux policy.
The version comparison logic in relabel.sh only worked for version strings <= 1.9.z. This patch improves this code to make sure upgrades to 2.10.2 don't accidently run unnecesary restorecon statements.
closes #2434 https://pulp.plan.io/issues/2424