Bug 765796 - rhn-profile-sync fails to submit a hostname
Summary: rhn-profile-sync fails to submit a hostname
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 1.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-12-09 13:04 UTC by Šimon Lukašík
Modified: 2013-04-12 20:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-12 09:37:48 UTC
Embargoed:

Attachments (Terms of Use)

Description Šimon Lukašík 2011-12-09 13:04:11 UTC 
Description of problem:
We have a regression in rhn-profile-sync. As a consequence of IPv6 changes,
rhn-profile-sync changed behaviour, who the hostname is reported back to
the RHN.

Version-Release number of selected component (if applicable):
rhn-client-tools-1.6.39-1.el5

How reproducible:
deterministic

Steps to Reproduce:
1. Register client with Spacewalk
2. # hostname tralalabumbum
3. # rhn-profile-sync
4. Verify the hostname with Spacewalk
    - call system.getNetwork() API
    - look at the webui
  
Actual results:
The old hostname is still present on Spacewalk

Expected results:
The new hostname is reported by Spacewalk

Additional info:
In regards of reported hostname, rhnreg_ks and rhn-profile-sync seem to
have different semantics.
Note You need to log in before you can comment on or make changes to this bug.