Bug 1878264

Summary: Facing warning messages "failed to get imageFs info: non-existent label "crio-images" after upgrading to OCP 4.4.12
Product: OpenShift Container Platform Reporter: Peter Hunt <pehunt>
Component: NodeAssignee: Peter Hunt <pehunt>
Status: CLOSED ERRATA QA Contact: Sunil Choudhary <schoudha>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: aos-bugs, asheth, dshumake, harpatil, jokerman, mharri, minmli, nagrawal, obulatov, pehunt, rdomnu, wzheng
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1866702
: 1878265 (view as bug list) Environment:
Last Closed: 2020-09-21 17:42:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1866702    
Bug Blocks: 1878265    

Comment 4 Sunil Choudhary 2020-09-17 10:41:27 UTC 
Verified on 4.5.0-0.nightly-2020-09-14-124053. Created a custom Container Runtime Config with pid limit of 8192. Do not see non-existent label messages in logs or while describing node.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-09-14-124053   True        False         141m    Cluster version is 4.5.0-0.nightly-2020-09-14-124053


$ oc get containerruntimeconfig custom-ctrcfg -o yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: ContainerRuntimeConfig
metadata:
  creationTimestamp: "2020-09-17T09:04:12Z"
  finalizers:
  - 99-worker-dd657657-5ca7-445e-8358-661a6e9ecba1-containerruntime
  generation: 1
  managedFields:
  - apiVersion: machineconfiguration.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"99-worker-dd657657-5ca7-445e-8358-661a6e9ecba1-containerruntime": {}
      f:spec:
        f:containerRuntimeConfig:
          f:logSizeMax: {}
          f:overlaySize: {}
      f:status:
        .: {}
        f:conditions: {}
        f:observedGeneration: {}
    manager: machine-config-controller
    operation: Update
    time: "2020-09-17T09:04:12Z"
  - apiVersion: machineconfiguration.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:containerRuntimeConfig:
          .: {}
          f:pidsLimit: {}
        f:machineConfigPoolSelector:
          .: {}
          f:matchLabels:
            .: {}
            f:custom: {}
    manager: oc
    operation: Update
    time: "2020-09-17T09:04:12Z"
  name: custom-ctrcfg
  resourceVersion: "40751"
  selfLink: /apis/machineconfiguration.openshift.io/v1/containerruntimeconfigs/custom-ctrcfg
  uid: dfe48eb8-14b2-4a5f-bbd0-3919294b1648
spec:
  containerRuntimeConfig:
    pidsLimit: 8192
  machineConfigPoolSelector:
    matchLabels:
      custom: pids-limit
status:
  conditions:
  - lastTransitionTime: "2020-09-17T09:04:12Z"
    message: Success
    status: "True"
    type: Success
  observedGeneration: 1
Comment 6 errata-xmlrpc 2020-09-21 17:42:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5.11 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3719