-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.18
Description of problem:
The release signature configmap file is invalid with no name defined
Version-Release number of selected component (if applicable):
oc-mirror version WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version. Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.18.0-202410011141.p0.g227a9c4.assembly.stream.el9-227a9c4", GitCommit:"227a9c499b6fd94e189a71776c83057149ee06c2", GitTreeState:"clean", BuildDate:"2024-10-01T20:07:43Z", GoVersion:"go1.22.5 (Red Hat 1.22.5-1.module+el8.10.0+22070+9237f38b) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}
How reproducible:
100%
Steps to Reproduce:
1) with isc : cat /test/yinzhou/config.yaml kind: ImageSetConfiguration apiVersion: mirror.openshift.io/v2alpha1 mirror: platform: channels: - name: stable-4.16 2) do mirror2disk + disk2mirror 3) use the signature configmap to create resource
Actual results:
3) failed to create resource with error: oc create -f signature-configmap.json The ConfigMap "" is invalid: metadata.name: Required value: name or generateName is required oc create -f signature-configmap.yaml The ConfigMap "" is invalid: metadata.name: Required value: name or generateName is required
Expected results:
No error
- blocks
-
OCPBUGS-46055 The release signature configmap file is invalid with no name
- POST
- is cloned by
-
OCPBUGS-46055 The release signature configmap file is invalid with no name
- POST
- is duplicated by
-
OCPBUGS-43829 signature config map isnt usable on the cluster
- Closed
- relates to
-
CLID-150 As a customer I want to be sure the release signatures are made available
- Testing
- links to