Bug 987522

Summary:	minor errors generated when PXE booting ovirt node
Product:	[Retired] oVirt	Reporter:	jas
Component:	ovirt-node	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.2	CC:	acathrow, fdeutsch, hadong, jboggs, leiwang, mgoldboi, ovirt-bugs, ovirt-maint
Target Milestone:	---
Target Release:	3.4.1
Hardware:	Unspecified
OS:	Linux
Whiteboard:	node
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-30 12:16:46 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:

Description jas 2013-07-23 14:52:21 UTC

Description of problem:

When PXE  booting ovirt node after running:

/mnt/LiveOS/livecd-iso-to-pxeboot /tmp/ovirt-node-iso-2.6.1-20120228.fc18.iso

... and using the default configuration, the node generates these two "harmless" errors:

dracut-cmdline[69]: Warning: Kernel command line option 'rd_NO_LVM' is deprecated, use 'rd.lvm=0' instead

AND

dracut-initqueue[225]: Warning: Kernel command line option 'check' is deprecated, use 'rd.live.check' instead.

This should probably be cleaned up in 3.3, if it hasn't already, and it should be relatively easy to fix.

Comment 1 Fabian Deutsch 2013-11-28 14:29:00 UTC

Hey jas,

thanks for the report.

Ryan,

we need to keep an eye on backwrds compatibility with el6, ubt maybe we can add the kargs depending on the platform.

Comment 2 Ryan Barry 2013-12-02 16:02:42 UTC

Fabian -

I'll check on current images, but I'd be really surprised if this wasn't a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=902424

Comment 3 Sandro Bonazzola 2014-03-04 09:23:10 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 4 Fabian Deutsch 2014-04-30 12:16:46 UTC

I haven't seen this error on the recent isos, probably because of the fix mentioned in comment 2. Closing this, please reopen if necessary.