Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-17899

`oc explain` should work for resource nodes.config.openshift.io /nodes.metrics.k8s.io/events.events.k8s.io/ pods.metrics.k8s.io

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 4.14.0
    • oc
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      `oc explain` will failed with resource nodes.config.openshift.io /nodes.metrics.k8s.io/events.events.k8s.io/ pods.metrics.k8s.io 

      Version-Release number of selected component (if applicable):

      ./oc version 
      Client Version: 4.14.0-0.nightly-2023-08-20-085537
      Kustomize Version: v5.0.1
      Server Version: 4.14.0-0.nightly-2023-08-11-055332
      Kubernetes Version: v1.27.4+deb2c60
       

      How reproducible:

      always 

      Steps to Reproduce:

      1.  `oc api-resources -o name`  to list all the resource for ocp cluster;
      2.  use `oc explain` for the resource list
      
      

      Actual results:

      /oc explain nodes.config.openshift.io
      KIND:       Node
      VERSION:    v1
      
      error: field "io" does not exist
       

      Expected results:

      2.1:  Show correct explain for these resource : nodes.config.openshift.io /nodes.metrics.k8s.io/events.events.k8s.io/ pods.metrics.k8s.io 
      2.2:  If this is not exist resource , should show : error: field "config" does not exist
       

      Additional info:

       
       
       

       
       
       
       

       

              aguclu@redhat.com Arda Guclu
              yinzhou@redhat.com Ying Zhou
              None
              None
              Ying Zhou Ying Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: