Bug 1900935 - `oc adm release mirror` panic panic: runtime error
Summary: `oc adm release mirror` panic panic: runtime error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-24 03:17 UTC by zhou ying
Modified: 2021-02-24 15:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:35:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:35:55 UTC

Description zhou ying 2020-11-24 03:17:55 UTC
Description of problem:
`oc adm release mirror` panic with error:
oc adm release mirror -a /home/slave2/mirror_pullsecret_config.json  --from=quay.io/openshift-release-dev/ocp-release:4.2.36-x86_64 --to=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release --to-release-image=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release:4.2.36-x86_64 | tee ~/release_image_mirror.out && exit ${PIPESTATUS[0]}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x55f1a0]

Version-Release number of selected component (if applicable):
4.2.36-x86_64 

How reproducible:
sometimes

Steps to Reproduce:
1.`oc adm release mirror -a /home/slave2/mirror_pullsecret_config.json  --from=quay.io/openshift-release-dev/ocp-release:4.2.36-x86_64 --to=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release --to-release-image=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release:4.2.36-x86_64 | tee ~/release_image_mirror.out && exit ${PIPESTATUS[0]}`
2.
3.

Actual results:
command panic 

Expected results:
no error.

Additional info:

Comment 1 zhou ying 2020-11-24 03:32:51 UTC
Command: oc adm release mirror -a /home/slave2/mirror_pullsecret_config.json  --from=quay.io/openshift-release-dev/ocp-release:4.2.36-x86_64 --to=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release --to-release-image=vmc.mirror-registry.qe.devcluster.openshift.com:5000/openshift-release-dev/ocp-release:4.2.36-x86_64 | tee ~/release_image_mirror.out && exit ${PIPESTATUS[0]}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x55f1a0]

goroutine 41 [running]:
bufio.(*Reader).fill(0xc000e8d080)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/bufio/bufio.go:100 +0xe0
bufio.(*Reader).WriteTo(0xc000e8d080, 0x2e7bc80, 0xc0000da790, 0x7f40aeb29a20, 0xc000e8d080, 0x2ee6801)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/bufio/bufio.go:511 +0x106
io.copyBuffer(0x2e7bc80, 0xc0000da790, 0x2e76440, 0xc000e8d080, 0x0, 0x0, 0x0, 0xc0008b9c00, 0xc0007107a0, 0x50e5d1)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/io/io.go:384 +0x34e
io.Copy(...)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/io/io.go:364
os/exec.(*Cmd).stdin.func1(0x0, 0x2ac17b8)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/os/exec/exec.go:243 +0x67
os/exec.(*Cmd).Start.func1(0xc0005bec60, 0xc0003be460)
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/os/exec/exec.go:409 +0x27
created by os/exec.(*Cmd).Start
	/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/os/exec/exec.go:408 +0x58f

Comment 2 Maciej Szulik 2020-11-24 10:56:55 UTC
Verified that with latest available oc and this is working as expected, moving for verification.

Comment 7 errata-xmlrpc 2021-02-24 15:35:25 UTC
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.7.0 security, bug fix, and enhancement 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-2020:5633


Note You need to log in before you can comment on or make changes to this bug.