StarlingX

  1. Bug #2042353
  2. Comment #7

Comment 7 for bug 2042353

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/c/starlingx/config/+/900576
Committed: https://opendev.org/starlingx/config/commit/25a42e06dfdd49ae1876841b05ed281f3097b6b7
Submitter: "Zuul (22348)"
Branch: master

commit 25a42e06dfdd49ae1876841b05ed281f3097b6b7
Author: Boovan Rajendran <email address hidden>
Date: Fri Nov 10 03:11:45 2023 -0500

    Increase timeout for cordon operation

    Based on lab testing we need to increase the overall timeout for the
    host cordon operation to give pods more time to shut down cleanly.
    In lab testing 150 seconds was sufficient, but it's possible that
    some conditions exist which might still cause us to hit the timeout.
    If this happens, we still want to treat the cordon operation as a
    success.

    Test Plan:
    Pass: Test by running 'system kube-host-cordon controller-0' on
    AIO-SX and verify cordon operation completed successfully.
    Pass: Perform k8s upgrade using orchestration method on AIO-SX
    and verify k8s upgraded successfully.

    Closes-Bug: 2042353

    Change-Id: I47fad26c98297227f6352c2df666c384be42d252
    Signed-off-by: Boovan Rajendran <email address hidden>