Comment 13 for bug 2028724

Reviewed: https://review.opendev.org/c/openstack/neutron/+/905329
Committed: https://opendev.org/openstack/neutron/commit/2c8076dd28c1e51e7d340d3ee5f9056b40396c0c
Submitter: "Zuul (22348)"
Branch: stable/zed

commit 2c8076dd28c1e51e7d340d3ee5f9056b40396c0c
Author: Lewis Denny <email address hidden>
Date: Mon Jul 31 16:38:22 2023 +1000

    Add max limit to agent_down_time

    The agent_down_time ends up being passed to an eventlet green-thread;
    under the hood, this uses a CPython C-types interface with a limitation
    of (2^32 / 2 - 1) INT_MAX (as defined in C) where int is usually 32 bits

    I have set the max value to (2^32 / 2 - 1)/1000 as agent_down_time
    configured in seconds, this ends up being 2147483.

    This patch is required as passing a larger number
    causes this error: OverflowError: timeout is too large

    If a user currently has a value larger than (2^32 / 2 - 1)/1000 set,
    Neutron Server will fail to start and will print out a very helpful
    error message.

    Conflicts:
          neutron/conf/agent/database/agents_db.py

    Closes-Bug: #2028724
    Change-Id: Ib5b943344cddbd468c00768461ba1ee00a2b4c58
    (cherry picked from commit 6fef1e65250dbda057206e1c2ee64f59b21d490f)