Description of problem: When use `oc adm release new` will print the choose image massage repetitively Version-Release number of selected component (if applicable): oc version --client Client Version: 4.11.0-0.nightly-2022-06-23-092832 Kustomize Version: v4.5.4 How reproducible: always Steps to Reproduce: 1. `oc adm release new --from-release=quay.io/openshift-release-dev/ocp-release@sha256:539fc5f98ea138395595fc72e9764aff3ad370803745b4d22db7df8e21d530db --to-image=localhost:5000/newtestamd --to-image-base file://openshift/release:4.10.18-x86_64-cluster-version-operator --insecure` Actual results: 1. oc adm release new --from-release=quay.io/openshift-release-dev/ocp-release@sha256:539fc5f98ea138395595fc72e9764aff3ad370803745b4d22db7df8e21d530db --to-image=localhost:5000/newtestamd --to-image-base file://openshift/release:4.10.18-x86_64-cluster-version-operator --insecure Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations. W0624 11:13:41.170805 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. info: Found 167 images in release Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations. W0624 11:13:45.149852 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:45.152977 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:45.161319 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:45.178559 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:47.508391 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:47.508396 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:47.538407 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:47.545266 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. info: Loading sha256:4504eff79e6436031441af73aa39ad165468cd59363050c11b07dd0beb7babf1 apiserver-network-proxy info: Loading sha256:4444fe810003c48fd0f3144ee499de72d24bcb9ba354804eab3d0c481a0e64e4 aws-cluster-api-controllers W0624 11:13:48.742758 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:48.751573 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. info: Loading sha256:05c6008cddb9236e9061a6145470f2290a01b2ea213abf308039b3a52d5aff83 aws-machine-controllers W0624 11:13:49.979726 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:51.211932 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:52.425342 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:13:53.736425 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. info: Loading sha256:72b2a0348f5bc94cab6f95497badbf5852451e562d77e39d6a3efdb5f176f0e5 azure-cluster-api-controllers W0624 11:14:02.333684 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:14:03.519841 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:14:03.819899 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:14:04.786263 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. W0624 11:14:05.105372 109310 manifest.go:442] Chose linux/amd64 manifest from the manifest list. .... Expected results: 1. No need to print the repetitive message. Additional info:
can't see the dump info now: ./oc version --client -o yaml clientVersion: buildDate: "2022-07-05T18:53:51Z" compiler: gc gitCommit: 6e19e6e7048aacab9190164afc3ae8d0b4adca10 gitTreeState: clean gitVersion: 4.12.0-202207051826.p0.g6e19e6e.assembly.stream-6e19e6e goVersion: go1.18 major: "" minor: "" platform: linux/amd64 kustomizeVersion: v4.5.4 releaseClientVersion: 4.12.0-0.nightly-2022-07-05-225149 [root@localhost ~]# ./oc adm release new --keep-manifest-list --from-release=quay.io/openshift-release-dev/ocp-release@sha256:03a4bb243ba2c1627e8e1a502cc4acdee24ddfe25be6884d83f07965de89e301 --to-image=localhost:5000/newtest66 --insecure Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations. info: Found 171 images in release Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations. info: Loading sha256:e7bbec234db1848a78934656828f4404bc774b75db4fd69937dbbf1f91351cd8 agent-installer-orchestrator info: Loading sha256:e426e9062344885b3fd34d8af6c0e18653648faf22f5fe3e3c6c9c03cbfef077 agent-installer-node-agent info: Loading sha256:47ac1f47737e3c2df1e4651c7b1d2b3256de5529e3027206dacf348d13664d2a agent-installer-csr-approver info: Loading sha256:27917beada48515273d901c0708f19a7f8ea4c653bf716ae84b6b9881dd69066 agent-installer-api-server info: Loading sha256:78af37cc332ced08af7364ae8c164e65028771471047928a9ec431c18a49e683 apiserver-network-proxy info: Loading sha256:4457d19a10c37ccc4d575a76804c367442ad6ba3c3009044fa6953b46ebf31c3 aws-cluster-api-controllers info: Loading sha256:25bfa56dc4e672116a7ea233b3c2b11575aadb77c141ff7556f7b34921e4fd34 aws-machine-controllers info: Loading sha256:df528c3f798fa35771a3d55f165c07bac6250debc5f368462f5101d6939f6b67 azure-cluster-api-controllers info: Loading sha256:cf99bc7ed24037697c9a6d7e68b9d2ffb5dbaa09d769cc41cc3d0d9f6aa9e112 azure-machine-controllers info: Loading sha256:a328c718da230e5cd8420515350a0662d3f066f7f626b10130c4120252dc9d79 baremetal-operator info: Loading sha256:79e95e272363e7b1c33ebfed14f2da9527af2eaf096c2f1516a361b8638ed143 cloud-credential-operator info: Loading sha256:74a1b9848b0155e0331cda46be47f058517d9d9eeb284e534995f24c17394130 cluster-authentication-operator info: Loading sha256:6282eca76ceb9fa94edd202611b740268d376184327de98221a2c0da9a393dc4 cluster-autoscaler-operator info: Loading sha256:501f7be1b035a4fb1b19b4f8e9e55d5d0426b3e2994404b31dd4e7c5bc5cca09 cluster-baremetal-operator info: Loading sha256:a76052ecf4902b18e68437d52a45a9002328dc011f80ec22a2ac021702054f19 cluster-bootstrap info: Loading sha256:c8111b4de62339046b2705a41dea0af3fff06e91f62093a069641de008a08130 cluster-capi-controllers info: Loading sha256:57c3702aa1129b8468d92c8b5b0f8a049c6776791a1bc4f5410fe249628bbf18 cluster-capi-operator info: Loading sha256:b71d279cca4774a3369e917578230ee01cedd1c33b3747dbd1c89d55fab2e8e3 cluster-cloud-controller-manager-operator info: Loading sha256:80350202de7c6e5f9515a19467ac92d2cddfadb95a53bbf7e0aa7f95f85503b8 cluster-config-operator info: Loading sha256:6efaa702c65d57a91f992223bd75b249c24749596651ba27d3f7e1ff3dd89e4d cluster-csi-snapshot-controller-operator info: Loading sha256:eee4221e68e5dbf7cad7b3a20d5638eae5e1a72bb3a200848cf482666bb257ee cluster-dns-operator info: Loading sha256:732a7e775fe34feac5e4874d1e20973bbd64966e90b5b520658265f588c3de56 cluster-etcd-operator info: Loading sha256:1c7a2d71217f6ddd33b60efee624d9f57c8ff06bb69c5671e865cce31b55370f cluster-image-registry-operator info: Loading sha256:bfa41c63d991c40c42ff6e59e5a8985e5fbc43ff4ba817c8bdecaaa574b518af cluster-kube-apiserver-operator info: Loading sha256:b38b2d382bbc1c9b9d511de5464f11c5da4adae4c85923886ea7c32f2c7f2c49 cluster-ingress-operator info: Loading sha256:826067995900ba018e4e65c8da578c5ceb2b245f72b4aec9eb7ffe169a2d7406 cluster-kube-cluster-api-operator info: Loading sha256:c3a6bd9e2b7ed3aa9d4fa687c6fc5bc2f848c28bd762365e18f4d995753f9387 cluster-kube-controller-manager-operator info: Loading sha256:0633ff2c9f58ac00802a66ac593ae70d0347486f7caf1eef335900343559ead0 cluster-kube-scheduler-operator info: Loading sha256:dca79c0b9ea20bab1e55bd7dfafc10425c18481849aa81f22df67c2f2fc753ba cluster-kube-storage-version-migrator-operator info: Loading sha256:e0e181bff7ecf655278b5d23c17c2c2ef20fe9927dae538def1d234fc56f3faa cluster-machine-approver info: Loading sha256:2f1c926783c9d3a93a8d779928596cedcf75a2289c19b7eb4150803ef98c57f1 cluster-monitoring-operator info: Loading sha256:5417daaf40a4eee33c9a01cc698e52052dc005ff957da13f8525ae9a695c4515 cluster-network-operator info: Loading sha256:163f2de4a2cabde49739ca05df0280891e598397e34f9c3f765ff2b1bf42857f cluster-node-tuning-operator info: Loading sha256:343f6594dc5c1ee6199c7c86e3ba18fc93b351d586ca51b6f358031b88d31d49 cluster-openshift-apiserver-operator info: Loading sha256:b929bd2a4d441906557c351b5242f6e81e7115dd9f3adde6060634dec9a2302e cluster-openshift-controller-manager-operator info: Loading sha256:483936fcfb626eda53b7046b481932f6cfdd43530dfbe8f841f0c99dbab97cea cluster-samples-operator info: Loading sha256:4d2ed2b1fbec7f2e623d10bb30192fdd9c87dca2e87eafaef61356809cc82f6e cluster-storage-operator info: Loading sha256:1821c5f2a2929d9006e46a341d8b215782973aecade86ce8658a3563336c88c2 cluster-update-keys info: Loading sha256:0ae34934e3ae5ebb2afcc678b2022e09665b7afd41caceb845f8cf4c251e2462 console-operator info: Loading sha256:c024193b758e33f046cd7692dd2a8a712dc4fdc4244bf501c4a6e741212cb0d0 driver-toolkit info: Loading sha256:7563366926280c74fc01b43745a47fcc1e6dec658b677f220535d76755ef1d8e gcp-cluster-api-controllers info: Loading sha256:0300680605a063af34281a2b1af42e073f5c0c5fe79819c80d01332994a4a0c7 hypershift info: Loading sha256:23c0bcce153596ea80e3a3946f7c4694364353fe8e4af2e326c7d68e7f04a2e5 insights-operator info: Loading sha256:91bed00fb484e011c1220fa96330f1e4d23d96bb92b7e00582436d23419e50f6 installer info: Loading sha256:dca4b9c490d7a2f0c4121b744d2078ebdf3986d889fa7728fc9340d264543d56 installer-artifacts info: Loading sha256:0245df4f96300f49f1d71da8a3e647586678d43b91d03508d7f7a2f9033e111f machine-api-operator info: Loading sha256:39642af2c452da18bb0a8c9e15cafe02eec84469ab54e6c30264227e70eb640b machine-config-operator info: Loading sha256:1c3e1edbf78e8332a921df58fc22b62adc83fabfc3883063c05b38c733ae5d3e machine-os-images info: Loading sha256:504f05ca7fdd79e9b51fd1aeb8efe49bef7ef323ff9f57e004b53f4d8784fc65 oc-mirror info: Loading sha256:08d9c92fae8270ae24e7b2d398bc5c7c896fdadaa50558ea8754ccf9792b7998 operator-lifecycle-manager info: Loading sha256:dd68f44fff21fc26e35253388ee2a0cfa08b5ada5054d52f8dbd6c986ce5778f operator-marketplace info: Loading sha256:1ae552d73aa944a61b65f51f79d8329331f55155831d74a61131dfbf0cd5d39f service-ca-operator info: Loading sha256:f066f17258f6043a4648cca39ce4a32557063473a1735cff193c0399629bfc51 vsphere-cluster-api-controllers info: Loading sha256:de728ef5cb5b2d8006414dacdb767816420a8db05db17ca3d9cd11df61a56415 vsphere-problem-detector Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations. info: Pushed to localhost:5000/newtest66 sha256:62578915e0e6713de4f59357b07d982fb5e034ae31f87944ae07b2c07faf87fd 4.11.0-0.nightly-multi-2022-07-04-162250 2022-07-06T01:48:23Z
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:7399