nova-manage log broken in several ways
Bug #753416 reported by
Soren Hansen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Ken Pepple | ||
Bug Description
"nova-manage log" doesn't work.
a) It assumes everything gets logged to the same file: /var/log/nova.log
b) Its use of utils.execute was never converted to the proper execve style calling.
If we cant fix it by release, I say we rip it out. Clearly no-one is using it anyway.
Related branches
lp:~ken-pepple/nova/lp753416
- Soren Hansen (community): Approve
- Josh Kearney (community): Approve
- Vish Ishaya (community): Approve
-
Diff: 27 lines (+0/-10)1 file modifiedbin/nova-manage (+0/-10)
Revision history for this message
| Ken Pepple (ken-pepple) wrote | #1 |
| Changed in nova: | |
| assignee: | nobody → Ken Pepple (ken-pepple) |
| Changed in nova: | |
| importance: | Undecided → Medium |
| milestone: | none → cactus-rc |
| status: | New → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | cactus-rc → 2011.2 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
agree -- this doesn't make sense in a multi-log world unless we completely rewrite it.
my linked branch removes it ...
(nova)k-2:lp753416 kpepple$ bin/nova-manage log
log does not match any options:
user
account
project
role
shell
vpn
fixed
floating
network
vm
service
db
volume
instance_type
image
flavor
instance
(nova)k-2:lp753416 kpepple$