Bug 2093883
| Summary: | [kickstart tests failure] 01:22:35,944 INFO rhsm-service:configparser.NoSectionError: No section: 'logging' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Radek Vykydal <rvykydal> | ||||
| Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> | ||||
| Status: | VERIFIED --- | QA Contact: | Jan Stodola <jstodola> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 9.0 | CC: | anaconda-maint-list, jkonecny, jstodola, mkolman, redakkan, release-test-team | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 9.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | subscription-manager-1.29.34-1.el9 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 2076948 | Environment: | |||||
| Last Closed: | 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: | |||||||
| Bug Depends On: | 2076948 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Radek Vykydal
2022-06-06 09:48:52 UTC
We've seen the issue for the first time in daily kickstart tests on RHEL 9. So it seems to be occuring much more rarely than on RHEL 8 (original of this clone). RHEL 9 version of bug 2076948. Note on reproducibility: we hit the issue in our daily kickstart tests (we run ~200 tests each daily) RHEL 8: ~ 1/700 tests RHEL 9: ~ 1/6000 tests We are able to run about 800 tests per day if we use all the resources that we do not use for current CI and daily workflows. We have not seen the issue with the latest builds, so the fix seems to work as intended. We haven't hit the issue in our daily kickstart tests since the inclusion of this fix so from our POV it seems to be fixed. Based on the confirmation from Radek , moving the bug to verified!! |