Yes, it is listed in "Known Issues" as I mentioned in my previous comment such workaround won't fix particularly nothing. I think we should update our documentation from
psql -U nailgun -W -h 127.0.0.1
update clusters set is_customized=false where id=${ID};
to following snippet:
psql -U nailgun -W -h 127.0.0.1
update clusters set replaced_deployment_info='{}' where id=${ID};
with mention that user must do this before deployment of newly added nodes to already deployed cluster if he/she has modified deployment info for that cluster via cli.
Meg,
Yes, it is listed in "Known Issues" as I mentioned in my previous comment such workaround won't fix particularly nothing. I think we should update our documentation from
psql -U nailgun -W -h 127.0.0.1
update clusters set is_customized=false where id=${ID};
to following snippet:
psql -U nailgun -W -h 127.0.0.1 deployment_ info='{ }' where id=${ID};
update clusters set replaced_
with mention that user must do this before deployment of newly added nodes to already deployed cluster if he/she has modified deployment info for that cluster via cli.