Description of problem: During a satellite-sync of a big channel the session token may expire and when it happens the underlying code treats it as a fault. In the following commits the number of tolerated faults was decreased from 5 to 1. And as result satellite-sync crashes after the token expire. Introduced by: 24e5386344f061e7c138e2f95b7cd2d31a30686a b61515ea3408dc9c04e8e371bb85984c55e180f6 351fb160a77bd5abc1348a01ab40a5769b4d20bc Version-Release number of selected component (if applicable): Spacewalk nightly rhn-client-tools-1.4.5-1.el5 spacewalk-backend-tools-1.4.19-1.el5 How reproducible: always, deterministic Steps to Reproduce: 1. satellite-sync -c rhel-i386-server-5 2. 3. Actual results: After a while of syncing exception is thrown Expected results: Sync whole channel without exceptions. Additional info: The related beaker job: j:61626
Created attachment 485544 [details] snippet from satellite-sync
Created attachment 485546 [details] the traceback
spacewalk.git: 377f4b439ef8c866c79c8c940bba1c11b1e88bb4
QA: How to test on rhel5: echo 'networkRetries=1' >> /etc/sysconfig/rhn/up2date satellite-sync -c rhel-i386-server-5
cherry picked as 3d05614b06013f20f3ecb1f58dd4932688ca5505
Moving to RELEASE_PENDING. Re-verified with spacewalk-backend-1.2.13-52.el6sat.noarch Used option 'networkRetries=1' in /etc/rhn/rhn.conf. Sync result (snippet): ====================== 13:03:01 Importing *relevant* package metadata: rhel-i386-server-5 (8864) 17:10:12 Retrieving / parsing errata data: rhel-i386-server-5 (1702) 17:11:20 Retrieving / parsing kickstart data: rhel-i386-server-5 (7) 17:11:22 Retrieving / parsing kickstart tree files: rhel-i386-server-5 (866) 17:24:55 Importing *relevant* errata: rhel-i386-server-5 (1702) 17:30:52 Imported kickstartable trees (7) Import complete: Begin time: Tue Jun 7 08:43:20 2011 End time: Tue Jun 7 17:30:52 2011 Elapsed: 8 hours, 47 minutes, 31 seconds ======================
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. https://rhn.redhat.com/errata/RHEA-2011-0875.html