You are here. You do not want to be here. Ganeti is missing that one feature you need and someone recommended that you edit the configuration. This page will tell you how, and try to dissuade you from doing so unless really necessary.
We generally do not encourage people to edit the configuration, but there are certain SNAFUs that are easiest to get out of by making a small change to the configuration. We try to fix these, so please make an issue, comment on an existing one, or ask around for alternative solutions in IRC or on the mailing list.
For resiliency purposes, the configuration is distributed and checked for unauthorized modifications, and changing it is intentionally not easy. You will have to go through a precise series of steps, and should you stray too far, the situation may go beyond repair. This is why you should not make a habit out of it.
gnt-cluster watcher pause 6h
. Give yourself more time if needed.gnt-cluster queue drain
gnt-job list
/var/lib/ganeti/config.data
/usr/lib/ganeti/tools/fmtjson <config.data >config.readable
gnt-cluster queue undrain
gnt-cluster redist-conf
gnt-cluster verify
, and whatever specific checks you needgnt-cluster watcher continue
If anything goes wrong, you can restore the old configuration by using the same procedure. If you changed the state of the cluster in the meantime, Ganeti might complain upon seeing the state of the configuration not match reality.