Automatic flavor matching when tagging nodes doesn't work for object-storage and custom roles

Bug #1644756 reported by Steven Hardy on 2016-11-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Florian Fuchs

Bug Description

At the moment, with or without the on-going custom role patches ( ), the automatic assignment of the flavor parameter is failing for Object Storage, and any custom role.

In my environment it seems to only work for ceph-storage, control, compute, block-storage. The issue with Swift is probably related to a comment on review 402085, as it's another special casing.

Steven Hardy (shardy) on 2016-11-25
Changed in tripleo:
status: New → Triaged
milestone: none → ocata-2
Julie Pichon (jpichon) wrote :

Thanks for filing this on my behalf!

Changed in tripleo:
importance: Undecided → High
tags: added: tripleo-common ui
Changed in tripleo:
assignee: nobody → Florian Fuchs (flo-fuchs)

Fix proposed to branch: master

Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: ocata-2 → ocata-3

Submitter: Jenkins
Branch: master

commit b6e94126281a58a81fc6503e393e2f290311a663
Author: Florian Fuchs <email address hidden>
Date: Mon Nov 28 21:52:31 2016 +0100

    Fix flavor matching for object-storage role

    When assigning a node to the `object-storage` role, the correct flavor
    will not be picked, because there is a mismatch between the role name
    and the flavor name (swift-storage).

    This patch adds some logic to pick the correct flavor for the object
    storage role.

    Change-Id: Id3d5738361f791a3e1120ad3b51d8867c27e4456
    Closes-Bug: #1644756

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/tripleo-common 5.8.0 release.

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

Other bug subscribers