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

UI界面登不上去 #67

Closed
Erick-shi opened this issue Jul 25, 2024 · 17 comments
Closed

UI界面登不上去 #67

Erick-shi opened this issue Jul 25, 2024 · 17 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Erick-shi
Copy link

当生产token后, token应该是一行,可是粘贴到了web节目中,就换行了,,,是不是bug呢?
image

@Erick-shi Erick-shi added the kind/bug Categorizes issue or PR as related to a bug. label Jul 25, 2024
@warjiang
Copy link
Contributor

It's the view of textarea, in fact no \r\n in the textarea component, maybe you can double check it by view the request in the network panel.

@warjiang
Copy link
Contributor

Is it the same issue with the #66, if true we can solve the problem in dedicated issue.

@axif0
Copy link
Contributor

axif0 commented Jul 27, 2024

@warjiang i generated the token which mentioned Here. And make karmada-dashboard-api run the front-end by seeing here. I couldn't login.

Also in input field, I see when - found it creates a new line. also in Authorization.

How can I solve the issue for login. can you please tell ?

image

(solved)
Runing Karmada Dashboard API server and i can login as well

_output/bin/linux/amd64/karmada-dashboard-api
--karmada-kubeconfig=/home/asif/.kube/karmada.config
--karmada-context=karmada-apiserver
--skip-karmada-apiserver-tls-verify
--kubeconfig=/home/asif/.kube/karmada.config
--context=karmada-host
--insecure-port=8000

@warjiang
Copy link
Contributor

@warjiang i generated the token which mentioned Here. And make karmada-dashboard-api run the front-end by seeing here. I couldn't login.

Also in input field, I see when - found it creates a new line. also in Authorization.

How can I solve the issue for login. can you please tell ?

image

(solved) Runing Karmada Dashboard API server and i can login as well

_output/bin/linux/amd64/karmada-dashboard-api --karmada-kubeconfig=/home/asif/.kube/karmada.config --karmada-context=karmada-apiserver --skip-karmada-apiserver-tls-verify --kubeconfig=/home/asif/.kube/karmada.config --context=karmada-host --insecure-port=8000

It seems that you've already solved it by yourself, right ?

@axif0
Copy link
Contributor

axif0 commented Jul 30, 2024

@warjiang yaa... thank you.

@Erick-shi
Copy link
Author

@warjiang , so how I can solve it?

@warjiang
Copy link
Contributor

warjiang commented Aug 8, 2024

@warjiang , so how I can solve it?

@Erick-shi can you inspect the network xhr request in the browser dev tools, when you click login, it will be an login request be sent, you can filter the xhr request by keyword login, it will give me more details about this issue

@Erick-shi
Copy link
Author

@warjiang , so how I can solve it?

@Erick-shi can you inspect the network xhr request in the browser dev tools, when you click login, it will be an login request be sent, you can filter the xhr request by keyword login, it will give me more details about this issue

image

image

@axif0
Copy link
Contributor

axif0 commented Aug 11, 2024

@Erick-shi hello, did you run the karmada-dashboard-api ? I also face the problem. After running the api I solved it.

@Erick-shi
Copy link
Author

@Erick-shi hello, did you run the karmada-dashboard-api ? I also face the problem. After running the api I solved it.

hello, that's my karmada pod

kube-controller-manager-7b94cb494f-knlv9        0/1     CrashLoopBackOff   64 (22s ago)    17d
[root@k8scluster-manager ~]# kubectl -n karmada-system get pod
NAME                                            READY   STATUS    RESTARTS         AGE
etcd-0                                          1/1     Running   14 (2m38s ago)   17d
karmada-aggregated-apiserver-564c75f4d6-nzqv5   1/1     Running   36 (80s ago)     17d
karmada-apiserver-54bc5656f4-rb898              1/1     Running   17 (110s ago)    17d
karmada-controller-manager-76f67d8f77-n8xlh     1/1     Running   68 (76s ago)     17d
karmada-dashboard-6649bd5d8d-kxkmc              1/1     Running   21 (2m ago)      17d
karmada-dashboard-api-68f4cd9c55-lg549          1/1     Running   11 (76s ago)     3d23h
karmada-dashboard-web-6bb6f998f8-vq25w          1/1     Running   3 (2m38s ago)    4d
karmada-scheduler-55d78d87dc-8jcwl              1/1     Running   44 (2m38s ago)   17d
karmada-webhook-586d65d978-2pkv2                1/1     Running   12 (2m38s ago)   17d
kube-controller-manager-7b94cb494f-knlv9        1/1     Running   65 (71s ago)     17d
[root@k8scluster-manager ~]#

I have run the karmada-dashboard-api but I had't login the dashboard. could you have any word around?

@warjiang
Copy link
Contributor

@warjiang , so how I can solve it?

@Erick-shi can you inspect the network xhr request in the browser dev tools, when you click login, it will be an login request be sent, you can filter the xhr request by keyword login, it will give me more details about this issue

image

image

Hi @Erick-shi , are you trying two kind of our dashboard? The above one is our new dashboard, the one at the bottom is the old version.

@Erick-shi
Copy link
Author

@warjiang , so how I can solve it?

@Erick-shi can you inspect the network xhr request in the browser dev tools, when you click login, it will be an login request be sent, you can filter the xhr request by keyword login, it will give me more details about this issue

image
image

Hi @Erick-shi , are you trying two kind of our dashboard? The above one is our new dashboard, the one at the bottom is the old version.

yes, the two dashboard I have to try,but all is failed.

@warjiang
Copy link
Contributor

warjiang commented Aug 12, 2024

For the newer dashboard, are you still using the same sa token as before or re-generate a new one? Are you using the guide: https://github.com/karmada-io/dashboard/blob/main/docs/user-guide.md

When generating sa token, you should use the right context:
image

@Erick-shi
Copy link
Author

For the newer dashboard, are you still using the same sa token as before or re-generate a new one? Are you using the guide: https://github.com/karmada-io/dashboard/blob/main/docs/user-guide.md

When generating sa token, you should use the right context: image

I had to try use

[root@k8scluster-manager dashboard]# export KUBECONFIG=${HOME}/.kube/karmada.config
[root@k8scluster-manager dashboard]# kubectl config use-context karmada-host
Switched to context "karmada-host".
[root@k8scluster-manager dashboard]# kubectl apply -f  karmada-dashboard-sa.yaml
error: error validating "karmada-dashboard-sa.yaml": error validating data: failed to download openapi: the server could not find the requested resource; if you choose to ignore these errors, turn validation off with --validate=false
[root@k8scluster-manager dashboard]#

I am use kubectl karmada init install the karmada, Is this error related to this?

@Erick-shi
Copy link
Author

For the newer dashboard, are you still using the same sa token as before or re-generate a new one? Are you using the guide: https://github.com/karmada-io/dashboard/blob/main/docs/user-guide.md
When generating sa token, you should use the right context: image

I had to try use

[root@k8scluster-manager dashboard]# export KUBECONFIG=${HOME}/.kube/karmada.config
[root@k8scluster-manager dashboard]# kubectl config use-context karmada-host
Switched to context "karmada-host".
[root@k8scluster-manager dashboard]# kubectl apply -f  karmada-dashboard-sa.yaml
error: error validating "karmada-dashboard-sa.yaml": error validating data: failed to download openapi: the server could not find the requested resource; if you choose to ignore these errors, turn validation off with --validate=false
[root@k8scluster-manager dashboard]#

I am use kubectl karmada init install the karmada, Is this error related to this?

@warjiang hi, I have solve my problem
I must change the context to karmada-apiserver

export KUBECONFIG=/etc/karmada/karmada-apiserver.config

thanks.

@RainbowMango
Copy link
Member

/close
As issue has been resolved.

@karmada-bot
Copy link
Collaborator

@RainbowMango: Closing this issue.

In response to this:

/close
As issue has been resolved.

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.

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

5 participants