Product SiteDocumentation Site

F.2.2. Upgrade the Configuration

As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax.
In order to support such environments, it is actually possible to continue using the old 0.6 syntax.
The downside however, is that not all the new features will be available and there is a performance impact since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely.
Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally).
  1. Create a shadow copy to work with
    crm_shadow --create upgrade06
  2. Verify the configuration is valid
    crm_verify --live-check
  3. Fix any errors or warnings
  4. Perform the upgrade
    cibadmin --upgrade
    If this step fails, there are three main possibilities
    1. The configuration was not valid to start with - go back to step 2
    2. The transformation failed - report a bug or email the project at
    3. The transformation was successful but produced an invalid result [14]
    If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit and/or try the following procedure described below under Section F.2.3, “Manually Upgrading the Configuration”.
  5. Check the changes
    crm_shadow --diff
    If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs) now is the time to do so. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually:
    crm_shadow --edit
    Will open the configuration in your favorite editor (or whichever one is specified by the standard EDITOR environment variable).
  6. Preview how the cluster will react
    Test what the cluster will do when you upload the new configuration
    ptest -VVVVV --live-check --save-dotfile
    Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See Section 2.7, “Testing Your Configuration Changes” for further details on how to interpret the output of ptest.
  7. Upload the changes
    crm_shadow --commit upgrade06 --force
    If this step fails, something really strange has occurred. You should report a bug.

[14] The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation