Bug 2151549
| Summary: | Artifacts of ansible-runner (executed from ovirt-engine) did not clean up as expected | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Kobi Hakimi <khakimi> |
| Component: | ovirt-engine | Assignee: | Dana <delfassy> |
| Status: | CLOSED ERRATA | QA Contact: | Barbora Dolezalova <bdolezal> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5.3 | CC: | emarcus, lleistne, mperina |
| Target Milestone: | ovirt-4.5.3-async | Keywords: | PrioBumpQA |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.5.3.7 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously,the ovirt-enghine ansible-runner artifacts were only cleaned once, and the machine could run out of free disk space on the /var partition. In this release, the artifacts are cleaned periodically according to values defined in the AnsibleRunnerArtifactsCleanupCheckTimeInHours and AnsibleRunnerArtifactsLifetimeInDays engine-config options.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-02-14 13:09:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Files were cleaned up in /var/lib/ovirt-engine/ansible-runner/ after allocated time (for example 1 day). Verified in ovirt-engine-4.5.3.8-0.zstream.20230209080313.git9d0405b2f98.el8.noarch 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 (Moderate: Red Hat Virtualization security and bug fix update), 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/RHSA-2023:0759 |
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).