Default flavors should be added by init script

Bug #1567964 reported by Dave McCowan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Undecided
Dave McCowan

Bug Description

In Mitaka, the Nova team removed the default flavors as part of Nova proper. Now, it is up to installers and operators to add their own flavors to use. Kolla should add the former default flavors during the init-runonce script.

Changed in kolla:
assignee: nobody → Dave McCowan (dave-mccowan)
Changed in kolla:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/302534
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=fda9444ea63ec436e7598ebb4ce221db0dd5d97d
Submitter: Jenkins
Branch: master

commit fda9444ea63ec436e7598ebb4ce221db0dd5d97d
Author: Dave McCowan <email address hidden>
Date: Wed Apr 6 23:31:10 2016 -0700

    Add default flavors during init-runonce

    The nova team is removing the default flavors from a standard
    deployment. This is great for operators, who have to delete
    the defaults anyways. This patch adds the original default
    flavors back during init-runonce so kolla users can be ready
    to launch instances.

    Closes-Bug: #1567964
    Change-Id: I17daec98997a6e412a99f34d3f8a4324460d8c60

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 3.0.0.0b1

This issue was fixed in the openstack/kolla 3.0.0.0b1 development milestone.

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.