-
Notifications
You must be signed in to change notification settings - Fork 378
Closed
Labels
area/backup-targetBackup target: S3, NFSBackup target: S3, NFSarea/performanceSystem function: PerformanceSystem function: Performancebackport-needed/1.4.3kind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releaseknown-issue-v1.4.2priority/0Must be fixed in this releaseMust be fixed in this releaserequire/docDocumentation update needed.Documentation update needed.severity/3Function working but has a major or UI issue w/ workaroundFunction working but has a major or UI issue w/ workaround
Milestone
Description
Describe the bug
High load of cpu by harvester process after upgrading from v1.4.1 to v1.4.2
To Reproduce
Steps to reproduce the behavior:
- Deploying harvester v1.4.1
- Configuring a backup target (example nfs)
- Upgrading to harvester v1.4.2
Expected behavior
Harvester deployment should not have high CPU loading
Environment
- Harvester ISO version: v1.4.2
- Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):
Additional context
The workaround is putting a value in the refresh interval of the backup target option post-upgrade
Metadata
Metadata
Assignees
Labels
area/backup-targetBackup target: S3, NFSBackup target: S3, NFSarea/performanceSystem function: PerformanceSystem function: Performancebackport-needed/1.4.3kind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releaseknown-issue-v1.4.2priority/0Must be fixed in this releaseMust be fixed in this releaserequire/docDocumentation update needed.Documentation update needed.severity/3Function working but has a major or UI issue w/ workaroundFunction working but has a major or UI issue w/ workaround
Type
Projects
Status
Closed