1Description of problem:{code:none}
If all the images in the pinnedimageset are not pulled before 2 minutes the machineconfignode is degraded


  - lastTransitionTime: "2024-04-23T10:30:46Z"
    message: 'Error: requeue: prefetching images incomplete after: 2m0s'
    reason: PrefetchFailed
    status: "True"
    type: PinnedImageSetsDegraded

    

    pre-merge https://github.com/openshift/machine-config-operator/pull/4303
    

Always
    

    1.  execute this command to fill in the following pinnedimageset


$ oc adm release info   -o pullspec | awk '{print "   - name: " $1}'
   - name: registry.build03.ci.openshift.org/ci-ln-d30q8sk/stable@sha256:7b1b1255645d6fe7a...
   - name: registry.build03.ci.openshift.org/ci-ln-d30q8sk/stable@sha256:42141b60a0ecaaab...
....



apiVersion: machineconfiguration.openshift.io/v1alpha1
kind: PinnedImageSet
metadata:
  [?4ms:
    machineconfiguration.openshift.io/role: worker
  name: my-worker-pinned-images-all
spec:
  pinnedImages:
   - name: registry.build03.ci.openshift.org/ci-ln-d30q8sk/stable@sha256:7b1b1255645d6fe7a...
   - name: registry.build03.ci.openshift.org/ci-ln-d30q8sk/stable@sha256:42141b60a0ecaaab...
......

    

The pinnedimageset will take longer than 2 minutes and the machineconfignodes will be degraded.


    

It is highly unlikely that MCO will be able to pull all the images in a relase in less than 2 minutes, so this timeout will always degrade MCO when we try to pin the release images.

We expect MCO to be able to pull all the images in a relase without being degraded. 

    

This is already planned to increase the timeout in follow-up PRs. This issue will not block the merge. The main goal of this ticket is not to forget that change and it's verification.


    

    Actual results:{code:none}