Bug 1025252

Summary: [RFE] Unified prefix for kernel arguments
Product: [Retired] oVirt Reporter: Fabian Deutsch <fdeutsch>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: bugs, hadong, leiwang, mgoldboi, ovirt-bugs, ovirt-maint, rbalakri, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1028929 (view as bug list) Environment:
Last Closed: 2015-06-05 11:01:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1028929    

Description Fabian Deutsch 2013-10-31 10:22:08 UTC 
Description of problem:
Currently most kernel arguments used by Node are not having a prefix. To prevent collisions (e.g. bug 1020700) with other parts of the system Node's kernel arguments should be prefixed with a common prefix.

Some prefix ideas:
node.
nd.

node.example=foo
nd.example=foo
Comment 1 Sandro Bonazzola 2014-03-04 09:27:06 UTC 
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 2 Sandro Bonazzola 2014-06-11 07:04:45 UTC 
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
Comment 3 Sandro Bonazzola 2014-06-11 07:05:22 UTC 
This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
Comment 4 Itamar Heim 2014-06-29 09:07:10 UTC 
*** Bug 1028929 has been marked as a duplicate of this bug. ***
Comment 5 Fabian Deutsch 2015-04-23 13:54:58 UTC 
This change would be really disruptive for the existing node. And the next gen node will not reuse the current auto-installation logic.