-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
2. What is the nature and description of the request?
Customer have four interfaces on BM hosts, DHCP enabled environment, on interface1 and interface2, customer wants to create bond and wants to disable interface3 and interface4. However this seem to be not possible as we can get an IP Assigned from DHCP.
Since interface3 and interface4 are not being used, as per customer security standards they would like these interface3 and interface4 to be down
Based on our documentation,
"Always set the state parameter to up when you set both the ipv4.enabled and the ipv6.enabled parameter to false to disable an interface. If you set state: down with this configuration, the interface receives a DHCP IP address because of automatic DHCP assignment."
3. Why does the customer need this? (List the business requirements here)
Customer have four interfaces on BM hosts, DHCP enabled environment, on interface1 and interface2, customer wants to create bond and wants to disable interface3 and interface4. However this seem to be not possible as we can get an IP Assigned from DHCP.
Since interface3 and interface4 are not being used, as per customer security standards they would like these interface3 and interface4 to be down
4. List any affected packages or components.
- causes
-
RHEL-102340 nmstate does not disable interface when state:down and ipv4:false
-
- Release Pending
-