Bug 1870126
| Summary: | tripleo validator healthcheck-service-status thread lock | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | David Vallee Delisle <dvd> |
| Component: | python-tripleoclient | Assignee: | Cédric Jeanneret <cjeanner> |
| Status: | CLOSED ERRATA | QA Contact: | David Rosenfeld <drosenfe> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16.1 (Train) | CC: | cjeanner, emacchi, hbrock, jjoyce, jschluet, jslagle, mbultel, mburns, slinaber, tvignaud |
| Target Milestone: | z2 | Keywords: | Triaged |
| Target Release: | 16.1 (Train on RHEL 8.2) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tripleoclient-12.3.2-1.20200914164926.72161e0.el8ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-28 15:39:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Vallee Delisle
2020-08-19 11:52:47 UTC
Hello David, Care to add "-w 2" to the command? The validator uses "old" code in osp-16.1, we're working hard in order to get the newer thing in place for a zstream. It's probably linked to this code: https://github.com/openstack/python-tripleoclient/blob/stable/train/tripleoclient/v1/tripleo_validator.py#L484 Cheers, C. Cédric, That was my impression as well. I put the strace files and sosreport here [1]. Thanks, DVD [1] http://file.rdu.redhat.com/~dvalleed/bz1870126/ Adding Mathieu, and creating an env to check if passing -w X would be a solution. Hello, I think this issue is now resolved with the latest things we've pushed for z2 - we've switch the whole code to the newer version that doesn't use "thread". Care to confirm once we get a proper build with the new code? Cheers, C. Thanks Cédric, It looks like it's working now. [1]. My only concern now is the ResourceWarning. Is there a way to make it disapear? I know it might cause our cautious customers to open cases. Thanks, DVD [1] ~~~ (undercloud) [stack@undercloud-0 ~]$ openstack tripleo validator run --validation healthcheck-service-status --workers 1 /usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_validator.py:437: ResourceWarning: unclosed file <_io.BufferedReader name=7> gathering_policy=gathering_policy) +--------------------------------------+----------------------------+--------+-----------------------+-------------------------------------+---------------------+-------------+ | UUID | Validations | Status | Host Group(s) | Status by Host | Unreachable Host(s) | Duration | +--------------------------------------+----------------------------+--------+-----------------------+-------------------------------------+---------------------+-------------+ | 5254005a-bc9d-4647-fd51-000000000008 | healthcheck-service-status | PASSED | undercloud, overcloud | compute-0, controller-0, undercloud | | 0:00:23.494 | +--------------------------------------+----------------------------+--------+-----------------------+-------------------------------------+---------------------+-------------+ ~~~ Hello David, that warning isn't due to the validator itself, it's somewhere in openstack clients. There have been some work on them upstream, not sure about the backport status though.. There are such messages for other CLI calls as well :(. I propose to close the current BZ and, if needed, create a new one for those warnings (though they are harmless, it's python3 being stricter than python2.7). Cheers, C. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:4284 |