Comment 7 for bug 1378066

Reviewed: https://review.openstack.org/159338
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e99f6e00cfd397bb74d44c9462dfcfa545dbed8c
Submitter: Jenkins
Branch: master

commit e99f6e00cfd397bb74d44c9462dfcfa545dbed8c
Author: lzklibj <email address hidden>
Date: Wed Feb 25 21:19:07 2015 -0800

    fix check_ports_exist_on_l3agent in no subnet case

    If no subnets attached to the given router, this check
    should return False.

    Currently, if no subnets attached to given router, the
    following process in this method will fetch all ports
    to continue its checking, consider those ports are not
    related to the given router, the following checking
    should be invalid.

    To issue #1378066, after running "router-gateway-clear",
    _schedule_router will be triggered, and the invalid
    checking will make processing in get_candidates believe
    that all l3-agents are valid to schedule this router,
    and finally, invalid records are inserted into table
    RouterL3AgentBindings.

    Closes-Bug: #1378066
    Closes-Bug: #1417908
    Closes-Bug: #1420032

    Change-Id: If96d866c831330cca68a5fe5a0f27f178bbf40a6