Octavia flavor isn't created if composable octavia

Bug #1797443 reported by Brent Eagles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Brent Eagles

Bug Description

Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1637884

We create the octavia flavor for launching amphora in the worker controller template because that is the component that uses the flavor and it's arguably most tightly related to that service. We use docker_puppet_tasks to run the puppet to create the flavor at the appropriate time in the worker. However, it appears that the docker_puppet_tasks is only run on the bootstrap node, which seems to be the first controller (regardless of distribution of services). So in composable roles, the worker, health manager, etc are likely to be located "off-controller" and the flavor will never be created.

Brent Eagles (beagles)
Changed in tripleo:
milestone: none → stein-1
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Brent Eagles (beagles)
Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.openstack.org/609696
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7d533b77370311926e23b18ef6dbdbf2c3dcac01
Submitter: Zuul
Branch: master

commit 7d533b77370311926e23b18ef6dbdbf2c3dcac01
Author: Brent Eagles <email address hidden>
Date: Thu Oct 11 10:34:48 2018 -0230

    Ensure octavia flavor gets configured if composable octavia

    The octavia service templates configure the octavia flavor through the
    controller-worker is deployed on a node other than the controller. Since
    this uses docker_puppet_tasks, it is only run on the bootstrap node
    which at the moment means the first controller. This patch moves the
    flavor creation to the docker API template to make sure the flavor gets
    created when deploying worker components in an non-standard role.

    Closes-Bug: #1797443

    Change-Id: Id823672b82ea60f355d1f01068f802567d687da5

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/618801

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

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/618805

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-heat-templates (stable/queens)

Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/618805
Reason: Abandoning to save resources.

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

Reviewed: https://review.openstack.org/618805
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fb4bc626261cc85c3fee1eb99476b3d7fba03e52
Submitter: Zuul
Branch: stable/queens

commit fb4bc626261cc85c3fee1eb99476b3d7fba03e52
Author: Brent Eagles <email address hidden>
Date: Thu Oct 11 10:34:48 2018 -0230

    Ensure octavia flavor gets configured if composable octavia

    The octavia service templates configure the octavia flavor through the
    controller-worker is deployed on a node other than the controller. Since
    this uses docker_puppet_tasks, it is only run on the bootstrap node
    which at the moment means the first controller. This patch moves the
    flavor creation to the docker API template to make sure the flavor gets
    created when deploying worker components in an non-standard role.

    Conflicts:
        docker/services/octavia-api.yaml

    Closes-Bug: #1797443

    Change-Id: Id823672b82ea60f355d1f01068f802567d687da5
    (cherry picked from commit 7d533b77370311926e23b18ef6dbdbf2c3dcac01)
    (cherry picked from commit 130633422731630ebc0bcc45bb899cd7c0aa1bc3)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 10.2.0

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 8.1.0

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

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

Reviewed: https://review.openstack.org/618801
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=130633422731630ebc0bcc45bb899cd7c0aa1bc3
Submitter: Zuul
Branch: stable/rocky

commit 130633422731630ebc0bcc45bb899cd7c0aa1bc3
Author: Brent Eagles <email address hidden>
Date: Thu Oct 11 10:34:48 2018 -0230

    Ensure octavia flavor gets configured if composable octavia

    The octavia service templates configure the octavia flavor through the
    controller-worker is deployed on a node other than the controller. Since
    this uses docker_puppet_tasks, it is only run on the bootstrap node
    which at the moment means the first controller. This patch moves the
    flavor creation to the docker API template to make sure the flavor gets
    created when deploying worker components in an non-standard role.

    Conflicts:
        docker/services/octavia-api.yaml

    Closes-Bug: #1797443

    Change-Id: Id823672b82ea60f355d1f01068f802567d687da5
    (cherry picked from commit 7d533b77370311926e23b18ef6dbdbf2c3dcac01)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 9.2.0

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