Backend configuration is outdated and no longer valid

Bug #1961516 reported by Takashi Kajinami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-designate
Fix Released
Critical
Takashi Kajinami

Bug Description

The current method to set up bind9 backend is no longer valid.

- The backend::bind9 section is no longer used.
- The backend definition should use not configuration parameters but pools.yaml as described in current designate documentation[1].

 [1] https://docs.openstack.org/designate/latest/admin/backends/bind9.html

Changed in puppet-designate:
importance: Undecided → Critical
assignee: nobody → Takashi Kajinami (kajinamit)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-designate (master)
Changed in puppet-designate:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-designate (master)

Reviewed: https://review.opendev.org/c/openstack/puppet-designate/+/830017
Committed: https://opendev.org/openstack/puppet-designate/commit/22019e46e2553e047fd7706c82d29d3cfb978e39
Submitter: "Zuul (22348)"
Branch: master

commit 22019e46e2553e047fd7706c82d29d3cfb978e39
Author: Takashi Kajinami <email address hidden>
Date: Sun Feb 20 17:41:59 2022 +0900

    Fix setup of bind9 backend

    Designate no longer uses the parameters in the [backend:bind9] section,
    since ppols.yaml was introduced. This change ensures the parameters in
    this wrong section are purged.

    Also, this change introduces support for setting up backend using
    pools.yaml according to the current installation guide.

    Closes-Bug: #1961516
    Change-Id: I28a91ab99325970db1e96aa904f35e8f9a5e109c

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

Reviewed: https://review.opendev.org/c/openstack/puppet-designate/+/830118
Committed: https://opendev.org/openstack/puppet-designate/commit/456aef053ec1e21b908153d904ac3ce8b67577b3
Submitter: "Zuul (22348)"
Branch: master

commit 456aef053ec1e21b908153d904ac3ce8b67577b3
Author: Takashi Kajinami <email address hidden>
Date: Mon Feb 21 16:18:32 2022 +0900

    Support agent backend and bind9 agent backend

    This change introduces support for setting up agent backend[1] and
    bind9 agent backend.

    [1] https://docs.openstack.org/designate/latest/admin/backends/agent.html

    Related-Bug: #1961516
    Change-Id: I5c65aa4853d8dfb4e54eaa4d65c871aa7968117c

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-designate (stable/xena)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/puppet-designate/+/832763

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-designate (stable/xena)

Reviewed: https://review.opendev.org/c/openstack/puppet-designate/+/832763
Committed: https://opendev.org/openstack/puppet-designate/commit/93f0d9b7aa09d1c6e40d5775e3d924845508a6f5
Submitter: "Zuul (22348)"
Branch: stable/xena

commit 93f0d9b7aa09d1c6e40d5775e3d924845508a6f5
Author: Takashi Kajinami <email address hidden>
Date: Sun Feb 20 17:41:59 2022 +0900

    Fix setup of bind9 backend

    Designate no longer uses the parameters in the [backend:bind9] section,
    since ppols.yaml was introduced. This change ensures the parameters in
    this wrong section are purged.

    Also, this change introduces support for setting up backend using
    pools.yaml according to the current installation guide.

    Backport note
    - Adjusted some logic to use hard-coded user/group names, because
      34ff6e6f04a69fec9579accc0bcc5f1c29049abe is not present in
      stable/xena.

    - Squashed the commit 979dd5b2dc69590a457f2c318b2dfc0fd6810dcd which
      fixed the wrong default dns_port.

    Closes-Bug: #1961516
    Change-Id: I28a91ab99325970db1e96aa904f35e8f9a5e109c
    (cherry picked from commit 22019e46e2553e047fd7706c82d29d3cfb978e39)

tags: added: in-stable-xena
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-designate (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/puppet-designate/+/833426

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-designate 20.2.0

This issue was fixed in the openstack/puppet-designate 20.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-designate (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/puppet-designate/+/833426
Committed: https://opendev.org/openstack/puppet-designate/commit/34bffaea0075ca45d1d72ee39d1d3d2b1e6d3d37
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 34bffaea0075ca45d1d72ee39d1d3d2b1e6d3d37
Author: Takashi Kajinami <email address hidden>
Date: Sun Feb 20 17:41:59 2022 +0900

    Fix setup of bind9 backend

    Designate no longer uses the parameters in the [backend:bind9] section,
    since ppols.yaml was introduced. This change ensures the parameters in
    this wrong section are purged.

    Also, this change introduces support for setting up backend using
    pools.yaml according to the current installation guide.

    Backport note
    - Adjusted some logic to use hard-coded user/group names, because
      34ff6e6f04a69fec9579accc0bcc5f1c29049abe is not present in
      stable/xena.

    - Squashed the commit 979dd5b2dc69590a457f2c318b2dfc0fd6810dcd which
      fixed the wrong default dns_port.

    Closes-Bug: #1961516
    Change-Id: I28a91ab99325970db1e96aa904f35e8f9a5e109c
    (cherry picked from commit 22019e46e2553e047fd7706c82d29d3cfb978e39)
    (cherry picked from commit 93f0d9b7aa09d1c6e40d5775e3d924845508a6f5)

tags: added: in-stable-wallaby
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-designate 18.6.0

This issue was fixed in the openstack/puppet-designate 18.6.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-designate 19.5.0

This issue was fixed in the openstack/puppet-designate 19.5.0 release.

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.