-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
What happened:
1、execution_controller updates member workload fail because of conflict, AppliedFailed is added in work's status.
2、After returns error, execution_controller retries, and updates member workload success.
3、But when setting Applied condition to AppliedSuccessful in function updateAppliedCondition, if the work object in informer cache is not updated, controller will not set AppliedSuccessful.
4、Because of GenerationChangedPredicate event filter, new event will not come if only work's status changes.
5、appliedMessage will be added to rb status, and the status from member workload will be empty.
6、Host workload's status will be empty.
What you expected to happen:
Host workload's status will not be effected.
How to reproduce it (as minimally and precisely as possible):
Hard to reproduce
Anything else we need to know?:
I think maybe GenerationChangedPredicate can be removed from execution_controller?
Environment:
- Karmada version:
- kubectl-karmada or karmadactl version (the result of
kubectl-karmada versionorkarmadactl version): - Others:
Metadata
Metadata
Assignees
Labels
Type
Projects
Status