Bug 1384137

Summary:	Provisioning a RHEL5 system with static bootproto creates network-script with dhcp bootproto
Product:	Red Hat Satellite	Reporter:	Mihir Lele <mlele>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.2	CC:	jcallaha
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 18:05:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Mihir Lele 2016-10-12 16:00:58 UTC

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

Comment 2 Mihir Lele 2017-04-05 16:56:16 UTC

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

Comment 3 Bernie Hoefer 2017-04-05 17:06:10 UTC

(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.

Comment 4 Bryan Kearney 2018-09-04 18:05:56 UTC

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.