This bug was fixed in the package nova -
2012.1~e3~20120113.12049-0ubuntu1
---
nova (2012.1~e3~20120113.12049-0ubuntu1) precise; urgency=low
[Chuck Short]
* New upstream version.
* debian/nova_sudoers, debian/nova-common.install,
Switch out to nova-rootwrap. (LP: #681774)
** Branch linked: lp:~ubuntu-server-dev/nova/essex
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/681774
Title:
nova_sudoers is brittle, often out of date, and too permissive
To
as part of nova-rootwrap blueprint
** Changed in: nova (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/681774
Title:
nova_sudoers
** Tags removed: server-o-rs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/681774
Title:
nova_sudoers is brittle, often out of date, and too permissive
To manage notifications about
** Tags added: server-o-rs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/681774
Title:
nova_sudoers is brittle, often out of date, and too permissive
To manage notifications about
** Changed in: nova (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/681774
Title:
nova_sudoers is brittle, often out of date, and too
Separating nova_sudoers into node-specific files sounds like a good idea
too (nova user is more exposed on API nodes, and API nodes actually do
not need a nova user that has the power of screwing up your network
configuration)
** Changed in: nova (Ubuntu)
Status: Confirmed = Triaged
**
