From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Description of problem: I register a AS 3.0 client via Proxy to our Internal Satellite. When I apply errata on Satellite and run rhn_check on client, the first errata is applied and the rest of the errata fails with a protocol error. If I apply the errata again and run rhn_check, the first errata is applied and the rest fail. I can step though all the errata this way, but it is broken. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Build AS3.0 client 2. Register AS 3.0 with Satellite via Proxy 3. Apply errata for client via Satellite GUI 4. On client, run rhn_check 5. Output from /var/log/up2date on client [Fri Jun 11 11:26:56 2004] up2date updating login info [Fri Jun 11 11:26:56 2004] up2date logging into up2date server [Fri Jun 11 11:26:56 2004] up2date successfully retrieved authentication token from up2date server [Fri Jun 11 11:26:56 2004] up2date availablePackageList from network [Fri Jun 11 11:26:58 2004] up2date installing packages: ['SysVinit-2.85-4.2'] [Fri Jun 11 11:27:02 2004] up2date Removing packages from package profile: ['SysVinit-2.85-4'] [Fri Jun 11 11:27:02 2004] up2date Adding packages to package profile: ['SysVinit-2.85-4.2'] [Fri Jun 11 11:27:03 2004] up2date deleting /var/spool/up2date/SysVinit-2.85-4.2.i386.hdr [Fri Jun 11 11:27:03 2004] up2date deleting /var/spool/up2date/SysVinit-2.85-4.2.i386.rpm [Fri Jun 11 11:27:03 2004] up2date updating login info [Fri Jun 11 11:27:03 2004] up2date logging into up2date server [Fri Jun 11 11:27:04 2004] up2date successfully retrieved authentication token from up2date server [Fri Jun 11 11:27:05 2004] up2date A protocol error occurred: Not Found , attempt #1, [Fri Jun 11 11:27:10 2004] up2date A protocol error occurred: Not Found , attempt #2, ...... Expected Results: All the errata should have been applied. Additional info:
See bug 115385 Will deliver patch to customer ASAP (i.e., as soon as QA gives an OK for beta). *** This bug has been marked as a duplicate of 115385 ***
It's an up2date bug by the way... so changed the component to reflect that.
Patch delivered to consultant.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.