yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

It doesn't look like an upstream Nova issue, but rather a package
problem which is not restarting the service after upgrading.


** Changed in: nova
       Status: New => Invalid

-- 
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/1744519

Title:
  console not working after  update nova-consoleauth:amd64
  (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0)

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  After last update on  2018-01-11 , consoles to instances became
  unresponsive. Services were reporting up and running. After a service
  restart for the nova-consoleauth and  nova-novncproxy we regained
  access to console.

  Update history was noting the following:
  Start-Date: 2018-01-11 16:25:39 
  Upgrade: nova-novncproxy:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-common:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), python-nova:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-api-os-compute:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-consoleauth:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-conductor:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-scheduler:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0), nova-cert:amd64 (13.1.4-0ubuntu4.1~cloud0, 13.1.4-0ubuntu4.2~cloud0) 
  End-Date: 2018-01-11 16:25:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1744519/+subscriptions