Skip to content

UI - Error Loading Project Configs #4981

Closed

Description

@ngoduykhanh

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

Image

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.

(app-root) bash-5.1$ feast feature-views list
/opt/app-root/lib64/python3.11/site-packages/feast/feature_view.py:48: DeprecationWarning: Entity value_type will be mandatory in the next release. Please specify a value_type for entity '__dummy'.
  DUMMY_ENTITY = Entity(
Received base64 encoded feature_store.yaml
NAME                         ENTITIES    TYPE
driver_hourly_stats_fresh    {'driver'}  FeatureView
driver_hourly_stats          {'driver'}  FeatureView
transformed_conv_rate_fresh  {'driver'}  OnDemandFeatureView
transformed_conv_rate        {'driver'}  OnDemandFeatureView

Specifications

  • Version: 0.43
  • Platform: MacOS/Kubernetes
  • Subsystem:

Possible Solution

Activity

  1. itsmano1993 commented on Jan 29, 2025

    @itsmano1993

    I am facing the same issue
    .I am using mac os and I did pip install feast followed by feast ui

  2. redhatHameed commented on Jan 29, 2025

    @redhatHameed
    Contributor

    limited knowledge on UI part, but I believe this PR should fix that. However, it's not part of the 0.43.0 current version.

  3. tchughesiv commented on Jan 29, 2025

    @tchughesiv
    Contributor

    @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
  4. redhatHameed commented on Jan 29, 2025

    @redhatHameed
    Contributor

    @tchughesiv thanks for verifying, can you make sure that while loading the page you see the PR code changes going using developer tools/console .

  5. tchughesiv commented on Jan 29, 2025

    @tchughesiv
    Contributor

    @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
  6. danbaron63 commented on Jan 30, 2025

    @danbaron63
    Contributor

    Same issue installing and running feast==0.43.0 using uv and running the quickstart. Ran plan, apply and then materialize-incremental and got the same UI error with nothing in the logs.

  7. hark444 commented on Jan 30, 2025

    @hark444

    I'm facing the same issue. I'm getting this error on the UI:
    Error loading project configs. There was an error loading the Project Configurations. Please check that feature_store.yaml file is available and well-formed.
    Version: 0.39.0 is working fine, as far as the UI is concerned.

  8. franciscojavierarceo commented on Jan 30, 2025

    @franciscojavierarceo
    Member

    @nanohanno any idea on this one?

  9. tchughesiv commented on Jan 31, 2025

    @tchughesiv
    Contributor

    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.
    from a kubernetes cluster, the following can be done to quickly test the UI -

    $ kubectl port-forward svc/feast-sample-all-services-ui 8080:80

    in k8s, after the port-forward, access - http://localhost:8080/

  10. ngoduykhanh commented on Jan 31, 2025

    @ngoduykhanh
    Author

    Nice! Thanks @tchughesiv for the quick fix. Looking forward to seeing the official release.

  11. unpinned this issue on Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions