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

Ingresses List warns pathExistsInSchema has been used without fetching the schema definition #11086

Closed
richard-cox opened this issue May 22, 2024 · 1 comment · Fixed by #11159
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented May 22, 2024

Setup

  • Rancher version:
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

  • schema diet related
  • pathExistsInSchema requires schema networking.k8s.io.ingress to have resources fields via schema definition but none were found. 
    has the schema 'fetchResourceFields' been called?
    
  • get useNestedBackendField() {
      if (!this.cache.useNestedBackendField) {
        this.cache.useNestedBackendField = this.$rootGetters['cluster/pathExistsInSchema'](this.type, 'spec.rules.http.paths.backend.service.name');
      }
    
      return this.cache.useNestedBackendField;
    }
    
  • /v1/schemaDefinitions/networking.k8s.io.ingress is called, so maybe a timing issue

To Reproduce

  • Open dev tools
  • Navigate to Ingress list

Result

  • See warnings in console

Expected Result

  • this has an unknown impact, could be that the list doesn't really need it, could cause info in list not to show
@richard-cox richard-cox added this to the v2.9.0 milestone May 22, 2024
@richard-cox richard-cox self-assigned this May 22, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label May 22, 2024
@richard-cox richard-cox assigned aalves08 and unassigned richard-cox Jun 4, 2024
@yonasberhe23
Copy link
Contributor

e2e test is sufficient! moving to done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
3 participants