openstack-tox-cover/tox-sanity-py39 job failure in openstack/tripleo-repos

Bug #2002112 reported by Sandeep Yadav
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Unassigned

Bug Description

Description:-

openstack-tox-cover job failing with below error:-

https://8d467ce3102205a450c5-3e96f4a6059887188f427c1d1030c3e5.ssl.cf2.rackcdn.com/869446/1/check/openstack-tox-cover/e3ece1f/job-output.txt

~~~
2023-01-06 11:15:55.624445 | ubuntu-jammy | ==============================
2023-01-06 11:15:55.624459 | ubuntu-jammy | Failed 1 tests - output below:
2023-01-06 11:15:55.624470 | ubuntu-jammy | ==============================
2023-01-06 11:15:55.624481 | ubuntu-jammy |
2023-01-06 11:15:55.624498 | ubuntu-jammy | tests.unit.get_hash.test_tripleo_get_hash.TestGetHash.test_verbose_logging_on
2023-01-06 11:15:55.624541 | ubuntu-jammy | -----------------------------------------------------------------------------
2023-01-06 11:15:55.624565 | ubuntu-jammy |
2023-01-06 11:15:55.624586 | ubuntu-jammy | Captured traceback:
2023-01-06 11:15:55.624607 | ubuntu-jammy | ~~~~~~~~~~~~~~~~~~~
2023-01-06 11:15:55.624631 | ubuntu-jammy | Traceback (most recent call last):
2023-01-06 11:15:55.624652 | ubuntu-jammy |
2023-01-06 11:15:55.624673 | ubuntu-jammy | File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
2023-01-06 11:15:55.624692 | ubuntu-jammy | return func(*newargs, **newkeywargs)
2023-01-06 11:15:55.624704 | ubuntu-jammy |
2023-01-06 11:15:55.624715 | ubuntu-jammy | File "/home/zuul/src/opendev.org/openstack/tripleo-repos/tests/unit/get_hash/test_tripleo_get_hash.py", line 70, in test_verbose_logging_on
2023-01-06 11:15:55.624726 | ubuntu-jammy | self.assertIn('Logging level set to DEBUG', debug_msgs)
2023-01-06 11:15:55.624737 | ubuntu-jammy |
2023-01-06 11:15:55.624749 | ubuntu-jammy | File "/usr/lib/python3.10/unittest/case.py", line 1112, in assertIn
2023-01-06 11:15:55.624770 | ubuntu-jammy | self.fail(self._formatMessage(msg, standardMsg))
2023-01-06 11:15:55.624793 | ubuntu-jammy |
2023-01-06 11:15:55.624815 | ubuntu-jammy | File "/usr/lib/python3.10/unittest/case.py", line 675, in fail
2023-01-06 11:15:55.624831 | ubuntu-jammy | raise self.failureException(msg)
2023-01-06 11:15:55.624842 | ubuntu-jammy |
2023-01-06 11:15:55.624852 | ubuntu-jammy | AssertionError: 'Logging level set to DEBUG' not found in []
~~~~

tox-sanity-py39 failing with below:-

https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_083/869446/1/check/tox-sanity-py39/083e7ea/job-output.txt

~~~
2023-01-06 11:17:06.877535 | ubuntu-focal | sanity: 524 D accepted PythonInfo(spec=CPython3.8.10.final.0-64, system=/usr/bin/python3.8, exe=/home/zuul/src/opendev.org/openstack/tripleo-repos/.tox/.tox/bin/python, platform=linux, version='3.8.10 (default, Nov 14 2022, 12:59:47) \n[GCC 9.4.0]', encoding_fs_io=utf-8-utf-8) [virtualenv/discovery/builtin.py:65]
2023-01-06 11:17:06.917188 | ubuntu-focal | sanity: 564 W commands[0]> stestr run --slowest [tox/tox_env/api.py:427]
2023-01-06 11:17:06.923333 | ubuntu-focal | sanity: 570 C exit 2 (0.00 seconds) /home/zuul/src/opendev.org/openstack/tripleo-repos> stestr run --slowest [tox/execute/api.py:275]
2023-01-06 11:17:06.924981 | ubuntu-focal | sanity: FAIL code 2 (0.10=setup[0.10]+cmd[0.00] seconds)
2023-01-06 11:17:06.925032 | ubuntu-focal | evaluation failed :( (0.41 seconds)
~~~

Tags: ci
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-repos (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-repos/+/869548

Revision history for this message
Marios Andreou (marios-b) wrote (last edit ):

For the verbose logging bug I can recreate it locally and I don't know yet why it broke (it has been running for a long time/since it merged with the original tests).

The test is at [1] and the code it is testing (writing with .debug level) is at [2].

For the tox-sanity-py39 i cannot re-create it locally. Noting that we already have py39 coverage with the openstack-tox-py39 job - disabling sanity-py39

we need to unblock the tripleo-repos gate and we can continue to investigate and re-enable the job/tests once we have proper fixes (I think it is 2 different issues but we can track as a single bug for now).

I just posted that to unblock the gate: https://review.opendev.org/c/openstack/tripleo-repos/+/869548 Temp disable verbose logging test and py39-sanity test

[1] https://opendev.org/openstack/tripleo-repos/src/commit/0e680e1f28d5a3bbf827fe17194d6fd8f97ff1ec/tests/unit/get_hash/test_tripleo_get_hash.py#L54
[2] https://opendev.org/openstack/tripleo-repos/src/commit/0e680e1f28d5a3bbf827fe17194d6fd8f97ff1ec/plugins/module_utils/tripleo_repos/get_hash/__main__.py#L80

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-repos (master)

Reviewed: https://review.opendev.org/c/openstack/tripleo-repos/+/869548
Committed: https://opendev.org/openstack/tripleo-repos/commit/e6c52d03712d3cfa08b6924ce2a7cde7018a44bf
Submitter: "Zuul (22348)"
Branch: master

commit e6c52d03712d3cfa08b6924ce2a7cde7018a44bf
Author: Marios Andreou <email address hidden>
Date: Mon Jan 9 12:24:21 2023 +0200

    Temp disable verbose logging test and py39-sanity test

    As described in related-bug the tripleo-repos gate is blocked
    on failing tox-cover and tox-sanity-py39 jobs.

    The verbose logging test is a nice to have but not critical and we
    already have py39 coverage with openstack-tox-py39. The verbose log
    test can be re-enabled once we have a fix but for now we need to
    unblock the gate.

    Related-Bug: 2002112

    Change-Id: Ia7a1e840f878def13e454c44741fb30702d8a975

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.