Bug 122635
Summary: | XMLRPC protocol incompatibility between RHEL3 client and Satellite | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Aleksandr Brezhnev <brezhnev> |
Component: | Configuration Management | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Paul Dorsey <pdorsey> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | rhn-bugs, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-06-18 16:32:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 119090 |
Description
Aleksandr Brezhnev
2004-05-06 15:08:33 UTC
Another discovery. I created a text file /tmp/hex-test with substring "%fa": 1234567890%fa1234567890 and uploaded this file into Satellite. Satellite shows this file properly. RHEL3 client can deploy it but substitutes substring "%fa" with one byte with code 0xfa: # od -t x1 /tmp/hex-test 0000000 31 32 33 34 35 36 37 38 39 30 fa 31 32 33 34 35 0000020 36 37 38 39 30 0a 0000026 Bumping priority, adding as a blocker for rhn340hosted. Need to determine if responsability lies w/ libxml2/libxml2-python or if it's somewhere in the RHN stack. Related problem is described in IT#38514: We have an activation key with a list of packages to install: python-optik rhncfg rhncfg-actions rhncfg-client rhncfg-management rhns-config-libs When we are trying to register RHEL3 client with Satellite using rhnreg_ks --force --activationkey ACTIVATION_KEY the package deployment action fails with error code 30 returned to Satellite. In fact, all rpms are installed but Satellite gets error code 0x30 which would be 0 if libxml2-python had transfered this hex code correctly. PS -- thank you for the excellently detailed bug report! rhncfg-client on RHEL 2.1 corrupts files containing %xx strings the same way as it does so on RHEL 3. For example, rhncfg-client get /etc/ftpaccess deploys file but converts "%65534" to "e534". Bret is working on it. Ok, nest of bugs uncovered and hopefully squashed. This needs to be
fully tested.
The new client rpms (rhncfg-*3.1.6-6-*) need to be tested on both
RHEL3 and RHEL2.1. Specifically, need to run through the scheduled
action, rhncfg-client, and rhncfg-manager tests.
They need to be pointed at *both* a 3.2 satellite to ensure they work
as much as the old ones did when pointed at old app code, and they
need to be pointed at a new rhn340 satellite and new rhn340 hosted env
(aka, webdev). The new server side packages should be confirmed to be
>= 3.4.0-7
Be sure to include /etc/mail/sendmail.cf, a text file of your choice,
and a binary file of your choice in the import and deploy tests.
Oh, and we also need to test the clients in prod against the new server side code to make sure they work together as much as the clients in prod did w/ the rhn320 code. So, rhncfg*-3.1.5-3-* against the rhns >= 3.4.0-7 backend packages. when testing in qa, be sure to test w/ rhncfg*3.1.6-7 All steps verified rhncfg-client rhncfg-manager Paul Note test plans for all rhncfg functions should be writen and automated When will this be released? |