-
Bug
-
Resolution: Done-Errata
-
Major
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
2
-
Important
-
None
-
None
-
None
-
MCO Sprint 269
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the PinnedImageSets reference in the MCN’s status, the LastFailedGeneration value defaults to 0. This value should not be less than 1.
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Always.
Steps to Reproduce:
1. Apply a valid PIS.
apiVersion: machineconfiguration.openshift.io/v1alpha1 kind: PinnedImageSet metadata: name: test-pinned labels: machineconfiguration.openshift.io/role: "worker" spec: pinnedImages: - name: quay.io/openshift-release-dev/ocp-release@sha256:513cf1028aa1a021fa73d0601427a0fbcf6d212b88aaf9d76d4e4841a061e44e - name: quay.io/openshift-release-dev/ocp-release@sha256:61eae2d261e54d1b8a0e05f6b5326228b00468364563745eed88460af04f909b
2. Wait for the PIS application to complete and view the MCN for a targeted node.
Status: … Pinned Image Sets: Current Generation: 1 Desired Generation: 1 Last Failed Generation: 0 Name: test-pinned
Actual results:
The PinnedImageSets reference contains a value of 0 for LastFailedGeneration.
Expected results:
The generation values cannot be 0. They should start at 1.
Additional info:
- Related API comment highlighting issue: https://github.com/openshift/api/pull/2255#discussion_r2037406327
- This bug can be considered resolved when no generation values referenced in the MCN API type are populated with a value of 0.
- blocks
-
MCO-1519 [API 4/6] Adapt MCO & origin code to use MCN’s V1 API
-
- Closed
-
- links to
-
RHEA-2024:11038
OpenShift Container Platform 4.19.z bug fix update
