Uploaded image for project: 'OpenShift Hive'
  1. OpenShift Hive
  2. HIVE-2242

hiveadmission: Get rid of warnings about FlowSchema and PriorityLevelConfiguration

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Not a Bug
    • Icon: Minor Minor
    • None
    • None
    • False
    • None
    • False

      W0606 06:20:45.651044       1 reflector.go:424] k8s.io/client-go@v12.0.0+incompatible/tools/cache/reflector.go:169: failed to list *v1beta3.FlowSchema: the server could not find the requested resource
      E0606 06:20:45.651100       1 reflector.go:140] k8s.io/client-go@v12.0.0+incompatible/tools/cache/reflector.go:169: Failed to watch *v1beta3.FlowSchema: failed to list *v1beta3.FlowSchema: the server could not find the requested resource
      W0606 06:20:58.617614       1 reflector.go:424] k8s.io/client-go@v12.0.0+incompatible/tools/cache/reflector.go:169: failed to list *v1beta3.PriorityLevelConfiguration: the server could not find the requested resource
      E0606 06:20:58.617663       1 reflector.go:140] k8s.io/client-go@v12.0.0+incompatible/tools/cache/reflector.go:169: Failed to watch *v1beta3.PriorityLevelConfiguration: failed to list *v1beta3.PriorityLevelConfiguration: the server could not find the requested resource
      

      probably due to an upstream dep that hasn't gotten rid of a removed version.

            leah_leshchinsky Leah Leshchinsky
            efried.openshift Eric Fried
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: