← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1830417] [NEW] NoVNCConsoleTestJSON.test_novnc fails in nova-multi-cell job since 5/20

 

Public bug reported:

Ever since we enabled the n-novnc service in the nova-multi-cell job on
May 20:

https://github.com/openstack/nova/commit/c5b83c3fbca83726f4a956009e1788d26bcedde0
#diff-7415f5ff7beee2cdf9ffe31e12e4c086

The
tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc
test has been intermittently failing like this:

2019-05-24 01:55:59.786818 | controller | {2} tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc [0.870805s] ... FAILED
2019-05-24 01:55:59.787151 | controller |
2019-05-24 01:55:59.787193 | controller | Captured traceback:
2019-05-24 01:55:59.787226 | controller | ~~~~~~~~~~~~~~~~~~~
2019-05-24 01:55:59.787271 | controller |     b'Traceback (most recent call last):'
2019-05-24 01:55:59.787381 | controller |     b'  File "/opt/stack/tempest/tempest/api/compute/servers/test_novnc.py", line 194, in test_novnc'
2019-05-24 01:55:59.787450 | controller |     b'    self._validate_rfb_negotiation()'
2019-05-24 01:55:59.787550 | controller |     b'  File "/opt/stack/tempest/tempest/api/compute/servers/test_novnc.py", line 92, in _validate_rfb_negotiation'
2019-05-24 01:55:59.787643 | controller |     b"    'Token must be invalid because the connection '"
2019-05-24 01:55:59.787748 | controller |     b'  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/unittest2/case.py", line 696, in assertFalse'
2019-05-24 01:55:59.787796 | controller |     b'    raise self.failureException(msg)'
2019-05-24 01:55:59.787894 | controller |     b'AssertionError: True is not false : Token must be invalid because the connection closed.'
2019-05-24 01:55:59.787922 | controller |     b''

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22b'AssertionError%3A%20True%20is%20not%20false%20%3A%20Token%20must%20be%20invalid%20because%20the%20connection%20closed.'%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d

My guess would be (without checking the test or the code) that something
isn't properly routing console auth token information/requests to the
correct cell which is why we don't see this in a "single" cell job.

** Affects: nova
     Importance: Medium
         Status: Confirmed


** Tags: cells consoles gate-failure

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

Title:
  NoVNCConsoleTestJSON.test_novnc fails in nova-multi-cell job since
  5/20

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Ever since we enabled the n-novnc service in the nova-multi-cell job
  on May 20:

  https://github.com/openstack/nova/commit/c5b83c3fbca83726f4a956009e1788d26bcedde0
  #diff-7415f5ff7beee2cdf9ffe31e12e4c086

  The
  tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc
  test has been intermittently failing like this:

  2019-05-24 01:55:59.786818 | controller | {2} tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc [0.870805s] ... FAILED
  2019-05-24 01:55:59.787151 | controller |
  2019-05-24 01:55:59.787193 | controller | Captured traceback:
  2019-05-24 01:55:59.787226 | controller | ~~~~~~~~~~~~~~~~~~~
  2019-05-24 01:55:59.787271 | controller |     b'Traceback (most recent call last):'
  2019-05-24 01:55:59.787381 | controller |     b'  File "/opt/stack/tempest/tempest/api/compute/servers/test_novnc.py", line 194, in test_novnc'
  2019-05-24 01:55:59.787450 | controller |     b'    self._validate_rfb_negotiation()'
  2019-05-24 01:55:59.787550 | controller |     b'  File "/opt/stack/tempest/tempest/api/compute/servers/test_novnc.py", line 92, in _validate_rfb_negotiation'
  2019-05-24 01:55:59.787643 | controller |     b"    'Token must be invalid because the connection '"
  2019-05-24 01:55:59.787748 | controller |     b'  File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/unittest2/case.py", line 696, in assertFalse'
  2019-05-24 01:55:59.787796 | controller |     b'    raise self.failureException(msg)'
  2019-05-24 01:55:59.787894 | controller |     b'AssertionError: True is not false : Token must be invalid because the connection closed.'
  2019-05-24 01:55:59.787922 | controller |     b''

  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22b'AssertionError%3A%20True%20is%20not%20false%20%3A%20Token%20must%20be%20invalid%20because%20the%20connection%20closed.'%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d

  My guess would be (without checking the test or the code) that
  something isn't properly routing console auth token
  information/requests to the correct cell which is why we don't see
  this in a "single" cell job.

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


Follow ups