-
Bug
-
Resolution: Unresolved
-
Major
-
4.16
-
Important
-
None
-
OCPNODE Sprint 255 (Green), OCPNODE Sprint 256 (Green), OCPNODE Sprint 257 (Green), OCP Node Sprint 258 (Green), OCP Node Sprint 259 (Green)
-
5
-
Rejected
-
False
-
-
-
Bug Fix
-
In Progress
Description of problem:
Wen a pinnedimageset resource is created the images are pinned, but when we remove this pinnedimageset resource the images are not unpinned.
Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.16.0-0.nightly-2024-05-07-025557 True False 3h23m Cluster version is 4.16.0-0.nightly-2024-05-07-025557
How reproducible:
Always
Steps to Reproduce:
1. Create a pinnedimageset
oc create -f - << EOF
apiVersion: machineconfiguration.openshift.io/v1alpha1
kind: PinnedImageSet
metadata:
labels:
machineconfiguration.openshift.io/role: worker
name: tc-73623-worker-pinned-images
spec:
pinnedImages:
- name: "quay.io/openshifttest/busybox@sha256:0415f56ccc05526f2af5a7ae8654baec97d4a614f24736e8eef41a4591f08019"
- name: $(oc adm release info --image-for rhel-coreos)
- name: $(oc adm release info --image-for rhel-coreos-extensions)
EOF
2.Wait until images are pinned
3. Remove the pinnedimageset resource
oc delete pinnedimageset tc-73623-worker-pinned-images
Actual results:
After removing the pinnedimageset resource the images are still pinned in the worker nodes.
Expected results:
Ater removing the pinnedimageset resource the images should not be pinned in the worker nodes.
Additional info:
Manually restarting crio service will unpin the images.
- blocks
-
OCPSTRAT-763 [TechPreview]Disconnected Cluster Update and Boot without local image registry - phase 1
-
- In Progress
-
- relates to
-
MCO-838 [TechPreview] Pin and pre-load images
-
- Closed
-
- links to
