Comment 10 for bug 1952363

I was able to reproduce it with these steps:

juju deploy ./my-vault.yaml # https://paste.ubuntu.com/p/P9QyKjtCRV/
juju wait

initialize/unsel vault.

# change the vip from 10.5.250.250 to 10.5.250.251
juju config vault vip=10.5.250.251

juju show-unit hacluster/0
....
          json_groups: '{"grp_vault-ext_vips": "res_vault-ext_9ede165_vip res_vault-ext_c02fdce_vip"}'
          json_resource_params: '{"res_vault-ext_9ede165_vip": " params ip=\"10.5.250.251\" meta
            migration-threshold=\"INFINITY\" failure-timeout=\"5s\" op monitor timeout=\"20s\"
            interval=\"10s\" depth=\"0\"", "res_vault-ext_c02fdce_vip": " params
            ip=\"10.5.250.250\" meta migration-threshold=\"INFINITY\" failure-timeout=\"5s\" op
            monitor timeout=\"20s\" interval=\"10s\" depth=\"0\""}'
          json_resources: '{"res_vault-ext_9ede165_vip": "ocf:heartbeat:IPaddr2",
            "res_vault-ext_c02fdce_vip": "ocf:heartbeat:IPaddr2"}'
....

There should be a json_delete_resources key to ask the deletion of the vip and also the old vip shouldn't be present in json_resource_params .