Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart

We created a cluster via blueprints where we did not want components to be started by Ambari (background - this was a takeover of existing cluster where services were already installed and started. We did not want STARTs to be done as they would overwrite existing configs). Towards this goal we set "provision_action" : "INSTALL_ONLY" so that when agents register with Ambari they will only do the install and not start.

{
  "blueprint" : "blueprint",
  "default_password" : "ambari",
  "provision_action" : "INSTALL_ONLY",
  "host_groups" : [
     ...
  ]
}

This flag did its job as long as ambari-server was not restarted. After restart however, new agents would install and start the host-components.