-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.19
-
Low
-
None
-
1
-
MCO Sprint 272
-
1
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
On the application of an invalid PinnedImageSet (PIS) resource, there is a typo in the `MachineConfigNodePinnedImageSetsDegraded` state's message field in the MachineConfigNode's (MCN) conditions list.
Version-Release number of selected component (if applicable):
This typo was introduced in 4.19, so it can be seen in both 4.19 & 4.20.
How reproducible:
Always when applying an invalid PIS.
Steps to Reproduce:
1. Launch a 4.20 or 4.19 cluster with tech preview enabled. Use the following launch command to create a cluster using ClusterBot.
launch 4.20 aws,techpreview
2. Apply an invalid PIS, such as the below example.
apiVersion: machineconfiguration.openshift.io/v1 kind: PinnedImageSet metadata: name: test-pinned labels: machineconfiguration.openshift.io/role: "worker" spec: pinnedImages: - name: quay.io/rh-ee-ijanssen/machine-config-operator@sha256:65d3a308767b1773b6e3ead2ec1bcae499dde6ef085753d7e20e685f78841079 - name: quay.io/rh-ee-ijanssen/machine-config-operator@sha256:fd3692eff21338e900a244dfe62152c959b84d73f2dd4503893de0f3fae61b0b
3. Wait for the PIS to finish trying to apply, this should only take a few seconds.
4. Look at one of the MCN resources associated with a node targeted in the PIS.
a. Get the MCNs.
oc get machineconfignode
b. Copy the `NAME` value for one of the MCNs that has the value `worker` for `POOLNAME`. This is necessary since the applied PIS targets the `worker` role.
c. Observe the message for `MachineConfigNodePinnedImageSetsDegraded` in the MCN conditions list.
oc describe machineconfignode/<mcn-name-from-step-b>
Actual results:
The condition for `MachineConfigNodePinnedImageSetsDegraded` is:
Last Transition Time: 2025-05-27T15:35:39Z
Message: One or more PinnedImageSet is experiencing an error. See PinnedImageSet list for more details
Reason: PrefetchFailed
Status: True
Type: PinnedImageSetsDegraded
Expected results:
The message for `MachineConfigNodePinnedImageSetsDegraded` should not have a typo, so it should be:
One or more PinnedImageSet is experiencing an error. See PinnedImageSet list for more details.
Additional info:
- The message being referred to in this bug is set here: https://github.com/openshift/machine-config-operator/blob/5feede61e20a283bbfbbddab8f1e5c57e7b6efda/pkg/daemon/pinned_image_set.go#L649
- The change needed is adding a period at the end of the error string.
- One or more PinnedImageSet is experiencing an error. See PinnedImageSet list for more details --> One or more PinnedImageSet is experiencing an error. See PinnedImageSet list for more details.
- blocks
-
OCPBUGS-57064 Fix typo in MCN's `MachineConfigNodePinnedImageSetsDegraded` message
-
- New
-
- is cloned by
-
OCPBUGS-57064 Fix typo in MCN's `MachineConfigNodePinnedImageSetsDegraded` message
-
- New
-
- links to