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

MCP not updating when an invalid MOSC is applied after a valid MOSC in Image Mode

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.20
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • None
    • MCO Sprint 276, MCO Sprint 277, MCO Sprint 278
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When a valid MOSC is applied, the MCP updates successfully. However, if an invalid MOSC is applied afterward, the MOSB fails as expected, but the MCP does not trigger an update. This leads to inconsistent behavior in Image Mode.
          

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

          4.20

      How reproducible:

          Always 

      Steps to Reproduce:

      1.Applied the correct MOSC.
      2.Waited for the MOSB.MCP to be updated.
      3.Edited the MOSC and updated it with the wrong container content.
      4.As expected, the MOSB failed.
      5.However, the MCP update did not happen.     
          

      Actual results:

      $ oc get machineosbuilds
      NAME                                      PREPARED   BUILDING   SUCCEEDED   INTERRUPTED   FAILED   AGE
      worker-5ede68d39b3bfa68d3c9a947ae64898a   False      False      True        False         False    30m
      worker-6eb62d2341a58f864e1c21c97fd31cf3   False      False      False       False         True     7m50s    
      
      $ oc logs machine-os-builder-5fbf8bb795-lpkz5 
      0902 09:14:51.919791       1 reflector.go:946] "Watch close" reflector="github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125" type="*v1.MachineConfigPool" totalItems=8
      I0902 09:16:09.915807       1 reflector.go:946] "Watch close" reflector="github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125" type="*v1.ControllerConfig" totalItems=9
      I0902 09:16:46.912461       1 reflector.go:946] "Watch close" reflector="github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125" type="*v1.MachineOSConfig" totalItems=11
      I0902 09:16:49.914718       1 reflector.go:946] "Watch close" reflector="k8s.io/client-go/informers/factory.go:160" type="*v1.ConfigMap" totalItems=11
      I0902 09:17:11.916807       1 reflector.go:946] "Watch close" reflector="github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125" type="*v1.MachineOSBuild" totalItems=12
      I0902 09:18:15.998385       1 reflector.go:946] "Watch close" reflector="github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125" type="*v1.MachineConfig" totalItems=7

      Expected results:

          The MCP should update and get failed as per this https://github.com/openshift/machine-config-operator/pull/5251

      Additional info:

          

              umohnani Urvashi Mohnani
              rh-ee-ptalgulk Prachiti Talgulkar
              None
              None
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: