On Mon, Oct 04, 2010 at 07:11:26PM +0100, Soren Hansen wrote: > If you change nova-manage to simply ignore it when it comes across data > the violates our currently expected data model, you're just delaying the > catastrophe until another part of the code comes across and tries to > handle this data. nova-manage is the only UI nova has, so it's the best > place imaginable to be notified about these things.
I didn't change nova-manage to "simply ignore it" -- it prints None. I'm quite happy to print "Warning warning danger danger" if you want, if you think that this really does violate the expected datamodel. Exploding isn't acceptable though -- debugging is a lot harder if the tools just throw a backtrace instead of diagnosing the problem for you. I agree that you should be notified about this problem by nova-manage. I don't agree that a backtrace is an acceptable way to do that. -- nova-manage project zip and nova-manage vpn list broken by change in DB semantics when networks are missing https://bugs.launchpad.net/bugs/654025 You received this bug notification because you are a member of Registry Administrators, which is subscribed to OpenStack. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
