Description of problem:
Setting a port of TYPE=OVSIntPort to use DHCP is ignored i.e. dhclient is not run for that interface
ifup-ovs script appears to only handle DHCP on TYPE=OVSBridge . Why?
Steps to Reproduce:
physical interface is 'p1p1' with config:
bridge interface is 'ovsbr0' with config:
Internet ovs port is 'mgmt0' with config:
I run 'systemctl start network.service' which completes without error, but interface mgmt0 never receives an IP address. Process listing shows no 'dhclient' process running.
dhclient should be started and 'mgmt0' should receive an IP
If I run 'dhclient mgmt0' manually, then 'mgmt0' receives an IP address.
Created attachment 829364 [details]
ifup-ovs with dhcp support for Internal Ports
It's bug. I don't see a reason to not support it.
Could you backup the original file at
and replace with the attached one for testing purposes?
I've tested the attached ifup-ovs script and it works for me. Thanks!
Created attachment 849626 [details]
Patch enabling DHCP support for internal ports
I've found some issues while reviewing again the previous file.
I came up another better patch which I will post upstream in a few minutes.
Upstream post: http://openvswitch.org/pipermail/dev/2014-January/035928.html
Patch accepted upstream.
openvswitch-2.0.0-4.fc20 has been submitted as an update for Fedora 20.
openvswitch-2.0.0-4.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openvswitch-2.0.0-4.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
openvswitch-2.0.0-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
openvswitch-2.0.0-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.