have the same.. below is the related unit logs, it is not firing the switchover, despite I shutdown the master machine. root@server:~# juju debug-log --include postgres-ha/6 unit-postgres-ha-6: 20:50:49 WARNING unit.postgres-ha/6.juju-log Falling back to comma separated extra_pg_auth unit-postgres-ha-6: 20:50:50 DEBUG unit.postgres-ha/6.juju-log Setting hot_standby to True unit-postgres-ha-6: 20:50:50 DEBUG unit.postgres-ha/6.juju-log Setting wal_level to logical unit-postgres-ha-6: 20:50:50 DEBUG unit.postgres-ha/6.juju-log Setting wal_keep_segments to 500 unit-postgres-ha-6: 20:50:50 INFO unit.postgres-ha/6.juju-log PostgreSQL has been configured unit-postgres-ha-6: 20:50:51 DEBUG unit.postgres-ha/6.juju-log postgresql.conf settings unchanged unit-postgres-ha-6: 20:50:51 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:851:set_active unit-postgres-ha-6: 20:50:51 INFO unit.postgres-ha/6.juju-log active: Live secondary (9.5.10) unit-postgres-ha-6: 20:50:52 DEBUG unit.postgres-ha/6.juju-log Coordinator: Leader handling coordinator requests unit-postgres-ha-6: 20:50:52 DEBUG unit.postgres-ha/6.juju-log Coordinator: Publishing state unit-postgres-ha-6: 20:50:33 INFO unit.postgres-ha/6.juju-log Reactive main running for hook update-status unit-postgres-ha-6: 20:50:33 DEBUG unit.postgres-ha/6.juju-log Coordinator: Using charms.coordinator.SimpleCoordinator coordinator unit-postgres-ha-6: 20:50:33 INFO unit.postgres-ha/6.juju-log Initializing Snap Layer unit-postgres-ha-6: 20:50:34 DEBUG unit.postgres-ha/6.update-status none unit-postgres-ha-6: 20:50:34 INFO unit.postgres-ha/6.juju-log Initializing Apt Layer unit-postgres-ha-6: 20:50:34 DEBUG unit.postgres-ha/6.juju-log Coordinator: Loading state unit-postgres-ha-6: 20:50:35 DEBUG unit.postgres-ha/6.juju-log Coordinator: Leader handling coordinator requests unit-postgres-ha-6: 20:50:35 INFO unit.postgres-ha/6.juju-log Coordinator: Initializing coordinator layer unit-postgres-ha-6: 20:50:36 INFO unit.postgres-ha/6.juju-log Initializing Leadership Layer (is leader) unit-postgres-ha-6: 20:50:36 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/workloadstatus.py:57:initialize_workloadstatus_state unit-postgres-ha-6: 20:50:36 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/postgresql/preflight.py:25:block_on_bad_juju unit-postgres-ha-6: 20:50:37 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/postgresql/preflight.py:33:block_on_invalid_config unit-postgres-ha-6: 20:50:37 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:45:main unit-postgres-ha-6: 20:50:37 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.is_leader unit-postgres-ha-6: 20:50:37 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.coordinator unit-postgres-ha-6: 20:50:37 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.master unit-postgres-ha-6: 20:50:37 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.replication_password unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.client.passwords_set unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.client.published unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.created unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.is_running unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.kernel_settings.set unit-postgres-ha-6: 20:50:38 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.locale.set unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.cloned unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.had_peers unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.has_master unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.has_peers unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.master.authorized unit-postgres-ha-6: 20:50:39 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.master.peered unit-postgres-ha-6: 20:50:40 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.wal_e.configured unit-postgres-ha-6: 20:50:40 DEBUG unit.postgres-ha/6.juju-log Reactive state: workloadstatus.active unit-postgres-ha-6: 20:50:40 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:38:publish_client_relations unit-postgres-ha-6: 20:50:40 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:38:replication_states unit-postgres-ha-6: 20:50:42 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:872:set_version unit-postgres-ha-6: 20:50:43 INFO unit.postgres-ha/6.juju-log Setting application version to 9.5.10 unit-postgres-ha-6: 20:50:43 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:205:configure_cluster unit-postgres-ha-6: 20:50:43 WARNING unit.postgres-ha/6.juju-log Falling back to comma separated extra_pg_auth unit-postgres-ha-6: 20:50:44 DEBUG unit.postgres-ha/6.juju-log Setting hot_standby to True unit-postgres-ha-6: 20:50:44 DEBUG unit.postgres-ha/6.juju-log Setting wal_level to logical unit-postgres-ha-6: 20:50:44 DEBUG unit.postgres-ha/6.juju-log Setting wal_keep_segments to 500 unit-postgres-ha-6: 20:50:44 INFO unit.postgres-ha/6.juju-log PostgreSQL has been configured unit-postgres-ha-6: 20:50:44 DEBUG unit.postgres-ha/6.juju-log postgresql.conf settings unchanged unit-postgres-ha-6: 20:50:45 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:350:publish_replication_details unit-postgres-ha-6: 20:50:46 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/apt.py:47:ensure_package_status unit-postgres-ha-6: 20:50:46 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:925:update_postgresql_crontab unit-postgres-ha-6: 20:50:47 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:475:follow_master unit-postgres-ha-6: 20:50:47 INFO unit.postgres-ha/6.juju-log Continuing to follow postgres-ha/3 unit-postgres-ha-6: 20:50:47 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:47:set_client_passwords unit-postgres-ha-6: 20:50:48 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:879:install_administrative_scripts unit-postgres-ha-6: 20:50:48 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:767:update_pgpass unit-postgres-ha-6: 20:50:49 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:106:mirror_master unit-postgres-ha-6: 20:50:49 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:205:configure_cluster unit-postgres-ha-6: 20:55:51 INFO unit.postgres-ha/6.juju-log Reactive main running for hook update-status unit-postgres-ha-6: 20:55:51 DEBUG unit.postgres-ha/6.juju-log Coordinator: Using charms.coordinator.SimpleCoordinator coordinator unit-postgres-ha-6: 20:55:51 INFO unit.postgres-ha/6.juju-log Initializing Snap Layer unit-postgres-ha-6: 20:55:51 DEBUG unit.postgres-ha/6.update-status none unit-postgres-ha-6: 20:55:52 INFO unit.postgres-ha/6.juju-log Initializing Apt Layer unit-postgres-ha-6: 20:55:52 DEBUG unit.postgres-ha/6.juju-log Coordinator: Loading state unit-postgres-ha-6: 20:55:53 DEBUG unit.postgres-ha/6.juju-log Coordinator: Leader handling coordinator requests unit-postgres-ha-6: 20:55:53 INFO unit.postgres-ha/6.juju-log Coordinator: Initializing coordinator layer unit-postgres-ha-6: 20:55:54 INFO unit.postgres-ha/6.juju-log Initializing Leadership Layer (is leader) unit-postgres-ha-6: 20:55:54 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/workloadstatus.py:57:initialize_workloadstatus_state unit-postgres-ha-6: 20:55:54 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/postgresql/preflight.py:25:block_on_bad_juju unit-postgres-ha-6: 20:55:55 INFO unit.postgres-ha/6.juju-log preflight handler: reactive/postgresql/preflight.py:33:block_on_invalid_config unit-postgres-ha-6: 20:55:55 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:38:replication_states unit-postgres-ha-6: 20:55:57 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:45:main unit-postgres-ha-6: 20:55:57 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.is_leader unit-postgres-ha-6: 20:55:57 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.coordinator unit-postgres-ha-6: 20:55:57 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.master unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: leadership.set.replication_password unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.client.passwords_set unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.client.published unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.created unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.is_running unit-postgres-ha-6: 20:55:58 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.kernel_settings.set unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.cluster.locale.set unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.cloned unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.had_peers unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.has_master unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.has_peers unit-postgres-ha-6: 20:55:59 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.master.authorized unit-postgres-ha-6: 20:56:00 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.replication.master.peered unit-postgres-ha-6: 20:56:00 DEBUG unit.postgres-ha/6.juju-log Reactive state: postgresql.wal_e.configured unit-postgres-ha-6: 20:56:00 DEBUG unit.postgres-ha/6.juju-log Reactive state: workloadstatus.active unit-postgres-ha-6: 20:56:00 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:38:publish_client_relations unit-postgres-ha-6: 20:56:00 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:925:update_postgresql_crontab unit-postgres-ha-6: 20:56:01 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:767:update_pgpass unit-postgres-ha-6: 20:56:02 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:879:install_administrative_scripts unit-postgres-ha-6: 20:56:02 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/apt.py:47:ensure_package_status unit-postgres-ha-6: 20:56:03 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:872:set_version unit-postgres-ha-6: 20:56:03 INFO unit.postgres-ha/6.juju-log Setting application version to 9.5.10 unit-postgres-ha-6: 20:56:03 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:205:configure_cluster unit-postgres-ha-6: 20:56:03 WARNING unit.postgres-ha/6.juju-log Falling back to comma separated extra_pg_auth unit-postgres-ha-6: 20:56:04 DEBUG unit.postgres-ha/6.juju-log Setting hot_standby to True unit-postgres-ha-6: 20:56:04 DEBUG unit.postgres-ha/6.juju-log Setting wal_level to logical unit-postgres-ha-6: 20:56:04 DEBUG unit.postgres-ha/6.juju-log Setting wal_keep_segments to 500 unit-postgres-ha-6: 20:56:04 INFO unit.postgres-ha/6.juju-log PostgreSQL has been configured unit-postgres-ha-6: 20:56:04 DEBUG unit.postgres-ha/6.juju-log postgresql.conf settings unchanged unit-postgres-ha-6: 20:56:05 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:47:set_client_passwords unit-postgres-ha-6: 20:56:05 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:350:publish_replication_details unit-postgres-ha-6: 20:56:06 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/replication.py:475:follow_master unit-postgres-ha-6: 20:56:07 INFO unit.postgres-ha/6.juju-log Continuing to follow postgres-ha/3 unit-postgres-ha-6: 20:56:07 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/client.py:106:mirror_master unit-postgres-ha-6: 20:56:07 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:205:configure_cluster unit-postgres-ha-6: 20:56:07 WARNING unit.postgres-ha/6.juju-log Falling back to comma separated extra_pg_auth unit-postgres-ha-6: 20:56:08 DEBUG unit.postgres-ha/6.juju-log Setting hot_standby to True unit-postgres-ha-6: 20:56:08 DEBUG unit.postgres-ha/6.juju-log Setting wal_level to logical unit-postgres-ha-6: 20:56:08 DEBUG unit.postgres-ha/6.juju-log Setting wal_keep_segments to 500 unit-postgres-ha-6: 20:56:08 INFO unit.postgres-ha/6.juju-log PostgreSQL has been configured unit-postgres-ha-6: 20:56:09 DEBUG unit.postgres-ha/6.juju-log postgresql.conf settings unchanged unit-postgres-ha-6: 20:56:09 INFO unit.postgres-ha/6.juju-log Invoking reactive handler: reactive/postgresql/service.py:851:set_active unit-postgres-ha-6: 20:56:09 INFO unit.postgres-ha/6.juju-log active: Live secondary (9.5.10) unit-postgres-ha-6: 20:56:10 DEBUG unit.postgres-ha/6.juju-log Coordinator: Leader handling coordinator requests unit-postgres-ha-6: 20:56:10 DEBUG unit.postgres-ha/6.juju-log Coordinator: Publishing state