dhcp-agent uses an interface which is down

[Magosányi Árpád]

I am using folsom from the ubuntu cloud archive.
Quantum started dnsmasq correctly, but on an interface which is down.
Modifying init_l3 in agent/linux/interface.py with adding a device.link.set_up() call remediated the problem.
I don't know who would be responsible for upping the interface in the first place though.

Here is the relevant snippet from my current code:

    def init_l3(self, device_name, ip_cidrs, namespace=None):
        """Set the L3 settings for the interface using data from the port.
           ip_cidrs: list of 'X.X.X.X/YY' strings
        """
        LOG.debug("init_l3")
        device = ip_lib.IPDevice(device_name, self.conf.root_helper,
                                 namespace=namespace)
        LOG.debug("link setup")
        device.link.set_up()

[Mark McClain (markmcclain)]

When did bug occur? Was it after a system reboot?

[dan wendlandt (danwent)]

assigning to garyk for triage, as this is likely related to some restart issues he's seen.

[Gary Kotton (garyk)]

Hi,
Can you please check that the quantum-ovs-cleanup is called when the host stars. Please make sure that this is called before the l3 and dhcp agents.
Thanks
Gary

[Gary Kotton (garyk)]

When the OVS is used and a tap device is created a reboot causes the device to be created and it is down. The quantum-ovs-cleanup utility make sure that device is purged from the ovs and then dhcp and l3 agents can do their magic :)

[Salvatore Orlando (salvatore-orlando)]

I am setting this bug as won't fix as we did not hear anything about for over a year.