devstackgaterc job is failing

[Numan Siddique]

See this [1] for more information

The commit [2] in neutron could be the cause. Need to investigate.

When q-dhcp is disabled, the tests are passing. Please see [3]

[1] - http://logs.openstack.org/46/346646/22/check/gate-tempest-dsvm-networking-ovn/02f81bb/logs/testr_results.html.gz

[2] - https://github.com/openstack/neutron/commit/7dc2707c2b0b05ad7699a24680a5b45e67f717fc

[3] - https://review.openstack.org/#/c/394199/1
      http://logs.openstack.org/99/394199/1/check/gate-tempest-dsvm-networking-ovn/1d792f1/logs/testr_results.html.gz

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/394457

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/394457
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=17a54337d2cca82a8a6f05972deadc64524b1726
Submitter: Jenkins
Branch: master

commit 17a54337d2cca82a8a6f05972deadc64524b1726
Author: Numan Siddique <email address hidden>
Date: Mon Nov 7 19:56:49 2016 +0530

    Disable q-dhcp in the devstackgaterc job

    devstackgaterc job is failing in gate. When q-dhcp is disabled,
    it is passing.
    This patch disables the q-dhcp and makes use of the native dhcp as a
    temporary solution to fix this issue.
    q-dhcp needs to be enabled back once the issue is fixed properly.

    Please see the bug description for more details.

    Change-Id: I03aaceead620b8e312823a872ef95c42df673252
    Partial-bug: #1639806

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/395248

[OpenStack Infra (hudson-openstack)]

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

commit 9f1057bfd9aff4acee1d41f14298c155a6759f55
Author: Kevin Benton <email address hidden>
Date: Tue Nov 8 15:15:26 2016 -0800

    DHCP: Add missing path for marking ports as ready

    'refresh_dhcp_helper', which is called after subnet update/create
    notifications in the DHCP agent, can end up retrieving ports that
    the agent hadn't yet seen. It will then configure those ports but
    not notify the server that they are ready.

    Unless the port is subsequently updated on the server afterwards to
    generate a new port update notification, the DHCP agent won't ever tell
    the server that the port has had DHCP provisioned. This led to the
    bug this closes. Another patch[1] that removed excessive DHCP ready
    notifications uncovered this bug.

    This patch just adjusts refresh_dhcp_helper to ensure that all ports
    are marked as ready after configuring them all.

    1. Ie7686837b18ff251baa315ef95dc511cda475672

    Change-Id: I1fed60c1835c2ebed7c050c6fa114f89beec3190
    Closes-Bug: #1639806

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/396384

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/396384
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c719a21e5ce496b6818d15f8b80b82d6172ca2f0
Submitter: Jenkins
Branch: stable/newton

commit c719a21e5ce496b6818d15f8b80b82d6172ca2f0
Author: Kevin Benton <email address hidden>
Date: Tue Nov 8 15:15:26 2016 -0800

    DHCP: Add missing path for marking ports as ready

    'refresh_dhcp_helper', which is called after subnet update/create
    notifications in the DHCP agent, can end up retrieving ports that
    the agent hadn't yet seen. It will then configure those ports but
    not notify the server that they are ready.

    Unless the port is subsequently updated on the server afterwards to
    generate a new port update notification, the DHCP agent won't ever tell
    the server that the port has had DHCP provisioned. This led to the
    bug this closes. Another patch[1] that removed excessive DHCP ready
    notifications uncovered this bug.

    This patch just adjusts refresh_dhcp_helper to ensure that all ports
    are marked as ready after configuring them all.

    1. Ie7686837b18ff251baa315ef95dc511cda475672

    Change-Id: I1fed60c1835c2ebed7c050c6fa114f89beec3190
    Closes-Bug: #1639806
    (cherry picked from commit 9f1057bfd9aff4acee1d41f14298c155a6759f55)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 10.0.0.0b1 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 9.1.1 release.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/421997

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/421997
Reason: The patch is not relevant for Mitaka because we did not have provisioning blocks back then.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/433288
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=4fe207e8b8a9342838f69adb26ad1830cbba7b04
Submitter: Jenkins
Branch: master

commit 4fe207e8b8a9342838f69adb26ad1830cbba7b04
Author: Russell Bryant <email address hidden>
Date: Mon Feb 13 16:27:20 2017 -0500

    Sync devstackgaterc with devstackgatenativeservicesrc.

    The main tempest job and the "native-services" job have been running the
    same configuration for a while. At one point we had thought that we
    might want to retain support for the DHCP agent, but I propose that we
    drop it and revisit if there's demand for it in the future.

    After this patch lands, I'm going to remove references to the
    nativeservicesrc file in CI config and then we can remove the file from
    our repo.

    Change-Id: I3aa7a6ac10e4da00d5830f68d7c9d3d684f91218
    Closes-bug: 1639806

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-ovn 3.0.0.0b1 development milestone.