tempest.scenario.test_server_basic_ops.TestServerBasicOps failing on metadata service

Bug #1965546 reported by Arx Cruz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

The test is not being able to connect to the metadata service:

    Response - Headers: {'content-type': 'application/json', 'content-length': '882', 'x-openstack-request-id': 'req-6ef5fe44-ddc7-4204-8b39-2394f33c1092', 'date': 'Fri, 18 Mar 2022 09:58:06 GMT', 'connection': 'close', 'status': '200', 'content-location': 'http://192.168.24.3:9696/v2.0/floatingips/c50d287b-09ec-4c02-b9d6-c8e9b2cc7a4e'}
        Body: b'{"floatingip": {"id": "c50d287b-09ec-4c02-b9d6-c8e9b2cc7a4e", "tenant_id": "74bdbeb76f294eb496d196452062ba42", "floating_ip_address": "192.168.24.186", "floating_network_id": "fb39f559-c0eb-4d25-9c5f-bef3ae00b4a3", "router_id": "e3106cee-1926-4dc5-95ab-041613bcccc4", "port_id": "1290c567-b1c4-4bde-b793-09c4a22561c3", "fixed_ip_address": "10.100.0.7", "status": "ACTIVE", "description": "", "qos_policy_id": null, "port_details": {"name": "", "network_id": "cc73a025-4fa2-444c-bc6d-535db6605e77", "mac_address": "fa:16:3e:bf:74:68", "admin_state_up": true, "status": "ACTIVE", "device_id": "715767cf-7dca-42f0-9f5c-6d61a88ef5f9", "device_owner": "compute:nova"}, "dns_domain": "", "dns_name": "", "port_forwardings": [], "tags": [], "created_at": "2022-03-18T09:57:56Z", "updated_at": "2022-03-18T09:58:00Z", "revision_number": 2, "project_id": "74bdbeb76f294eb496d196452062ba42"}}'
2022-03-18 09:58:06,755 180551 INFO [tempest.lib.common.ssh] Creating ssh connection to '192.168.24.186:22' as 'cirros' with public key authentication
2022-03-18 09:58:13,881 180551 WARNING [tempest.lib.common.ssh] Failed to establish authenticated ssh connection to cirros@192.168.24.186 ([Errno None] Unable to connect to port 22 on 192.168.24.186). Number attempts: 1. Retry after 2 seconds.
2022-03-18 09:58:16,432 180551 INFO [paramiko.transport] Connected (version 2.0, client dropbear_2018.76)
2022-03-18 09:58:16,598 180551 INFO [paramiko.transport] Authentication (publickey) successful!
2022-03-18 09:58:16,598 180551 INFO [tempest.lib.common.ssh] ssh connection to cirros@192.168.24.186 successfully created
2022-03-18 09:58:16,599 180551 DEBUG [tempest.lib.common.utils.linux.remote_client] Remote command: set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; curl http://169.254.169.254/latest/meta-data/public-ipv4
2022-03-18 09:58:16,600 180551 INFO [tempest.lib.common.ssh] Creating ssh connection to '192.168.24.186:22' as 'cirros' with public key authentication
2022-03-18 09:58:16,613 180551 INFO [paramiko.transport] Connected (version 2.0, client dropbear_2018.76)
2022-03-18 09:58:16,719 180551 INFO [paramiko.transport] Authentication (publickey) successful!
2022-03-18 09:58:16,720 180551 INFO [tempest.lib.common.ssh] ssh connection to cirros@192.168.24.186 successfully created
2022-03-18 09:58:18,021 180551 ERROR [tempest.lib.common.utils.linux.remote_client] (TestServerBasicOps:test_server_basic_ops) Executing command on 192.168.24.186 failed. Error: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; curl http://169.254.169.254/latest/meta-data/public-ipv4' failed, exit status: 7, stderr:
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed

  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 169.254.169.254 port 80: Connection refused

Last time this test pass was 3 days ago, and 3 days ago, also, this test fail in another periodic job, wit a slightly different error:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/tempest/common/utils/__init__.py", line 70, in wrapper
    return f(*func_args, **func_kwargs)
  File "/usr/lib/python3.9/site-packages/tempest/scenario/test_server_basic_ops.py", line 141, in test_server_basic_ops
    self.verify_metadata()
  File "/usr/lib/python3.9/site-packages/tempest/scenario/test_server_basic_ops.py", line 86, in verify_metadata
    if not test_utils.call_until_true(exec_cmd_and_verify_output,
  File "/usr/lib/python3.9/site-packages/tempest/lib/common/utils/test_utils.py", line 116, in call_until_true
    if func(*args, **kwargs):
  File "/usr/lib/python3.9/site-packages/tempest/scenario/test_server_basic_ops.py", line 83, in exec_cmd_and_verify_output
    self.assertEqual(self.ip, result, msg)
  File "/usr/lib/python3.9/site-packages/testtools/testcase.py", line 393, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/usr/lib/python3.9/site-packages/testtools/testcase.py", line 480, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = '192.168.24.151'
actual = '''\
<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>
'''
: Failed while verifying metadata on server. Result of command "curl http://169.254.169.254/latest/meta-data/public-ipv4" is NOT "192.168.24.151".

In this case, on March 15, it was able to curl the metadata service, but it return a gateway timeout.

Logs on March 15:
https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-standalone-full-tempest-scenario-master/21b3275/logs/undercloud/var/log/tempest/stestr_results.html.gz

Logs today:
https://logserver.rdoproject.org/25/39025/12/check/periodic-tripleo-ci-centos-9-standalone-full-tempest-scenario-master/860a762/logs/undercloud/var/log/tempest/stestr_results.html.gz

Arx Cruz (arxcruz)
summary: - tempest.scenario.test_server_basic_ops.TestServerBasicOps failing o
+ tempest.scenario.test_server_basic_ops.TestServerBasicOps failing on
+ metadata service
Revision history for this message
Arx Cruz (arxcruz) wrote :
Revision history for this message
Arx Cruz (arxcruz) wrote :

Moving to doe since we did not saw it anymore

Changed in tripleo:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.