Change Details

See code for `ra_supports_legacy_reload` and `PCMK_ACTION_RELOAD` `handle_remote_ra_exec()` can continue to support `PCMK_ACTION_RELOAD` as long as we support rolling upgrades from <2.1.0 (see T300)

Before the OCF Resource Agent API 1.1 standard introduced the `reload-agent` action and the `reloadable` parameter meta-data attribute, Pacemaker supported using the `reload` action with the `unique` attribute. Only Pacemaker agents are known to have used this extension. Pacemaker 2.1.0 introduced support for `reload-agent` and deprecated support for `reload`. Once we no longer support rolling upgrades from <2.1.0 (see subtask), we can drop the deprecated support. See code for `ra_supports_legacy_reload` and `PCMK_ACTION_RELOAD`.

See code for `ra_supports_legacy_reload` and `PCMK_ACTION_RELOAD`Before the OCF Resource Agent API 1.1 standard introduced the `reload-agent` action and the `reloadable` parameter meta-data attribute, Pacemaker supported using the `reload` action with the `unique` attribute. Only Pacemaker agents are known to have used this extension. `handle_remote_ra_exec()` can continue toPacemaker 2.1.0 introduced support for `reload-agent` and deprecated support `PCMK_ACTION_RELOAD` asfor `reload`. Once we no long as weer support rolling upgrades from <2.1.0 (see T300)subtask), we can drop the deprecated support. See code for `ra_supports_legacy_reload` and `PCMK_ACTION_RELOAD`.