DR: set-geo-primary-node should be more verbose if successful
Description
While setting up DR, running gitlab-ctl set-geo-primary-node
returns
Saving primary GeoNode with URL http://primary/
2017-04-14T16:39:40.951Z 4553 TID-ouaakc1zs INFO: Cron Jobs - add job with name: geo_bulk_notify_worker
This is, in fact, a success message, but it wasn't clear that it was.
Proposal
The goal of this command is to set the current node as the primary. Upon success, we should say
Saving primary GeoNode with URL http://<IP or `FQDN`
http://<IP or `FQDN`> is now the primary node.
Moreover, is the INFO log message necessary there?