Bug 1915997 - [4.6.z] RHCOS 4.6 ostree removed dhclient
Summary: [4.6.z] RHCOS 4.6 ostree removed dhclient
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: ---
: 4.6.z
Assignee: Christian Glombek
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On: 1908462
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-13 22:15 UTC by Micah Abbott
Modified: 2021-03-02 04:48 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The dhclient binary was removed from RHCOS when the switch to using NetworkManager in the initramfs was made. Consequence: Users that had configured RHCOS to use dhclient for DHCP operations were left with systems that were unable to properly acquire a DHCP address. Fix: Include the dhclient binary in RHCOS. Result: RHCOS systems are able to perform DHCP operations using dhclient successfully.
Clone Of: 1908462
Environment:
Last Closed: 2021-03-02 04:48:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:0634 0 None None None 2021-03-02 04:48:28 UTC

Comment 1 Micah Abbott 2021-01-15 20:33:27 UTC
Higher priority work has prevented from this issue being worked on; adding UpcomingSprint keyword

Comment 4 Micah Abbott 2021-02-17 16:29:40 UTC
The changes were included in RHCOS 46.82.202102171440.0; they should make their way into the OCP nightly release payloads soon.

Comment 7 Michael Nguyen 2021-02-22 14:35:30 UTC
Verified on 4.6.0-0.nightly-2021-02-20-05545.  dhclient binary exists on RHCOS now.


$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.6.0-0.nightly-2021-02-20-055459   True        False         10m     Cluster version is 4.6.0-0.nightly-2021-02-20-055459
$ oc get nodes
NAME                                         STATUS   ROLES    AGE   VERSION
ip-10-0-131-211.us-west-2.compute.internal   Ready    worker   22m   v1.19.0+8d12420
ip-10-0-141-183.us-west-2.compute.internal   Ready    master   31m   v1.19.0+8d12420
ip-10-0-166-230.us-west-2.compute.internal   Ready    worker   25m   v1.19.0+8d12420
ip-10-0-168-134.us-west-2.compute.internal   Ready    master   30m   v1.19.0+8d12420
ip-10-0-193-158.us-west-2.compute.internal   Ready    worker   22m   v1.19.0+8d12420
ip-10-0-210-250.us-west-2.compute.internal   Ready    master   31m   v1.19.0+8d12420
$ oc debug node/ip-10-0-131-211.us-west-2.compute.internal 
Starting pod/ip-10-0-131-211us-west-2computeinternal-debug ...
To use host binaries, run `chroot /host`
If you don't see a command prompt, try pressing enter.
sh-4.2# chroot /host
sh-4.4# rpm -q dhclient
package dhclient is not installed
sh-4.4# rpm-ostree status
State: idle
Deployments:
* pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:11e2d302afbdaca8b0be95cf2e0a56c93491597eb65f21acba2e5208674307bb
              CustomOrigin: Managed by machine-config-operator
                   Version: 46.82.202102190441-0 (2021-02-19T04:45:17Z)

  ostree://cb0327325553e6922ff25822ea7eb1a2ec213e70c7cf6880965e7e2bb5ee7dea
                   Version: 46.82.202011260640-0 (2020-11-26T06:44:15Z)
sh-4.4# which dhclient
/usr/sbin/dhclient
sh-4.4# ls /etc/dhcp/
dhclient.d
sh-4.4# ls /etc/NetworkManager/dispatcher.d/
04-iscsi   20-coreos-chrony-dhcp			   90-long-hostname  pre-down.d
20-chrony  90-console-login-helper-messages-gensnippet_if  no-wait.d	     pre-up.d
sh-4.4# ls /usr/lib64/pm-utils/sleep.d/
sh-4.4# ls /usr/sbin/ | grep dhclient
dhclient
dhclient-script

sh-4.4# exit
exit
sh-4.2# exit
exit

Removing debug pod ...

Comment 9 errata-xmlrpc 2021-03-02 04:48:10 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 (OpenShift Container Platform 4.6.19 bug fix 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/RHBA-2021:0634


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