community.mongodb icon indicating copy to clipboard operation
community.mongodb copied to clipboard

mongodb_shutdown: Ignore "this node decided to step down for other reasons"

Open rhysmeister opened this issue 1 year ago • 0 comments

SUMMARY

This error has happened a few times in the CI with 6.0...

ok: [testhost] => {
    "changed": false,
    "invocation": {
        "module_args": {
            "auth_mechanism": null,
            "connection_options": null,
            "force": false,
            "login_database": "admin",
            "login_host": "localhost",
            "login_password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "login_port": 3001,
            "login_user": "test_root",
            "ssl": false,
            "ssl_ca_certs": null,
            "ssl_cert_reqs": "CERT_REQUIRED",
            "ssl_certfile": null,
            "ssl_crlfile": null,
            "ssl_keyfile": null,
            "ssl_pem_passphrase": null,
            "strict_compatibility": true,
            "timeout": 10
        }
    },
    "msg": "An error occurred: While waiting for secondaries to catch up before stepping down, this node decided to step down for other reasons, full error: {'topologyVersion': {'processId': ObjectId('6341abdf1bdb4925796dc00f'), 'counter': 10}, 'ok': 0.0, 'errmsg': 'While waiting for secondaries to catch up before stepping down, this node decided to step down for other reasons', 'code': 189, 'codeName': 'PrimarySteppedDown'}"
}

As the intended event has happened anyway we should report this as a success, perhaps controlable via a parameter.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

mongodb_shutdown

rhysmeister avatar Oct 08 '22 17:10 rhysmeister