Devstack plugin fails with worker enabled

Bug #1733992 reported by Ritesh Anand on 2017-11-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ritesh Anand

Bug Description

On Ubuntu Xenial current devstack, with designate devstack plugin enabled fails to stack.

Add the follwing to local.conf, for devstack, to enable designate devstack plugin:

enable_plugin designate
enable_service designate,designate-central,designate-api,designate-worker,designate-producer,designate-mdns fails with:

"ERROR designate.cmd.pool_manager [-] You have designate-worker enabled, starting designate-pool-manager is incompatible with designate-worker. You need to start designate-worker instead."

Changed in designate:
assignee: nobody → Ritesh Anand (ritesh-anand)
status: New → In Progress
Dr. Jens Harbott (j-harbott) wrote :

As a workaround you should be able to get by if you disable the offending services in your local.conf, i.e. add

disable_service designate-pool-manager

disable_service designate-zone-manager

Submitter: Zuul
Branch: master

commit 0f8db9f7542201c1b570f1c7fc51c696911e39ab
Author: Ritesh Anand <email address hidden>
Date: Mon Nov 27 13:55:16 2017 -0800

    Enable worker and producer by default in devstack

    In devstack settings we have pool-manager and zone-manager
    enabled by default. This causes conflict if a user wants to run
    designate plugin with worker and producer.

    This change replaces pool-manager and zone-manager with worker
    and producer in devstack settings.

    Closes-Bug: #1733992

    Change-Id: Id96f1430d1091f2485099523fae499bde377e7e6

Changed in designate:
status: In Progress → Fix Released

This issue was fixed in the openstack/designate development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers