nova-compute requires root /w connection_type=xenapi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince |
Bug Description
Using 2011.2~bzr971.
When running nova-compute with connection_
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
----
Couple of ways to go about fixing this. Adding a 'sudo chown' to give nova permission to write to the device seems like the simplest way ((especially since nova already has sudo privs). We could also mess with /etc/udev/ and have the devices show up to a special group that the nova user belongs to and thus has write access. Given that we remap the devices for Maverick support already the sudo looks more appealing for now.
Related branches
- Josh Kearney (community): Approve
- Vish Ishaya (community): Approve
- Ewan Mellor (community): Disapprove
-
Diff: 12 lines (+2/-0)1 file modifiednova/virt/xenapi/vm_utils.py (+2/-0)
Changed in nova: | |
assignee: | nobody → Dan Prince (dan-prince) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-2 |
Changed in nova: | |
milestone: | diablo-2 → 2011.3 |
status: | Fix Committed → Fix Released |