yahoo-eng-team team mailing list archive

[Sylvain Bauza <2028851@xxxxxxxxxxxxxxxxxx>]

Seems to be a regression coming from the automatic rebase of
https://github.com/openstack/tempest/commit/eea2c1cfac1e5d240cad4f8be68cff7d72f220a8

** Also affects: tempest
   Importance: Undecided
       Status: New

** 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/2028851

Title:
   Console output was empty in
  test_get_console_output_server_id_in_shutoff_status

Status in OpenStack Compute (nova):
  Invalid
Status in tempest:
  New

Bug description:
  test_get_console_output_server_id_in_shutoff_status

  https://github.com/openstack/tempest/blob/04cb0adc822ffea6c7bfccce8fa08b03739894b7/tempest/api/compute/servers/test_server_actions.py#L713

  is failing consistently in the nova-lvm job starting on July 24 with
  132 failures in the last 3 days. https://tinyurl.com/kvcc9289

  
  Traceback (most recent call last):
    File "/opt/stack/tempest/tempest/api/compute/servers/test_server_actions.py", line 728, in test_get_console_output_server_id_in_shutoff_status
      self.wait_for(self._get_output)
    File "/opt/stack/tempest/tempest/api/compute/base.py", line 340, in wait_for
      condition()
    File "/opt/stack/tempest/tempest/api/compute/servers/test_server_actions.py", line 213, in _get_output
      self.assertTrue(output, "Console output was empty.")
    File "/usr/lib/python3.10/unittest/case.py", line 687, in assertTrue
      raise self.failureException(msg)
  AssertionError: '' is not true : Console output was empty.

  its not clear why this has started failing. it may be a regression or
  a latent race in the test that we are now failing.

      def test_get_console_output_server_id_in_shutoff_status(self):
          """Test getting console output for a server in SHUTOFF status

          Should be able to GET the console output for a given server_id
          in SHUTOFF status.
          """

          # NOTE: SHUTOFF is irregular status. To avoid test instability,
          #       one server is created only for this test without using
          #       the server that was created in setUpClass.
          server = self.create_test_server(wait_until='ACTIVE')
          temp_server_id = server['id']

          self.client.stop_server(temp_server_id)
          waiters.wait_for_server_status(self.client, temp_server_id, 'SHUTOFF')
          self.wait_for(self._get_output)

  the test does not wait for the VM to be sshable so its possible that
  we are shutting off the VM before it is fully booted and no output has
  been written to the console.

  this failure has happened on multiple providers but only in the nova-lvm job.
  the console behavior is unrelated to the storage backend but the lvm job i belive is using
  lvm on a loopback file so the storage performance is likely slower then raw/qcow.

  so perhaps the boot is taking longer and no output is being written.

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