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

objectsearch bug report #444

Open
tangming1996 opened this issue Sep 13, 2024 · 1 comment
Open

objectsearch bug report #444

tangming1996 opened this issue Sep 13, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@tangming1996
Copy link
Contributor

What happened:
After the objectsearch resource is deleted, its associated pod resource remains
What you expected to happen:
After the objectsearch resource is deleted, its associated pod resource is also deleted
How to reproduce it (as minimally and precisely as possible):
Create an objectsearch resource. After the pod instance is created, delete the objectsearch resource and check whether the Pods are also deleted.
Anything else we need to know?:

Environment:
kubernetes version: 1.23.0
kubeedge version: 1.16.1
sedna version: 0.6.0

CloudSide Environment:

Hardware configuration
$ lscpu
# paste output here
OS
$ cat /etc/os-release
# paste output here
Kernel
$ uname -a
# paste output here
Others

EdgeSide Environment:

Hardware configuration
$ lscpu
# paste output here
OS
$ cat /etc/os-release
# paste output here
Kernel
$ uname -a
# paste output here
Others
@tangming1996 tangming1996 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 13, 2024
@tangming1996
Copy link
Contributor Author

The main problem is that the ownerReferences/0/kind field was misrepresented as Name when pod associated the upper objectsearch resource, which should actually be KindName

The bug has since been fixed. #443

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
None yet
Development

No branches or pull requests

1 participant