Bug 1970037
| Summary: | [4.9.0] Garbage collector not cleaning up directories of removed clusters | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ronnie Lazar <alazar> |
| Component: | assisted-installer | Assignee: | Sarah Lavie <slavie> |
| assisted-installer sub component: | Deployment Operator | QA Contact: | bjacot |
| Status: | CLOSED DUPLICATE | Docs Contact: | |
| Severity: | high | ||
| Priority: | low | CC: | aos-bugs, mfilanov, trwest, yobshans |
| Version: | 4.8 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AI-Team-Hive | ||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1968451 | Environment: | |
| Last Closed: | 2021-12-11 13:51:12 UTC | Type: | --- |
| 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: | 1967773, 1968451 | ||
| Bug Blocks: | |||
|
Description
Ronnie Lazar
2021-06-09 16:56:48 UTC
@masayag Tested this on 2.4.0-DOWNSTREAM-2021-11-02-15-58-38. It looks like directories are not being removed after the cluster resources are deleted. This is coming from the assisted-service log: time="2021-11-05T15:15:19Z" level=warning msg="Failed deleting cluster directory b571aa67-7dac-4787-93ec-6cefe7510306" func=github.com/openshift/assisted-service/internal/cluster.Manager.PermanentClustersDeletion file="/remote-source/assisted-service/app/internal/cluster/cluster.go:1096" error="Failed to delete file /data/b571aa67-7dac-4787-93ec-6cefe7510306: remove /data/b571aa67-7dac-4787-93ec-6cefe7510306: directory not empty" pkg=cluster-stat The directory only contains other empty directories. This is very low priority and I don't think it needs to be addressed immediately. We can push the fix to next release if that is okay. *** This bug has been marked as a duplicate of bug 1967773 *** |