Updates:
Cc: [email protected]
Comment #2 on issue 914 by [email protected]: gnt-job info and list
corrupted after gnt-cluster destroy / init
http://code.google.com/p/ganeti/issues/detail?id=914
After some offline discussion we found that simply
removing those files is dangerous (as it might lead
to loss of data relevant for auditing what happened).
So our plan is to add a check to cluster init that
refuses to init the cluster if old data is still present
telling the user to remove the files if he is sure that
they are no longer needed.
Would that solution work for you as well?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
