Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Provisioning a RHEL5 system with static bootproto creates two network-scripts: one with dhcp bootproto and other with bootproto as none
Version-Release number of selected component (if applicable):
Satellite 6.2.x
RHEL 5.x
How reproducible: Always
Steps to Reproduce:
1. Go to Subnet --> Select IPAM as none and Boot mode as 'Static'
2. Provision a fresh RHEL5 system
Actual results:
Two files are created. One with bootproto as dhcp and second with bootproto as none.
Expected results:
The system must have one network-script ethernet (assuming that only one interface has been added), with bootproto as static.
Additional info:
[root@xyz ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Virtio Network Device
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
HWADDR=00:1a:4a:34:6d:00
[root@xyz ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0.bak
BOOTPROTO="none"
IPADDR="192.168.100.97"
NETMASK="255.255.255.0"
GATEWAY="192.168.100.18"
DEVICE=eth0
HWADDR="00:1a:4a:34:6d:00"
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
DNS1=192.168.100.18
Hello,
Is there any update on this.
I was able to reproduce this issue on my satellite @6.2.3
But, My satellite is @6.2.8 and I am unable to reproduce the issue now.
But, the customer has upgraded to 6.2.7 and is still facing this issue.
The customer is required to move the ifcfg-eth0.bak to ifcfg-eth0 and then restart the system for the system to be able to get an IP, otherwise the system fails to get an IP after it is provisioned.
Issue faced for only rhel5 systems.
Regards,
Mihir
(In reply to Mihir Lele from comment #2)
===
> But, the customer has upgraded to 6.2.7 and is still facing this issue.
===
Mihir, I think the customer forgot to tell you that they updated to 6.2.8 in late March. But yes, even at that version they are still facing the issue.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.