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

Results couldn't be loaded due to an error #202

Closed
michas2 opened this issue Apr 30, 2022 · 11 comments
Closed

Results couldn't be loaded due to an error #202

michas2 opened this issue Apr 30, 2022 · 11 comments

Comments

@michas2
Copy link

michas2 commented Apr 30, 2022

I installed forecastle using helm install forecastle stakater/forecastle.

When I access the web interface I only get "Results couldn't be loaded due to an error".
There is no error shown in kubectl logs.

What might be wrong? Is there a way to debug further?

@michas2
Copy link
Author

michas2 commented May 1, 2022

From what I see, the api/apps endpoint simply return null.
Looks like the AppsHandler in the backend is unhappy, but for some reason does not log any error message.
I'm not sure how to debug this any further without major effort.

@muammercakir
Copy link

I have the same issue with the latest helm chart version 1.0.97.

@igorcoding
Copy link

igorcoding commented Sep 19, 2022

I'm stuck with the same issue. Is there any solution to this?

UPD: seems like forecastle does not react to ForecastleApp CRD. Apps exposed using ingress annotations work fine, but I currently cannot add an external app using the CRD - it just does not appear.

UPD2: Ok, sorry :) I should have enabled crdEnabled: true in the config for this to work.

@Xide
Copy link

Xide commented Sep 22, 2022

I encountered the same issue after a fresh Forecastle install.
The issue for me was that had not configured any ingress with a forecastle.stakater.com/expose annotation yet.
After adding this annotation to an ingress, the error message was gone.

@rasheedamir
Copy link
Member

@davidkarlsen can you please check this issue as well?

@davidkarlsen
Copy link
Collaborator

I can have a look, can you add some stack-traces please?

@karl-johan-grahn
Copy link
Contributor

@michas2 can you add stack-traces please?

@andrasnemethcg
Copy link

In a fresh installation of forecastle (1.0.131), we same error as above. The api/apps returns null.

The crd is installed and I tried both annotating an existing ingress and creating an Kind:ForecastleApp. Namespace selector is any.
There is no error in the pod log. How can I debug further where is the error?

time="2023-10-26T11:09:06Z" level=info msg="Looking for forecastle apps in the following namespaces: * (All Namespaces)" _source="handlers/appsHandler.go:51"

@andrasnemethcg
Copy link

andrasnemethcg commented Oct 26, 2023

In a fresh installation of forecastle (1.0.131), we same error as above. The api/apps returns null.

The crd is installed and I tried both annotating an existing ingress and creating an Kind:ForecastleApp. Namespace selector is any. There is no error in the pod log. How can I debug further where is the error?

time="2023-10-26T11:09:06Z" level=info msg="Looking for forecastle apps in the following namespaces: * (All Namespaces)" _source="handlers/appsHandler.go:51"

After some digging around, it seems that instanceName filtered out my applications. So, now it is set to empty and works.

@MuneebAijaz
Copy link
Contributor

@andrasnemethcg , @michas2 can we close this issue if its fixed on your side? or do we need some code change?

@andrasnemethcg
Copy link

andrasnemethcg commented Nov 29, 2023

@andrasnemethcg , @michas2 can we close this issue if its fixed on your side? or do we need some code change?

My problem was solved by removing the instanceName. Ok to close from my point of view. However, this is not my issue, but @michas2 's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants