Red Hat Bugzilla – Bug 129840
Provisioning using defined NIC info macros produce unexpected results
Last modified: 2010-10-21 22:35:18 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Description of problem: Using the rhn.system.net_interface.ip_address(eth_device) macro in provisioning will pad any single digit in the quad notation IP address for an interface with a preceeding 0. So any given quad will be at least two digits in length after provisioning. Version-Release number of selected component (if applicable): rhn-satellite-3.4 How reproducible: Always Steps to Reproduce: 1. Set /etc/sysconfig/network-scripts/ifcfg-<device> to be provisioned 2. Use macro rhn.system.net_interface.ip_address(device) for IPADDRESS= directive 3. Provision RHN satellite registered client system, using 'rhncfg-client get' Actual Results: IPADDRESS= directive in /etc/sysconfig/network-scripts/ifcfg-<device> will have a 0 prefix for any quad member that is a single digit. eg if current IP assigned to eth0 interface is 172.21.5.71, then after provisioning file, IPADDRESS will be 172.21.05.71. Expected Results: IPADDRESS= should be exact IP address currently assigned to interface. Additional info:
Reassigned based on 4/27 RHN 400 status meeting.
User jslagle@redhat.com's account has been closed
Commited workaround for RHEL3 and RHEL4 (bug already fixed in >FC4, thus in RHEL5). Sending up2date_client/hardware.py Transmitting file data . Committed revision 173785.
This should be fixed in upstream; reverted previous svn commit and cloned original rhpl bug 157657 as RHEL4 rhpl bug 451002.
This bug should be fixed upstream by bug 451002. I updated the upstream bug's rhel4.9 flag to ? It seems to me that the upstream fix has fallen off their radar, and will hopefully get back on their radar. Although misleading, I am adding ClosedValid to the QA Whiteboard.