Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1964900 +++
Description of problem:
If not install dhcp-client, cloud-init fails to provision VM on Azure. Suggest to either add dhcp-client to the cloud-init dependencies, or fix cloud-init to not rely on dhclient.
Related RHEL-8 BZ#1641190
Version-Release number of selected components (if applicable):
RHEL Version:
RHEL-8.5.0-20210626.n.0
cloud-init-20.3-10.el8_4.3.noarch
How reproducible:
100%
Steps to Reproduce:
1. Start a VM on Azure without dhcp-client installed
2. Check cloud-init.log
Actual results:
Provisioning failed.
2021-05-26 07:34:13,715 - dhcp.py[DEBUG]: Skip dhclient configuration: No dhclient command found.
2021-05-26 07:34:13,715 - handlers.py[DEBUG]: finish: azure-ds/obtain-dhcp-lease: FAIL: obtain dhcp lease
2021-05-26 07:34:13,715 - azure.py[WARNING]: exception while getting metadata:
2021-05-26 07:34:13,725 - handlers.py[DEBUG]: finish: azure-ds/get_metadata_from_imds: FAIL: get_metadata_from_imds
2021-05-26 07:34:13,725 - handlers.py[DEBUG]: finish: azure-ds/crawl_metadata: FAIL: crawl_metadata
2021-05-26 07:34:13,725 - util.py[DEBUG]: Crawl of metadata service took 0.273 seconds
2021-05-26 07:34:13,725 - azure.py[ERROR]: Could not crawl Azure metadata:
Expected results:
Provision successfully.
Additional info:
N/A
Hi Eduardo,
Now this issue (and BZ#1964900) may impact the image-builder project. Could you please help to check if we can add dhcp-client as a dependency of cloud-init? Thanks!
Hello Eduardo,
is there a plan to add the dhcp-client dependency to cloud-init? We (the Image Builder team) think that this is the best option. If this is a problem for you, we need to know it sooner rather than later so we can change the image definition for Azure images in 8.5.
Thanks,
Ondřej
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 (cloud-init 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/RHEA-2021:4294