-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
To Reproduce Steps to reproduce the behavior:
- Deploy rhel-ai-nvidia-1.4.4-1744921925-x86_64-kvm.qcow2 from stage
- sudo bootc status
- Observe that the deployed system is based on production bootc container
Expected behavior
- Deliverable is based on a stage bootc container
Screenshots
$ sudo bootc status apiVersion: org.containers.bootc/v1alpha1 kind: BootcHost metadata: name: host spec: image: image: registry.redhat.io/rhelai1/bootc-nvidia-rhel9:1.4 transport: registry bootOrder: default status: staged: null booted: image: image: image: registry.redhat.io/rhelai1/bootc-nvidia-rhel9:1.4 transport: registry version: 9.20250220.0 timestamp: null imageDigest: sha256:2d5e4d0ca9f95a5edcef0a46d795db5042c9923091fae79c3f084c00bce164ad cachedUpdate: null incompatible: false pinned: false store: ostreeContainer ostree: checksum: 877ea654799cbfe2b173b482e6a54603e6a4490e9c46236eb104c29b14a9ebc3 deploySerial: 0 rollback: null rollbackQueued: false type: bootcHost
Device Info (please complete the following information):
Bug impact
- Incorrect component versions used, unavailable bootc upgrade path to newer containers (having to resort to bootc switch), maybe other
Known workaround
- N/A
Additional context
- <your text here>
- …
