-
Notifications
You must be signed in to change notification settings - Fork 56
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
Comments
From what I see, the |
I have the same issue with the latest helm chart version 1.0.97. |
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 |
I encountered the same issue after a fresh Forecastle install. |
@davidkarlsen can you please check this issue as well? |
I can have a look, can you add some stack-traces please? |
@michas2 can you add stack-traces please? |
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.
|
After some digging around, it seems that instanceName filtered out my applications. So, now it is set to empty and works. |
@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. |
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?
The text was updated successfully, but these errors were encountered: