Bug 2044808 - machine-config-daemon-pull.service: use `cp` instead of `cat` when extracting MCD in OKD
Summary: machine-config-daemon-pull.service: use `cp` instead of `cat` when extracting...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: MCO Team
QA Contact: Rio Liu
Depends On:
Blocks: 2096792
TreeView+ depends on / blocked
Reported: 2022-01-25 09:06 UTC by Vadim Rutkovsky
Modified: 2022-06-14 09:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:42:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2925 0 None Merged Bug 2044808: mcd pull service: use `cp` instead of `cat` to copy MCD on host 2022-01-31 22:17:59 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:42:39 UTC

Description Vadim Rutkovsky 2022-01-25 09:06:43 UTC
OKD OS doesn't come with MCD included, so it needs to be extracted from MCO image early in the boot. This is implemented via running `cat` command in the container to ensure that the binary is copied atomically.

Since F35 bump `podman run ... --entrypoint=cat ...` no longer exists correctly, so we have to fall back to `podman run ... -v /run/bin:/host/run/bin ... --entrypoint=cp ...` to copy the binary from container. This is not an atomic operation, but at least this method is being regularly tested upstream.

Comment 2 Sergio 2022-01-28 17:06:45 UTC
This BZ was breaking only OKD nightlies aws tests.

OCP is not affected by this BZ. Moved to VERIFIED.

Comment 5 errata-xmlrpc 2022-03-10 16:42:23 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.10.3 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.


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