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

Dashboard errors if pod's owner reference is not supported #3251

Closed
yqwang-ms opened this issue Sep 4, 2018 · 7 comments
Closed

Dashboard errors if pod's owner reference is not supported #3251

yqwang-ms opened this issue Sep 4, 2018 · 7 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@yqwang-ms
Copy link

Steps to reproduce

The pod is created as:
podObject.OwnerReferences = []meta.OwnerReference{*meta.NewControllerRef(configMapObject, ConfigMapGroupVersionKind)}

Environment
Installation method: 
Kubernetes version:
Dashboard version: v1.8.1
Commit: 7b3553aecf28224ef7275e157b5bba7dd23f436a
Observed result

Dashboard reported Internal Server Error (500):

Unknown reference kind ConfigMap

Comments

By setting the owner is also a controller, the Pod functions normally, except for its detail cannot be viewed from kube dashboard, and the dashboard shows error:
"Unknown reference kind ConfigMap".

Seems this is related to #3158

Please help :)

@maciaszczykm
Copy link
Member

We have to solve it because there are multiple resources that are not supported.

@maciaszczykm maciaszczykm changed the title Dashboard 500 error if ConfigMap is set to be the controller owner of Pod Dashboard errors if pod's owner reference is not supported Sep 4, 2018
@maciaszczykm
Copy link
Member

@yqwang-ms If you are familiar with Go, perhaps you would be interested in fixing this issue so we can release fix for it :) We are quite occupied with Angular migration and we do not have time for it at the moment.

@maciaszczykm maciaszczykm added kind/bug Categorizes issue or PR as related to a bug. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 4, 2018
@yqwang-ms
Copy link
Author

Thanks @maciaszczykm for the comment, I will try first but not sure :)

@yqwang-ms
Copy link
Author

Hi @maciaszczykm I have not got free to look into the code, do you have resource to fix it now? :)

@maciaszczykm
Copy link
Member

At the moment I am focused on getting ng migration done. Perhaps someone else will pick it up.

@mrow4a
Copy link

mrow4a commented Apr 29, 2019

@maciaszczykm is this planned to be included in next release, or earliest 2.0.0? It is tiny fix, but would be great to have it for these who already use CRDs early (kubeflow/spark-operator#484).

@maciaszczykm
Copy link
Member

Earliest in 2.0.0, @mrow4a. If you would be willing to create bugfix branch on top of old release then we can get it released perhaps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants