Actually I first saw this problem in vault and then in designate, by pure coincidence. But I expected it to be rather generic and affect every application clustered with hacluster subordinate charm (that's why I tested with keystone next, as initially reported).
Actually I first saw this problem in vault and then in designate, by pure coincidence. But I expected it to be rather generic and affect every application clustered with hacluster subordinate charm (that's why I tested with keystone next, as initially reported).