designate charm fails to bootstrap designate for pike release.

Bug #1715411 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate Charm
Fix Released
Critical
James Page

Bug Description

The charm makes use of the v1 API, which is disabled by default in the Pike OpenStack release.

This stops the charm from bootstrapping designate as part of install/config.

James Page (james-page)
Changed in charm-designate:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → James Page (james-page)
milestone: none → 17.08
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-designate (master)

Fix proposed to branch: master
Review: https://review.openstack.org/501302

Changed in charm-designate:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-designate (master)

Reviewed: https://review.openstack.org/501302
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=2ae25faae378f84543a0f64541ad9fffc45e9890
Submitter: Jenkins
Branch: master

commit 2ae25faae378f84543a0f64541ad9fffc45e9890
Author: James Page <email address hidden>
Date: Wed Sep 6 15:58:57 2017 +0100

    Re-enable v1 API for charm compatibility

    Pike disables the v1 API be default; re-enable universally until
    the charm can be refactored to support the v2 API.

    Change-Id: Ib71f8b6187add4c28170b27d04f5d203f855ac82
    Closes-Bug: 1715411

Changed in charm-designate:
status: In Progress → Fix Committed
James Page (james-page)
Changed in charm-designate:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.