Bashism in vznetcfg makes it impossible to use veth in a vz
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vzctl (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: vzctl
In Hardy, the vznetcfg script contains a bashism that makes it impossible to use veth devices. This was fixed in debian unstable and synced in Jaunty.
TEST CASE:
On a functionnal openvz host, create a new vz :
vzctl create 101
Add a veth interface to the vz
vzctl set 101 --netif_add eth0 --save
Try to start the vz:
vzctl start 101
Starting VE ...
VE is mounted
Setting CPU units: 1000
Configure meminfo: 9223372036854775807
Configure veth devices: veth101.0
/usr/sbin/vznetcfg: 20: source: not found
VE start in progress...
The vz starts but the veth device is not configured.
Regression potential:
The fix is a oneliner that removes a bashism, regression potential is very low.
Related branches
Changed in vzctl (Ubuntu Hardy): | |
importance: | Undecided → High |
status: | New → Fix Committed |
tags: | added: verification-done |
Patch was done inline as in debian. I could add a minimal patch system if it's the preffered method.