yahoo-eng-team team mailing list archive

[Alexander Aleksiyants <aleksiyantsa@xxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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):
  New

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