m (→Dependencies) |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=WIP: Deprecate dhclient | =WIP: Deprecate dhclient <!-- The name of your change proposal -->= | ||
== Summary == | == Summary == | ||
| Line 72: | Line 72: | ||
https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | ||
--> | --> | ||
Modern implementation fixes few bugs which are difficult to fix in | Modern implementation fixes a few bugs which are difficult to fix in '''dhcp-client''' like monotonic time support (bz#876791) and brings support for mixed ipv4 + ipv6 environment. Besides it fits more accurately into modern stack of networking management in Fedora (ip addresses lifetime, etc). | ||
== Scope == | == Scope == | ||
| Line 78: | Line 78: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: Anaconda and Dracut maintainers to drop rhard requirement of dhcp-client, | * Other developers: Anaconda and Dracut maintainers to drop rhard requirement of dhcp-client, RCM to drop dhcp-client RPM from ISO, maintainers of packages depending on dhcp-client rpm | ||
RCM to drop dhcp-client RPM from ISO | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 113: | Line 113: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
Check | Check: | ||
1. '''dhcp-client''' rpm does not exist on installation ISO and the absence of the RPM does not have an impact on installation including network installation. | |||
2. There is no package depending on '''dhcp-client''' rpm. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 129: | Line 133: | ||
--> | --> | ||
Regular users should not | Regular users should not notice any change. Advanced users and third-party applications may call '''dhclient''' binary directly thus they will be affected and should start using '''dhcpcd''', or install '''dhcp-client''' from the EPEL repo (TBD/TODO), and/or adjust the dependencies list accordingly. | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
dracut-network-0: | cloud-init-0:23.2.1-1.fc39.noarch [https://bugzilla.redhat.com/show_bug.cgi?id=2247055 BZ#2247055] | ||
dracut-network-0:059-12.fc39.x86_64 [https://bugzilla.redhat.com/show_bug.cgi?id=2247056 BZ#2247056] | |||
google-compute-engine-guest-configs-0:20230801.00-1.fc39.noarch [https://bugzilla.redhat.com/show_bug.cgi?id=2251746 BZ#2251746] | |||
libguestfs-1:1.51.6-2.fc39.src [https://bugzilla.redhat.com/show_bug.cgi?id=2247057 BZ#2247057] | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 11:46, 27 November 2023
WIP: Deprecate dhclient
Summary
This is the next step in the deprecation of ISC DHCP in Fedora due to deprecation by the vendor (ISC).
Currently, dhclient (dhcp-client) is the main implementation and while some projects switched to dhcp library provided by NetworkManager (TBD links) and some work was done in Fedora to switch to dhcp library ( BZ#1204226) dhclient binary is pulled into ISO by anaconda and dracut still.
Owner
- Name: Martin Osvald
- Email: mosvald at redhat dot com
- Release notes owner:
Current status
- Targeted release: Fedora 40
- Last updated: 2023-11-27
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
dhcp-client no longer receives any development by the vendor (ISC) and it is deprecated. While dhcp-server is deprecated by ISC Kea, dhcp-client doesn't have an alternative developed by ISC and the proposal is to use DHCP implementation provided by NetworkManager (preferable) and if not possible use a client provided by dhcpcd package.
Benefit to Fedora
Modern implementation fixes a few bugs which are difficult to fix in dhcp-client like monotonic time support (bz#876791) and brings support for mixed ipv4 + ipv6 environment. Besides it fits more accurately into modern stack of networking management in Fedora (ip addresses lifetime, etc).
Scope
- Proposal owners:
- Other developers: Anaconda and Dracut maintainers to drop rhard requirement of dhcp-client, RCM to drop dhcp-client RPM from ISO, maintainers of packages depending on dhcp-client rpm
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
NetworkManager's dhcp implementation is NOT drop-in replacement of dhclient. While it supports (almost) all RFCs it can behave in different way in some cases ((IB support, client identifier, direct calls of dhclient binary etc links: TBD ). The goal is to find this cases and fix them.
How To Test
Check:
1. dhcp-client rpm does not exist on installation ISO and the absence of the RPM does not have an impact on installation including network installation.
2. There is no package depending on dhcp-client rpm.
User Experience
Regular users should not notice any change. Advanced users and third-party applications may call dhclient binary directly thus they will be affected and should start using dhcpcd, or install dhcp-client from the EPEL repo (TBD/TODO), and/or adjust the dependencies list accordingly.
Dependencies
cloud-init-0:23.2.1-1.fc39.noarch BZ#2247055
dracut-network-0:059-12.fc39.x86_64 BZ#2247056
google-compute-engine-guest-configs-0:20230801.00-1.fc39.noarch BZ#2251746
libguestfs-1:1.51.6-2.fc39.src BZ#2247057
Contingency Plan
- Contingency mechanism: Pull dhclient into iso and allow anaconda/dracut use it as before
- Contingency deadline: Beta freeze (not a System Wide Change)
- Blocks release? Yes
- Blocks product? product
Documentation
N/A (not a System Wide Change)