Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propagate resource to member cluster failed. #4999

Open
CharlesQQ opened this issue May 29, 2024 · 6 comments
Open

Propagate resource to member cluster failed. #4999

CharlesQQ opened this issue May 29, 2024 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@CharlesQQ
Copy link
Contributor

CharlesQQ commented May 29, 2024

What happened:

deployment already exist in member cluster; pp's spec.conflictResolution=Overwrite, but found deployment not propagated successfully
image

work object has message: message: 'Failed to apply all manifests (0/1): resource(kind=Deployment, default/xxx) already exists in the cluster cluster1 and the work.karmada.io/conflict-resolution strategy value is empty, Karmada will not manage this resource'

If I delete deployement in member cluster, workload propagate succeed

What you expected to happen:

deployment Propagate succeed
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment: V1.29

  • Karmada version: V1.9.0
  • kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
  • Others:
@CharlesQQ CharlesQQ added the kind/bug Categorizes issue or PR as related to a bug. label May 29, 2024
@CharlesQQ
Copy link
Contributor Author

/close

@karmada-bot
Copy link
Collaborator

@CharlesQQ: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@CharlesQQ
Copy link
Contributor Author

/reopen

@karmada-bot karmada-bot reopened this May 29, 2024
@karmada-bot
Copy link
Collaborator

@CharlesQQ: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@XiShanYongYe-Chang
Copy link
Member

Ask to feature owner @chaosi-zju to help take a look.
cc @chaosi-zju

@chaosi-zju
Copy link
Member

@CharlesQQ hello, can you describe the steps about how to produce it?

the work.karmada.io/conflict-resolution strategy value is empty

by the way, can you check whether the corresponding binding and work has the work.karmada.io/conflict-resolution label?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Status: No status
Development

No branches or pull requests

4 participants