Bug 765796

Summary: rhn-profile-sync fails to submit a hostname
Product: [Community] Spacewalk Reporter: Šimon Lukašík <slukasik>
Component: ClientsAssignee: Miroslav Suchý <msuchy>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.6CC: jhutar, msuchy
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-12 09:37:48 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: 723481    

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.