Bug 1007476

Summary:	udevadm trigger --type=devices with 70-persistent-net.rules calls ifup on devices whose ifcfg contains ONBOOT=no
Product:	Red Hat Enterprise Linux 6	Reporter:	Assaf Muller <amuller>
Component:	initscripts	Assignee:	Lukáš Nykrýn <lnykryn>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	alonbl, danken, lpeer
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-13 07:00: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:
Embargoed:
Bug Depends On:
Bug Blocks:	1005278

Description Assaf Muller 2013-09-12 14:44:14 UTC

Description of problem:
Calling "udevadm trigger --type=devices" will ifup all network devices, including those with ONBOOT=no in their ifcfg files.

Version-Release number of selected component (if applicable):
udev rpm: udev-147-2.46.el6.x86_64
initscripts rpm: initscripts-9.03.38-1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. ifdown an interface (eth1 for example)
2. set ONBOOT=no in its ifcfg file
3. Call udevadm trigger --type=devices

Actual results:
ifup called on eth1

Expected results:
ifup not called on eth1

Comment 2 Lukáš Nykrýn 2013-09-13 06:40:19 UTC

I think that setting HOTPLUG=no would be a proper solution here.

Comment 3 Alon Bar-Lev 2013-09-13 07:00:56 UTC

(In reply to Lukáš Nykrýn from comment #2)
> I think that setting HOTPLUG=no would be a proper solution here.

Do you mean adding that to all ifcfg files? it is not really an option... but after reviewing the entire initscripts, I understand you point of view.