-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14
-
None
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
I try to update a pull-secret in a ROSA hosted OCP cluster. I follow https://access.redhat.com/documentation/en-us/openshift_container_platform/4.14/html/images/managing-images#images-update-global-pull-secret_using-image-pull-secrets and I also tried to Edit Secret in OpenShift Console, but the value stays the same. The documentation should be updated with steps that will also work on ROSA hosted OCP clusters.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Deterministic.
Steps to Reproduce:
1. oc get secret/pull-secret -n openshift-config --template='{{index .data ".dockerconfigjson" | base64decode}}' > /tmp/pull-secret 2. oc registry login --registry="<registry>" --auth-basic="<username>:<password>" --to=/tmp/pull-secret 3. oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=/tmp/pull-secret 4. oc get secret/pull-secret -n openshift-config --template='{{index .data ".dockerconfigjson" | base64decode}}' > /tmp/pull-secret-new 5. diff /tmp/pull-secret /tmp/pull-secret-new
Actual results:
The files are the same.
Expected results:
The second file should have that extra entry.
Additional info:
In fact, it seems like something is recreating the secret under my hands, even if I outright remove it: $ oc get -n openshift-config secret/pull-secret -o json | jq -r '.metadata.creationTimestamp' 2023-11-23T18:52:38Z $ oc delete -n openshift-config secret/pull-secret secret "pull-secret" deleted $ oc get -n openshift-config secret/pull-secret -o json | jq -r '.metadata.creationTimestamp' 2023-11-23T18:55:13Z