Issues resolutions requiring manual application

Issues resolutions requiring manual application


Before proceeding with the manual steps below, verify that you have performed the steps described in Apply maintenance updates.

[35657] [Queens] Failure during designate-manage database sync

When applying MCP 2019.2.11 maintenance updates, the designate state may fail due to inability to run the designate-manage database sync command. For details, see the community issue.

To apply the fix that prevents the issue, manually clean up the Designate database as described below.

To apply the issue resolution:

  1. Log in to the Salt Master node.

  2. Verify that the Designate packages are updated on the primary node. The reported package version must be 1:6.0.1-1.1~u16.04+mcp31.

    sudo salt -I "designate:server:role:primary" pkg.version designate-central python-designate
  3. Stop the designate-central service on all nodes:

    sudo salt -I "designate:server:role:*" service.stop designate-central
  4. Start the designate-central service on the primary node only:

    sudo salt -I "designate:server:role:primary" service.start designate-central
  5. Clean up the duplicated service entries from the Designate database:

    sudo salt -I "designate:server:role:primary" "designate-manage services delete_duplicated_services"
  6. Start the designate-central service:

    sudo salt -I "designate:server:role:*" service.start designate-central

Once done, continue the update process from the failed step.