[BUG] Errors in synchronization process of deviceprofile between cloud and edge

[qclc]

What happened:

• Problem one: After deleting the deviceprofile through edgex-core-metadata, the corresponding deviceprofile on openyurt will not be deleted;
• Problem two: With the restart of yurt-device-controller, openyurt may have a deviceprofile with two nodepool prefixes in its name.

What you expected to happen:

1. After deleting the deviceprofile through edgex-core-metadata, the corresponding deviceprofile on openyurt will be deleted;
2. During the synchronization process, no deviceprofiles whose names contain the two nodepool prefixes will appear.

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

• Problem one：
  1. Delete a deviceprofile object via edgex-core-metadata as follows： curl -X 'DELETE' 'http://edgex-core-metadata:30081/api/v1/deviceprofile/name/[device profile name]' -H 'accept: */*'
• Problem two：
  1. The operating environment is normal, and the cloud-edge resources are consistent;
  2. Delete a deviceprofile object via edgex-core-metadata;
  3. Restart yurt-device-controller, then openyurt will have a deviceprofile with two nodepool prefixes in its name.

Anything else we need to know?:

Environment:

• OpenYurt version:
• Kubernetes version (use kubectl version):
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

others

/kind bug

[openyurt-bot]

@qclc: The label(s) kind/bug cannot be applied, because the repository doesn't have them

In response to [this](https://github.com/openyurtio/yurt-device-controller/issues/18): > > > >**What happened**: >- **Problem one:** After deleting the deviceprofile through edgex-core-metadata, the corresponding deviceprofile on openyurt will not be deleted; >- **Problem two:** With the restart of yurt-device-controller, openyurt may have a deviceprofile with two nodepool prefixes in its name. > >**What you expected to happen**: >1. After deleting the deviceprofile through edgex-core-metadata, the corresponding deviceprofile on openyurt will be deleted; >2. During the synchronization process, no deviceprofiles whose names contain the two nodepool prefixes will appear. > >**How to reproduce it (as minimally and precisely as possible)**: >- **Problem one：** > 1. Delete a deviceprofile object via edgex-core-metadata as follows： > `curl -X 'DELETE' 'http://edgex-core-metadata:30081/api/v1/deviceprofile/name/[device profile name]' -H 'accept: */*'` >- **Problem two：** > 1. The operating environment is normal, and the cloud-edge resources are consistent; > 2. Delete a deviceprofile object via edgex-core-metadata; > 3. Restart yurt-device-controller, then openyurt will have a deviceprofile with two nodepool prefixes in its name. > >**Anything else we need to know?**: > >**Environment**: >- OpenYurt version: >- Kubernetes version (use `kubectl version`): >- OS (e.g: `cat /etc/os-release`): >- Kernel (e.g. `uname -a`): >- Install tools: >- Others: > >**others** > >/kind bug > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[qclc]

/assign @qclc