Newton scheduler clients should keep trying to report

Reviewed: https://review.openstack.org/418590
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bbf9b431ee26e4064278e58bf9c177de48e8719a
Submitter: Jenkins
Branch: master

commit bbf9b431ee26e4064278e58bf9c177de48e8719a
Author: Dan Smith <email address hidden>
Date: Tue Jan 10 13:49:19 2017 -0800

    Make placement client keep trying to connect

    In Newton, placement is optional and computes will stop even trying
    to connect to placement when they encounter an error or missing
    configuration. We really want them to keep trying so that enabling
    the service pre-upgrade does not require restarting all computes
    to start filling data.

    This patch removes the auto-disable logic and replaces it with a
    limited, but persistent warning to the logs about the required
    nature of placement for the upgrade. If we had messaged the upcoming
    requirement better, I think we could have been less chatty here.
    However, we know that it's not been received, so this patch periodically
    re-emits the warning and mentions the upgrade specifically.

    Closes-Bug: #1655494
    Change-Id: Ie6387afeb239a20d39c00f519e8288f3b3a5e9cb

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

Reviewed: https://review.openstack.org/419217
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=13ba33a57488f5e553dcca7162cc35b58ff0e7f8
Submitter: Jenkins
Branch: stable/newton

commit 13ba33a57488f5e553dcca7162cc35b58ff0e7f8
Author: Dan Smith <email address hidden>
Date: Tue Jan 10 13:49:19 2017 -0800

    Make placement client keep trying to connect

    In Newton, placement is optional and computes will stop even trying
    to connect to placement when they encounter an error or missing
    configuration. We really want them to keep trying so that enabling
    the service pre-upgrade does not require restarting all computes
    to start filling data.

    This patch removes the auto-disable logic and replaces it with a
    limited, but persistent warning to the logs about the required
    nature of placement for the upgrade. If we had messaged the upcoming
    requirement better, I think we could have been less chatty here.
    However, we know that it's not been received, so this patch periodically
    re-emits the warning and mentions the upgrade specifically.

    Conflicts:
            nova/scheduler/client/report.py

    NOTE(mriedem): The conflict is due to 3c217acb9 not being in Newton.

    Closes-Bug: #1655494
    Change-Id: Ie6387afeb239a20d39c00f519e8288f3b3a5e9cb
    (cherry picked from commit bbf9b431ee26e4064278e58bf9c177de48e8719a)

This issue was fixed in the openstack/nova 15.0.0.0b3 development milestone.

This issue was fixed in the openstack/nova 14.0.4 release.