We changed the release management from a "delayed-release" to a "direct-release" model [1]. It seems that the fix for this bug merged in the timeframe where we made the transition to the new model and therefore wasn't closed with "Fix-Released" at it should be. => Manually closing this bug with "Fix-Released".
[1] "openstack-dev" ML, 2015-11-23, Doug Hellmann, "[release] process change for closing bugs when patches merge" http://lists.openstack.org/pipermail/openstack-dev/2015-November/080288.html ** Changed in: nova Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1506213 Title: nova.cmd.baseproxy handles errors incorrectly Status in OpenStack Compute (nova): Fix Released Bug description: Nova from master. The module doesn't print error message. If an error occurs in nova.cmd.baseproxy the method exit_with_error is executed that looks as follows: def exit_with_error(msg, errno=-1): print(msg) and sys.exit(errno) So in python 2.7 this method terminates the application without printing anything (unable to flush on time) and in python 3.4 it does strange things because print() returns None. I noticed this bug when I was trying to run nova-novncproxy without novnc istalled. nova-novncproxy was being terminated without any prints. Then I debugged it and found out that it tries to send an error message but it fails. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1506213/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp