controller-no-external.yaml fix backport

Bug #1573943 reported by Christopher Brown
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Dan Sneddon
Liberty
Fix Released
Medium
Christopher Brown
Mitaka
Fix Released
Medium
Christopher Brown

Bug Description

Deployment using controller-no-external.yaml fails with:

ERROR: Failed to validate: Failed to validate: resources[0]: Property error: resources.NetworkConfig.properties: Unknown Property ControlPlaneIp

The following fix committed recently to master fixes this:

https://review.openstack.org/#/c/309211/

I have cherry-picked this to Liberty and Mitaka branches as a simple backport fix.

tags: added: backport-liberty
tags: added: backport
removed: backport-liberty
Steven Hardy (shardy)
tags: added: liberty-backport-potential mitaka-backport-potential
removed: backport
Changed in tripleo:
status: New → Fix Committed
importance: Undecided → Medium
milestone: none → newton-1
assignee: nobody → Dan Sneddon (dsneddon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/mitaka)

Reviewed: https://review.openstack.org/309662
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=29cc933a8ae0ed433c2461d8bd07cf5352565a40
Submitter: Jenkins
Branch: stable/mitaka

commit 29cc933a8ae0ed433c2461d8bd07cf5352565a40
Author: Dan Sneddon <email address hidden>
Date: Thu Apr 21 15:45:25 2016 -0700

    Fix controller-no-external.yaml in bonded configs.

    For some reason the controller-no-external.yaml template is configured
    for DHCP on the control plane interface. We switched to static control
    plane IPs before the controller-no-external.yaml was created (IIRC), so
    I'm not sure how that happened. This change brings the
    controller-no-external.yaml in line with the rest of the bonded NIC
    templates.

    Closes-Bug: #1573943
    Change-Id: I2ac929e241707db72a0beabf9d5cd7fc14b90f76
    (cherry picked from commit 6d27813db3ce06b4352ac42c3e45887030094c39)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/liberty)

Reviewed: https://review.openstack.org/309661
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=df8e8a4b7acd384f8eb3ee98231b00ed78df23e5
Submitter: Jenkins
Branch: stable/liberty

commit df8e8a4b7acd384f8eb3ee98231b00ed78df23e5
Author: Dan Sneddon <email address hidden>
Date: Thu Apr 21 15:45:25 2016 -0700

    Fix controller-no-external.yaml in bonded configs.

    For some reason the controller-no-external.yaml template is configured
    for DHCP on the control plane interface. We switched to static control
    plane IPs before the controller-no-external.yaml was created (IIRC), so
    I'm not sure how that happened. This change brings the
    controller-no-external.yaml in line with the rest of the bonded NIC
    templates.

    Closes-Bug: #1573943
    Change-Id: I2ac929e241707db72a0beabf9d5cd7fc14b90f76
    (cherry picked from commit 6d27813db3ce06b4352ac42c3e45887030094c39)

Steven Hardy (shardy)
Changed in tripleo:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/331680

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/tripleo-heat-templates 2.1.0

This issue was fixed in the openstack/tripleo-heat-templates 2.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

This issue was fixed in the openstack/tripleo-heat-templates 2.1.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.