Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1883808

Summary: Clearer dhclient timeout message
Product: OpenShift Container Platform Reporter: Yuval Goldberg <ygoldber>
Component: assisted-installerAssignee: Ori Amizur <oamizur>
assisted-installer sub component: discovery-agent QA Contact: Yuri Obshansky <yobshans>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: high CC: aos-bugs, vlaad
Version: 4.6   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: assisted-installer-prod
Fixed In Version: OCP-Metal-v1.0.10.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-25 21:41:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yuval Goldberg 2020-09-30 09:45:46 UTC
Description of problem:
The agent is called wrapped by a timeout utility.
If it fails it would return a "dhclient existed with non-zero exit code 124" error message.


Steps to Reproduce:
1. Some DHCP server failure

Actual results:
dhclient existed with non-zero exit code 124: Internet Systems Consortium DHCP Client 4.3.6\nCopyright 2004-2017 Internet Systems Consortium.\nAll rights reserved.\nFor info, please visit https://www.isc.org/software/dhcp/\n\nListening on LPF/ingress/00:1a:4a:c4:dd:ec\nSending on   LPF/ingress/00:1a:4a:c4:dd:ec\nSending on   Socket/fallback\nNot enough data in /etc/machine-id\nCreated duid \"\\000\\001\\000\\001'\\0067A\\000\\032J\\304\\335\\354\".\nDHCPDISCOVER on ingress to 255.255.255.255 port 67 interval 8 (xid=0x477a714e)\nDHCPREQUEST on ingress to 255.255.255.255 port 67 (xid=0x477a714e)\nDHCPOFFER from 10.10.10.5\n

Expected results:
dhclient failed on timeout of %d seconds


Additional info:
- Should fix "existed" to "exited".
- Extend timeout for more than 5 seconds.

Comment 3 Ronnie Lazar 2020-11-04 16:40:07 UTC
just a test

Comment 4 nshidlin 2020-11-16 17:17:06 UTC
Verified on OCP-Metal-v1.0.11.1

Error message:

Nov 16 16:58:30 master-0-1 dhcp_lease_allo[4880]: time="16-11-2020 16:58:30" level=error msg="Failed to lease a vip" file="dhcp_lease_allocate.go:98" error="dhclient was timed out after 28 seconds" ip= mac="00:1a:4a:f0:44:2b" masterDevice=ens3 name=api