-
Notifications
You must be signed in to change notification settings - Fork 1k
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 - Error Loading Project Configs #4981
Comments
I am facing the same issue |
limited knowledge on UI part, but I believe this PR should fix that. However, it's not part of the |
@redhatHameed it doesn't appear to resolve the issue... i just ran the latest code w/ - $ make -C infra/feast-operator install deploy IMG=quay.io/feastdev-ci/feast-operator:develop FS_IMG=quay.io/feastdev-ci/feature-server:develop
$ kubectl apply -f infra/feast-operator/config/samples/v1alpha1_featurestore_all_services_default.yaml |
@tchughesiv thanks for verifying, can you make sure that while loading the page you see the PR code changes going using developer tools/console . |
@redhatHameed it's not showing the latest code changes... even when specifying a recent commit - $ make -C infra/feast-operator install deploy IMG=quay.io/feastdev-ci/feast-operator:197a55f232733402a9632ca492f0fc12f0197d6c FS_IMG=quay.io/feastdev-ci/feature-server:197a55f232733402a9632ca492f0fc12f0197d6c
$ kubectl apply -f infra/feast-operator/config/samples/v1alpha1_featurestore_all_services_default.yaml |
Same issue installing and running feast==0.43.0 using |
I'm facing the same issue. I'm getting this error on the UI: |
@nanohanno any idea on this one? |
this has been resolved and can be tested w/ the latest operator & feature-server image development builds - # from the latest master branch, against a kubernetes or openshift cluster
$ git checkout 0145e5501e2c7854628d204cb515270fac3bee7d
$ make -C infra/feast-operator install deploy IMG=quay.io/feastdev-ci/feast-operator:$(git rev-parse HEAD) FS_IMG=quay.io/feastdev-ci/feature-server:$(git rev-parse HEAD)
$ kubectl apply -f infra/feast-operator/config/samples/v1alpha1_featurestore_all_services_default.yaml
$ kubectl wait --for=condition=available --timeout=8m deploy/feast-sample-all-services
$ kubectl exec deploy/feast-sample-all-services -c registry -- feast apply from an openshift cluster, a route will be exposed that you can use to access to UI. $ kubectl port-forward svc/feast-sample-all-services-ui 8080:80 in k8s, after the port-forward, access - http://localhost:8080/ |
Nice! Thanks @tchughesiv for the quick fix. Looking forward to seeing the official release. |
I've searched for similar issues opened previously here, but didn't see any useful information so I'd like to open a new one.
Expected Behavior
The UI loads successfully
Current Behavior
The UI is accessible but can't load anything
Steps to reproduce
I have tried both local setup using the Quickstart guide and deploying to Kubernetes. They have the same issue.
I enabled the DEBUG log of Feast UI container and saw no error.
If I log in into the feast-ui container, I can run feast cli successfully without issue.
Specifications
Possible Solution
The text was updated successfully, but these errors were encountered: